Quote:
i'd actually already set the value to zero, but i decided to give the extension a shot and it's great in the sense that you can do some stuff on-the-fly that are a pain in the ass to hunt down and change manually, thanks for the advice. i'm paranoid about extensions since if you don't like it, firefox does a lousy job at uninstalling them completely, which sucks when the supposedly uninstalled extension that broke some other function left the problematic values in your registry.this one's a keeper so far though.
Well, you can always don your super-geek cape
and edit extensions.rdf to get rid of extensions. Carefully. After making a backup.
There are a few websites that need referrer logging to work right (sometimes the Add-to-Cart button uses the referrer URL to know what to add to the cart). So setting it manually to zero always might be a problem.
Quote:
my gripe with the calling home thing is not only is it a step away from why firefox, k-meleon, etc. were created but also that just unchecking the box doesn't totally disable the function. from what i can figure out, it looks like all it does is really disable the notifications, so it's sending the data unless you turn it off outside of the normal options menu. probably harmless, but i don't see any reason for it.
I'd post this as a question to developers if not already discussed in Google. It's something they'd take seriously.
A quick sniff of an update cycle says nothing is being sent for extension or theme updates. Merely checking for an update it not harmful; trusting an update offered as a result of this is where the risk lies.
FireFox itself is doing its update under SSL so I can't see what's there but there does seem to be a lot of data involved, far more than I'd expect. I'd have to pull down the source code to see what's happening (assuming FireFox isn't written in some exotic language).
_________________________
"If they can't picture me with a knife, forcing them to strip in an alley, I don't want any part of it. It's humiliating." - windsock