Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Mozilla The Internet Your Rights Online

Firefox 's Ping Attribute: Useful or Spyware? 575

An anonymous reader writes "The Mozilla Team has quietly enabled a new feature in Firefox that parses 'ping' attributes to anchor tags in HTML. Now links can have a 'ping' attribute that contains a list of servers to notify when you click on a link. Although link tracking has been done using redirects and Javascript, this new "feature" allows notification of an unlimited and uncontrollable number of servers for every click, and it is not noticeable without examining the source code for a link before clicking it."
This discussion has been archived. No new comments can be posted.

Firefox 's Ping Attribute: Useful or Spyware?

Comments Filter:
  • Out of control (Score:2, Interesting)

    by RuiFerreira ( 791654 ) on Wednesday January 18, 2006 @11:04AM (#14499427) Homepage
    kind of abusive, no? I'm just imagining slashdotting more than one server... hum? another issue is the pre fetch directive on firefox... i'm starting to think my bandwidth is out of my control..
  • Very useful (Score:5, Interesting)

    by dada21 ( 163177 ) * <adam.dada@gmail.com> on Wednesday January 18, 2006 @11:05AM (#14499447) Homepage Journal
    This feature is extremely useful for any website that wants to give their users better content by parsing what they're going through. It also lets you figure out who is clicking advertisements (which are usually off site) and even gives you the ability to run a multitude of websites but aggregate all the statistics on one of your machines.

    Sure it can be abused -- I don't see why more of these abusive features can't be set up in a whitelist fashion. I'm already shocked that web browsers make it so difficult to white lists sites you feel are safe (or don't mind giving up some information to make your experience better).

    That comes to the point of this post -- how about a standard "setup" logo/button committee that helps create a "setup" web profile that sites can use to give the users options on how they want to be configured? We've got some standard buttons already (RSS feed, etc), why not one that users could be familiar with so that they can white list or opt-in to certain additional "anti-privacy" features?

    I know many websites (including a few of mine) could use more user information, and I don't see why we can't work to just setting a standard for how to do it.
  • Extension (Score:5, Interesting)

    by nes11 ( 767888 ) on Wednesday January 18, 2006 @11:05AM (#14499449)
    This is firefox we're talking about. There will be an extension available within the first day to strip out those attributes. Or even more likely a built-in option to not acknowledge them.
  • by dmoen ( 88623 ) on Wednesday January 18, 2006 @11:08AM (#14499481) Homepage
    I would recommend Firefox be distributed with this option disabled.

    Are you also recommending that Firefox be distributed with Javascript disabled? Because this ping functionality is easy enough to implement in javascript. If ping is disabled by default, then nobody will have it enabled, which means that web developers will continue to do it the old fashioned way, and the ability to disable ping will be worthless.

    Doug Moen.

  • by ivan256 ( 17499 ) * on Wednesday January 18, 2006 @11:09AM (#14499486)
    Does this feature track and retain your surfing habits without your consent?

    No.

    Can you not opt-out of it?

    Disable the feature. Easy.

    It's not spyware by your definition. It has the added benefit of giving the user some control instead of being secretly tracked by the server side.
  • by suso ( 153703 ) * on Wednesday January 18, 2006 @11:12AM (#14499517) Journal
    What I'm saying is that just because you thought of something neat, you shouldn't just implement it (and I know that this isn't how it happens of course). Cookies and javascript weren't just implemented. A lot of thought went into how they could be used, abused, what the gotchas are and how to solve them. Test models were done and analyzed. This seems like the kind of feature that is comparable to that level of change in the way browsers work. I wonder if the WhatWG people really tested the concept and implementation that much.
  • Re:Out of control (Score:3, Interesting)

    by peragrin ( 659227 ) on Wednesday January 18, 2006 @11:16AM (#14499559)
    Actually I kind of like it. With this tool Slashdot could finally Slashdot all the advertisers in one shot. Talk about a major DDOS.

    Create a link with an image to a story site. Embed that link with this. You could slashdot The big sites with this. Go Open Source innovation.
  • Don't worry yet (Score:5, Interesting)

    by courtarro ( 786894 ) on Wednesday January 18, 2006 @11:19AM (#14499595) Homepage
    "Quietly" refers to Mozilla's inclusion of this feature in the nightly trunk versions, not the official version available for download. That's hardly cause for concern. I'll bet most of the features added to nightlies are "quiet", so that's just a bit of fear mongering. It's a development version! I personally don't like the idea of pings that much, but I'm willing to bet it will have a UI to allow disabling when it's released to the masses. According to the bug request to implement it [mozilla.org]:

    We should try and do an experimental implementation of , to see if there are any unexpected real-world problems.

    That's what nightlies are for! We now see that it's a controversial tag (and they're probably already well-aware), so they're giving it a shot. Would you rather them just say "no, we don't like that potential standard [whatwg.org], so we're not going to try implementing it"?
  • by SmallFurryCreature ( 593017 ) on Wednesday January 18, 2006 @11:19AM (#14499598) Journal
    I click a link in a slashdot article to an external site and slashdot is notified about this. Mmm, okay. I can see that it might be considered usefull for deteriming how people use their website.

    It could enable a user comments vs people who actuall RTFA statistic. Knowing slashdot it would crash on a divide by zero error offcourse.

    But wait a minute, a infinite number of pings? So the story submitter himself can also add his pings? Knowing the quality of slashdot editors (HA!) any story submitter would know who read what links in his article. Do I want him to know?

    Imagine that someone puts a goatse.cx link on a forum. You don't of course admit that you been tricked but the next post is a record of all the pings the link submitter received proving that all of slashdot wanks to the goatse man.

    The abuse of this feature is clear and the benefits? If slashdot really cared to know wich external links are followed or not then that is their business isn't it?

    Do I really want websites to know wich external links I follow? I think this is a solution looking for a problem and in the few cases where a website needs to know the users need for privacy is superior.

    Bad mozilla. This is something I would have expected of MS or the old Netscape. Now go sit in a corner and don't come out until you stop adding crap features that tattle on me without informing me.

  • by Hurga ( 265993 ) on Wednesday January 18, 2006 @11:25AM (#14499645)
    Are you also recommending that Firefox be distributed with Javascript disabled?

    I know that I HAVE JavaScript disabled (using the NoScript extension) for this and other reasons, and I don't want to have that functionality back whithout me noticing.

    Hurga
  • Why would a web developer use the ping attribute now? AFAIK only Firefox supports it.
  • Possible fix (Score:5, Interesting)

    by spitzak ( 4019 ) on Wednesday January 18, 2006 @11:29AM (#14499683) Homepage
    Why not limit the ping to the server that made the current page? This should prevent people from embedding pings into blogs, and still allow the replacement of redirects for tracking where you go. I would think unless this is done, too many people will disable it for any real sites to use it, and it will *only* be used for nefarious purposes.
  • by Anonymous Coward on Wednesday January 18, 2006 @11:31AM (#14499716)
    We aren't talking about a low-level ping here - the "ping" locations are URLs to which a request will be issued. There's no reason for them to go via any route other than your normal HTTP proxy, if you use one.

    From the WHATWG spec [whatwg.org]:

    For URIs that are HTTP URIs, the requests must be performed using the POST method (with an empty entity body in the request). User agents must ignore any entity bodies returned in the responses, but must honour the HTTP headers -- in particular, HTTP cookie headers.


    It's a literal replacement for the current habit of links passing through a traffic stats site before redirecting you to where you actually wanted to go. It won't waste any more bandwidth, since browsers - according to the spec - MUST ignore any entity that is returned. The only productive thing you can do is log the fact that the ping URL was visited, and drop a cookie on the client - just as with an HTTP redirect.
  • Re:This stinks, Why? (Score:3, Interesting)

    by LWATCDR ( 28044 ) on Wednesday January 18, 2006 @11:33AM (#14499728) Homepage Journal
    I find this so odd. What is wrong if I want to see how many people click a link on my website? I can think of a lot of none evil uses for it. Think of it like P2P why should you eliminate a perfectly useful technology just because it can be abused?
  • by Bogtha ( 906264 ) on Wednesday January 18, 2006 @11:34AM (#14499731)

    How is this different from the web server logging every page and image you load?

    It's different because web server logs only record what you ask that server for. Web server logs don't record what you ask other servers for.

    This is essentially what the Referer header does, except in reverse. Instead of telling a new server where you have come from, it tells the old server where you are going.

    This is already possible with Javascript, and it was possible with CSS too - I'm not sure if it still is, but the technique was basically to suggest a local background image to style :active links - so when the link becomes :active (when it gets clicked on), the browser downloads the background image and you know the link was clicked.

  • by Kozz ( 7764 ) on Wednesday January 18, 2006 @11:37AM (#14499762)
    Sure, the basic functionality can be duplicated with javascript. However, tying this behavior explicitly to a "ping" attribute makes it much easier to identify and block/disable the behavior. If someone doesn't want to mess around with a NoScript extension, script whitelists, etc... then this makes life easier.

    Look at it this way: I'm lazy. I don't want to be a security/privacy Nazi about any/every script on webpages I view. However, if there's an "easy" way to block something I view as potentially abusive, this ping attribute could easily be disabled.

    Which makes me think that if other users are lazy like me and just want to disable "ping", this feature would likely be dead-in-the-water, and designers who want to track users would continue to use Javascript.
  • by 9-bits.tk ( 751823 ) on Wednesday January 18, 2006 @11:41AM (#14499800)
    If they're going to go any further with the "ping" feature, there should be a function (enabled by default) that prompts you before pinging the servers.
  • Trust Firefox? (Score:2, Interesting)

    by saberworks ( 267163 ) on Wednesday January 18, 2006 @11:51AM (#14499874)
    Personally, I don't trust Firefox anymore. No matter how many times I disable "check for updates" it keeps checking for updates. No matter how many times I tell it to stop checking automatically for updates or upgrades for my extensions, it refuses to stop. Yes, I have used the preferences. I have tried manually setting them with about:config. Nothing will make it stop checking. This has been happening since the 1.5 beta and is persistent in 1.5 final.

    It also appears to be impossible to install it without the "report to your master" feature (which is supposed to report crashes). It can be disabled (supposedly) later, but in the install you used to be able to uncheck it, now it's grayed out and gets installed by default every time.

    Then there's the whole automatically prefetching links that you MAY click on in order to "speed up" the browsing. There's no way to tell if it's even doing this unless you are watching your network connection carefully, but it's ridiculous and it's hard to make it stop.

    No application should be using the network connection without my explicit permission on each and every action. Typing a URL or clicking a link is permission, I'm TELLING it to go fetch that data. But doing crap in the background without asking me is just dishonest.
  • by Roadkills-R-Us ( 122219 ) on Wednesday January 18, 2006 @12:08PM (#14500047) Homepage
    I agree that would be the reason to enable it.

    But it's a lousy scenario. There shouldn't *be* expensive, hidden redirects, and we're just encouraging what I consider (at best) stupid. even (worse) anti-social, possibly evil behavior.

    I'm completely in favor of progress, but it seems the net is always taking at least one step back (in some cases a few dozen) for every step forward.

    We should be encouraging content providers to produce clean web page sthat do what we expect them to do, simply, instead of to be ever more complex, sneaky, tricky marketing tools. or worse.
  • Thanks! (Score:2, Interesting)

    by etymxris ( 121288 ) on Wednesday January 18, 2006 @12:08PM (#14500055)
    I never realized before why URLs wouldn't show up in the status bar on fark. After reading your comment, though, I allowed javascript to change the status bar and the issue was fixed. I think in the case of fark they aren't trying to be sneaky so much as user-friendly. The redirect URLs are unreadable because of the URL-encoding of the link destination. I don't particularly care that fark knows when I click an external link from their site, but I do enjoy the ability to see a readable URL by hovering over links with the mouse.
  • by SethJohnson ( 112166 ) on Wednesday January 18, 2006 @12:12PM (#14500092) Homepage Journal
    Why would a web developer use the ping attribute now?

    I think the main developer who would want to use it is Google with their adwords program. They're probably trying to minimize the bandwidth those redirects consume for all the clicking that happens on their ads. This is on top of the bandwidth of every page view requesting the ads to be embedded in the first place, which can't be avoided...

    Even if Google can shave off 6% of unneccessary redirects (all Firefox users), that's a big bandwidth savings.

    Seth
  • by Quixote ( 154172 ) * on Wednesday January 18, 2006 @12:31PM (#14500265) Homepage Journal
    Relying on the user to submit the right statistics is asinine. No company will trust user-submitted stats ("I stayed on your web page and read every word...lol"). This is why redirects are essential: the site owner has concrete numbers about the clicks.

    Once again, Firefox/Mozilla folks are showing their arrogance (anyone else remember "blink"?). When their marketshare was down, they would never have done such a thing; but now that their marketshare is noticeable, they are back to their old ways.

    If Microsoft had done this, everyone would be up in arms about their "embrace and extend". Why isn't there a hue-and-cry about Firefox "extending" things unilaterally? Oh, I know why: because the almighty Google backs FF now.

  • by SilverspurG ( 844751 ) * on Wednesday January 18, 2006 @12:35PM (#14500300) Homepage Journal
    You would think so. Starting with cookies, though, there's always been a major component of web design and development which hinges on deliberately obfuscating important events from the user.

    I don't want to get too heavy into tin-foilery over this. It would be difficult to support a claim that these pings and cookies are used for anything but the most innocuous of data mining and profiling pursuits. Here is where a natural danger sense comes into play, though: if people are being so careful not to draw attention to the extra activities of the software then just what are they hiding?
  • by mfg ( 16466 ) on Wednesday January 18, 2006 @01:02PM (#14500662)
    > what's wrong with the gnome file dialog?

    The most obvious problem is that, unlike the old
    XUL file browser, they don't use the current Firefox
    theme. This makes them look completely out of place
    on screen.

    More importantly, the design of the new file browser
    is fundamentally broken; it's been dumbed down to the
    point of unusability. There's no obvious place to type
    filenames rather than using the mouse, the display of
    the directory tree is non-standard, clicking on
    "Browse for other folders" in the save dialog triples
    the size of the window and often moves the cancel/save
    buttons off the bottom of the screen, etc.

    The disaster that is the new GTK file browser is the
    main reason that I'm still using GTK1 versions of
    Mozilla etc.
  • by gr8_phk ( 621180 ) on Wednesday January 18, 2006 @01:05PM (#14500707)
    "I think the main developer who would want to use it is Google with their adwords program. They're probably trying to minimize the bandwidth those redirects consume for all the clicking that happens on their ads.

    Google gets paid for those clicks on their ads. They don't need to be altering my browser to help their business anyway. As bender would say, Google can bite my shiney metal 4$$. Hopefully distros will patch firefox, so their users won't need to fret about this. Just those windows users who get it straight from the firefox site.

    I've been thinking it's time for a firefox fork that drops the MPL. The dual licensing is preventing integration of other GPLed work - like a built in PDF viewer so we can avoid Adobe. A GPL only fork would help prevent folks like Google from creating their own branded browser with stupid features no user would ever want.

  • by jacksonj04 ( 800021 ) <nick@nickjackson.me> on Wednesday January 18, 2006 @01:18PM (#14500862) Homepage
    This is an important point. An AJAX application will quite merrily send and recieve large quantities of data without you knowing - this is by design. It relies on being able to do things 'behind the user's back'.

    Think of it this way - if you had a popup every time a local application wanted to communicate with the hard disk, how quickly would you become angry?
  • by jlarocco ( 851450 ) on Wednesday January 18, 2006 @01:29PM (#14501031) Homepage
    I'm racking my brain to imagine why a user would ever want to enable it.

    Nobody would ever go out of their way to enable it. I don't know of anyone ever requesting this "feature." And it's not in any HTML, XHTML, Javascript, or CSS standards. So why the hell did they add it? I would expect this from Microsoft, but I'm a little surprised that Firefox is doing it.

  • by JourneyExpertApe ( 906162 ) on Wednesday January 18, 2006 @02:20PM (#14501700)
    The difference is that JavaScript linking becomes obvious by looking at the status bar. In this case, you just see the destination URL. Maybe FF could put "(ping <list of servers>)" at the end of the status bar text.
  • by Kitsune78 ( 941644 ) on Wednesday January 18, 2006 @02:39PM (#14501907)
    Communication between an application and my hard drive should not result in data leaving my immediate "control zone" (or at least one would hope). That same sort of activity occuring over a public network to an unknown destination is more insecure by orders of magnitude.

    Your point is valid that AJAX functionality poses many of the same issues as this Firefox "feature", but I politely refute your hypothetical example.
  • by SilverspurG ( 844751 ) * on Wednesday January 18, 2006 @03:12PM (#14502371) Homepage Journal
    I know that this will be extraordinarily out of the box type thinking which was discarded back around '95 when the intarweb was used to create a huge marketing bubble...

    Use your imagination and come up with something which doesn't involve HTTP and port 80. I know, it's tough because there's so little out there. Looking at the internet today one would think that HTTP and port 80 were the whole reason behind designing desktop computers.

    And, again... what functionality does this new ping give to _ME_, the user who bought this hardware and is paying the electric bill to run this browser? If I were to talk with the author of the code for this little snippet what explanation would he be able to give to justify that _I_, the user, want this?
  • by Anonymous Coward on Wednesday January 18, 2006 @04:20PM (#14503239)
    >
    > AJAX is faster because there are fewer page loads.
    >

    You do know about browser cache, don't you?

    For the page in itself, if most webpages weren't composed half of useless JavaScript (be it advertising or not), HTML tables used for design and deprecated tags/attributes, I guess we would not need to limit page loads.

    >
    > The ping will help reduce page loads as well. Only headers need be exchanged when you use the ping,
    > instead of loading some shim graphic to handle hit tracking, which people will do with or without ping.
    >

    Better yet: do not track users and care for your content instead. Web server logs are way enough for the only legitimate purposes there are to keep stats: manage your server bandwidth and maybe check if what you are writing/serving, has been read/saw/heard by many or few. You should not care about anything else.
  • by cduffy ( 652 ) <charles+slashdot@dyfis.net> on Wednesday January 18, 2006 @04:50PM (#14503595)
    What functionality does this give to me, as a user, that couldn't be entirely implemented on the server side without requiring anything to happen behind my back?

    The alternative is the same stuff happening on the client side, as it is right now, but through more user-hostile means. Think hidden frames and DIVs, transparent GIFs, JavaScript being used to make arbitrary requests, and all that junk.

    ping gives a less user-hostile alternative to all of that miscellany -- and one that the users can actually easily turn off. It's a Good Thing. Embrace it.

  • by jlarocco ( 851450 ) on Wednesday January 18, 2006 @05:10PM (#14503835) Homepage

    Sure, but XMLHttpRequest is actually helpful and useful, as GMail shows. If XMLHttpRequest was turned off, most people would turn it on. I can't think of any use for this "pinging" other than to track internet usage. If it were turned off, I think most people would keep it that way.

    My point is, the Firefox dev team is adding useless features that nobody really wants (except maybe DoubleClick), when there are other more important things they could be working on. How about passing the Acid2 test? Or how about optimizing the download size? Or decreasing start up times? None of these things are really important, but I think for most people they'd have higher priority than this "pinging."

The key elements in human thinking are not numbers but labels of fuzzy sets. -- L. Zadeh

Working...