Spurious malware / spam detection is a painful topic to discuss - and it's even more so when the question of country code alias redirection is discussed. Like auto pagination long ago, country code alias redirection appears to be another case of Google manipulating its customers, maliciously. If you consider this issue from the viewpoint of Blogger blogs in general, though, you may see the full picture.
Blogger blogs, like the Internet, need to be available to all countries in the world, without fear of censorship. Country Code Alias Redirection allows Blogger to selectively disable any single blog, in any single country. This selective disabling will, eventually, eliminate the need of any country government to block the entire Blogger service, in their country, because of a few unsuitable blogs.
Country Code Alias Redirection is a righteous feature in Blogger blogs. Like many new Google features, it was added before every Internet service was made able to support it. CCAR uses an Internet standard - not a Google proprietary feature - the canonical URL tag. If you look at the header in this blog, you can see an example of a canonical URL tag.
<link href='http://blogging.nitecruzr.net/2013/02/malware-classification-and-cc-alias.html' rel='canonical'/>That's the tag for this article, for instance.
Some Blogger blog owners find that CCAR causes problems, with some accessories on their blog. Some owners have added anti redirection code to their blogs, so the accessories on their blogs continue to work. CCAR may not work with every third party provided blog accessory or Internet service - because all Internet services, and third party accessory providers, are not yet aware of canonical URL tags.
Just because some people are not up to date with all Internet features (like CCAR), this does not mean that CCAR should not be used. The people involved need to be encouraged to update their accessories, and their services, as necessary.
Right now, some blogs which include anti redirection code are being spuriously detected as malware hosts - and this is more controversy. The anti redirection code looks like malware, because similar code is used by people to abuse our blogs. To not classify blogs attempting to disable CCAR, would require the malware classifier to identify the intent of the blog owner - and would make malware detection more complicated.
Identification of intent is not present in computer software, right now. That ability will be available only when computers truly are programmed to "think" - and when that happens, it may be the end of the human race as we know it.
Since CCAR is a righteous feature, it's possible that anti redirection code actually should be treated as malware - even though the blog owners, adding the code to their blogs, may not consider this to be the case. Those of us who are concerned with detection and removal of malware and spam from the Internet, in general, know that malware and spam is like a cancer - if you don't remove what you see, it's only going to get worse.
To allow anti redirection code to be installed in some Blogger blogs, will encourage other blog owners to do the same. Also, it will allow some hackers and spammers to do likewise, without fear of detection. Neither of these possibilities is good for Blogger blogs, in general.
If you installed anti redirection code in your blog some time ago, your blog was just locked as a suspected malware host. and you are now anxiously waiting for malware review while your blog remains offline, we're sorry for you. But you are not being abused by Blogger - nor is your malware classification unfair.
Remove the anti redirection code, on your blog - now, while you are able. Encourage the providers of third party accessories and Internet services to update their code. And don't allow or encourage hackers and spammers to abuse Blogger blogs, or the Internet in general. Please.
>> Top
No comments:
Post a Comment