The new "ping" attribute might ruin Firefox
When I click on a link on a page, I want the browser to go to that page. Nothing more, nothing less, nothing else. A simple anchor tag with a simple href. Sometimes even javascript is acceptable, but I'm not very fond of those types of link. I hate it when I click on something without knowing where I'm going or what's happening in the background.
Some people may wonder what's the point of having such obscure links and not simple straightforward anchors. The answer: user activity tracking. See, most website administrators will gather and store everything they can about your browsing habits, whether you like it or not. Most of it is pretty harmless and helps them improve their service. They identify the most visited pages and give them more importance. The less visited ones are analyzed in order to identify problems or broken links. Nothing to panic about; they just want to know if you are finding everything without problems.
All of this can be done with relative ease using server logs. A user can be tracked with his IP number, and the different pages requested can be ordered through time to get a very reliable browsing history. What's missing here? Well, you don't know how is it that the user exited the site.
You can easily identify the last page the user visited within your site, but you don't know what the user did next. Maybe he closed the window or tab. Maybe he clicked on an external link. But which one? How do you know where are your users going? Well, now is when things begin to get ugly.
Some websites currently use a wide variety of techniques in order to know exactly where their visitors are going. One that is very easy to identify is when links point to something like http://www.somesite.com/link?id=200 or http://www.somesite.com/link?url="http://www.someothersite.com". You can tell you're not going directly to the place specified, but you are rather being redirected to a special page that will store your click and will then redirect you to the place you wanted to go. Now they know where you went.
Other more devious techniques involve using javascript events to change the URL right after the click, so that visitors will see the correct URL when hovering on the link but will be directed to another page in reality. That's just plain wrong by my book.
These click tracking tricks (try saying that 3 times in a row) slow down browsing, annoy the tech-savvy and completely fool everybody else into doing things they didn't agree on. I wouldn't qualify it quite as spyware, but it's close, and very wrong to say the least. Now is when things get really, really ugly.
Darin Fischer, Mozilla developer and Google employee, has recently blogged about a new, experimental attribute that has been added to anchor tags in the Firefox developer builds. In his words:
Now, let's be very clear: this is currently present only on Firefox developer builds and might never make it to the public, which is part of the reason for today's rant. No sites implement this attribute yet and it's very unlikely that they ever will. You should also read Darin's response to user feedback to form your own opinion about this issue. Now follows my own.
This feature will be labeled as spyware unless it can be easily disabled. The current version can be disabled through a preference and there's no reason to believe it won't always be like that. In the worst case it will be easy to disable it through an extension or a Greasemonkey script, both of which must be in the making as we speak.
Now, if website administrators really want this information to the point of using such ugly techniques as they currently do, why would they rely on such a weak and, may I add with utmost disgust, BROWSER-SPECIFIC feature? They won't. They will continue doing what they do, possibly adding an extra "ping", you know, "just in case". So now we have more unnecessary traffic and the problem hasn't changed at all. Calling Microsoft PR...
The way I see it, this issue is no different than popups. It's a battle between browser makers and webmasters. One wants to give their users the best experience possible, the others want to sell whatever they sell in the best way possible, usually stepping over the rights and comfort of their visitors. Popups must be blocked, and link redirections should be blocked as well. I'm thinking some work could be done with Greasemonkey to prevent this on a per-site basis. I know the problem is very complicated and just as popups, new ways to bypass the protections will be found. Still, I think it's a fight worth fighting and hopefully this will lead to more site administrators abandoning the fight and focus on doing their jobs.
I won't even get started with the WhatWG. You make up your minds. Apparently the word "standard" means nothing to some people. Don't get me wrong, I know standards are driven by innovation, but there's an order to things. If the W3 wants to go with this abomination, fine, let it be a standard and then you can implement it. At least you would have somebody else to blame, instead of giving Mozilla such a bad name.
Because, in the end, all of this is about reputation. "The browser you can trust", remember? A lot of people are seriously angry about this. They may be taking rushed decisions or just being trolls, but in reality a lot of us are disturbed with the direction Mozilla development could be taking. I know (now) that there's a Bugzilla post about this change, but they could have been a little more open about this, considering it is obviously a very controversial feature. A lot of people probably feel they weren't asked about this or they would have complained before. I know I do.
This better not make it out of the experimental phase. It will become Firefox's ActiveX if you continue with it. Enough damage has been done already, bury the damned thing. Leave the unilateral "my standard" making to the unprofessionals.
Some people may wonder what's the point of having such obscure links and not simple straightforward anchors. The answer: user activity tracking. See, most website administrators will gather and store everything they can about your browsing habits, whether you like it or not. Most of it is pretty harmless and helps them improve their service. They identify the most visited pages and give them more importance. The less visited ones are analyzed in order to identify problems or broken links. Nothing to panic about; they just want to know if you are finding everything without problems.
All of this can be done with relative ease using server logs. A user can be tracked with his IP number, and the different pages requested can be ordered through time to get a very reliable browsing history. What's missing here? Well, you don't know how is it that the user exited the site.
You can easily identify the last page the user visited within your site, but you don't know what the user did next. Maybe he closed the window or tab. Maybe he clicked on an external link. But which one? How do you know where are your users going? Well, now is when things begin to get ugly.
Some websites currently use a wide variety of techniques in order to know exactly where their visitors are going. One that is very easy to identify is when links point to something like http://www.somesite.com/link?id=200 or http://www.somesite.com/link?url="http://www.someothersite.com". You can tell you're not going directly to the place specified, but you are rather being redirected to a special page that will store your click and will then redirect you to the place you wanted to go. Now they know where you went.
Other more devious techniques involve using javascript events to change the URL right after the click, so that visitors will see the correct URL when hovering on the link but will be directed to another page in reality. That's just plain wrong by my book.
These click tracking tricks (try saying that 3 times in a row) slow down browsing, annoy the tech-savvy and completely fool everybody else into doing things they didn't agree on. I wouldn't qualify it quite as spyware, but it's close, and very wrong to say the least. Now is when things get really, really ugly.
Darin Fischer, Mozilla developer and Google employee, has recently blogged about a new, experimental attribute that has been added to anchor tags in the Firefox developer builds. In his words:
It is now possible to define a ping attribute on anchor and area tags. When a user follows a link via one of these tags, the browser will send notification pings to the specified URLs after following the link.
Now, let's be very clear: this is currently present only on Firefox developer builds and might never make it to the public, which is part of the reason for today's rant. No sites implement this attribute yet and it's very unlikely that they ever will. You should also read Darin's response to user feedback to form your own opinion about this issue. Now follows my own.
This feature will be labeled as spyware unless it can be easily disabled. The current version can be disabled through a preference and there's no reason to believe it won't always be like that. In the worst case it will be easy to disable it through an extension or a Greasemonkey script, both of which must be in the making as we speak.
Now, if website administrators really want this information to the point of using such ugly techniques as they currently do, why would they rely on such a weak and, may I add with utmost disgust, BROWSER-SPECIFIC feature? They won't. They will continue doing what they do, possibly adding an extra "ping", you know, "just in case". So now we have more unnecessary traffic and the problem hasn't changed at all. Calling Microsoft PR...
The way I see it, this issue is no different than popups. It's a battle between browser makers and webmasters. One wants to give their users the best experience possible, the others want to sell whatever they sell in the best way possible, usually stepping over the rights and comfort of their visitors. Popups must be blocked, and link redirections should be blocked as well. I'm thinking some work could be done with Greasemonkey to prevent this on a per-site basis. I know the problem is very complicated and just as popups, new ways to bypass the protections will be found. Still, I think it's a fight worth fighting and hopefully this will lead to more site administrators abandoning the fight and focus on doing their jobs.
I won't even get started with the WhatWG. You make up your minds. Apparently the word "standard" means nothing to some people. Don't get me wrong, I know standards are driven by innovation, but there's an order to things. If the W3 wants to go with this abomination, fine, let it be a standard and then you can implement it. At least you would have somebody else to blame, instead of giving Mozilla such a bad name.
Because, in the end, all of this is about reputation. "The browser you can trust", remember? A lot of people are seriously angry about this. They may be taking rushed decisions or just being trolls, but in reality a lot of us are disturbed with the direction Mozilla development could be taking. I know (now) that there's a Bugzilla post about this change, but they could have been a little more open about this, considering it is obviously a very controversial feature. A lot of people probably feel they weren't asked about this or they would have complained before. I know I do.
This better not make it out of the experimental phase. It will become Firefox's ActiveX if you continue with it. Enough damage has been done already, bury the damned thing. Leave the unilateral "my standard" making to the unprofessionals.
posted by Villa at
9:38 AM
0 Comments:
Post a Comment
<< Home