I can't read your link unfortunately (get an SSL error when trying to connect), but that's interesting, given the sheer amount of trackable requests firefox makes silently in the background (like safe search/content blacklists from google, etc). Based on the goals stated by the iceweasel project, I assume they have not patched those things (as their goal is to be firefox-without-trademarks and nothing more).
I'm really disappointed in mozilla's track record on privacy. They always seem to choose features over privacy. See for example all of the patches sent by the Tor Browser developers for various info leaks that have been rejected as they would be inconvenient for average users.
It really seems quite pointless to work on a leak like this when there's so many others in the upstream that they refuse to patch (even if they have understandable reasons).
> See for example all of the patches sent by the Tor Browser developers for various info leaks that have been rejected as they would be inconvenient for average users.
I wasn't aware of this, what kinds of leaks are you talking about? Care to supply us with some references?
That's a list of the original planned features for the TBB. You can clearly see they intended it to be a temporary thing until patches were pushed upstream, but it's still around and still adding new patches to fix leaks. You might try to search for the tickets for the issues above in the mozilla bugtracker and you will see many WONTFIXes.
I'm really disappointed in mozilla's track record on privacy. They always seem to choose features over privacy. See for example all of the patches sent by the Tor Browser developers for various info leaks that have been rejected as they would be inconvenient for average users.
It really seems quite pointless to work on a leak like this when there's so many others in the upstream that they refuse to patch (even if they have understandable reasons).