EDIT: for anyone who doesn't think it wasn't about money, please explain why it is so difficult to remove, why I have to open about:config to "disable" (not remove) it, and why it wasn't just added as an add-on (which already existed)?
EDIT: for anyone who doesn't think it wasn't about money, please explain why it is so difficult to remove, why I have to open about:config to "disable" (not remove) it, and why it wasn't just added as an add-on (which already existed)?
the integration does not collect personal data until the user opts in, and it does not consume memory beyond loading the image from disk until the user opts in.
meanwhile, that search bar up at the top is an integrated browser function (not even an add-on) that sends personal data to a 3rd party, closed source server.
> please explain why it is so difficult to remove
you remove it just like every other thing in your toolbar: click the menu button, drag it off of the toolbar.
> Mozilla has now begun changing the default
like when they added bookmarks, search, download menu, spaces, and countless other functions? that's literally what browser vendors do.
All of those features either work offline or use Mozilla's own services as opposed to third party services.
The only exception I can think of at the moment is search which should also be provided through add-ons in my opinion because I don't use it - I go directly to Google website and search there.
This is no different from the integration with Google or Yahoo. The Firefox-side code is not proprietary. It doesn't consume resources if you're not using it.
You can remove it via the customizeable UI feature too.
I've seen Firefox employees stating that there was no money involved.
Edit: Checking more closely, something like that: http://getpocket.com/blog/2009/08/reading-it-later-two-years...
So it does sound likely that Pocket was well known.
I think the integration is useful, and I've used it quite a bit. It's a lot better (faster, more reliable) than pocket's old extension.
Do we really want Mozilla to go that way though?
Just for comparison, Chrome has chunks of closed source code, including the binary blob that is downloaded on first run to enable listening for "OK Google". This add-on is pre-installed. And it's pre-installed to make Google more money.
And I think comparing Firefox to Chrome is just legitimizing the argument; Firefox markets itself essentially as the opposite of most of the things Google does. "It's okay because Chrome does it" doesn't make me feel very good about Firefox.
I only referenced Chrome because the post I responded to specifically mentioned Chrome for comparison.
Not very reassuring. Do you suggest i make a daily reminder to check the Firefox source code to check whether the implemented privacy invading code still "isn't executed" ?
Yes it is. They have started to sell users just like everyone else.
> (4) Individuals’ security and privacy on the Internet are fundamental and must not be treated as optional.
Google, Pocket, etc. are arguably not compatible with this manifesto, because their business model is precisely to sell user data.
So Mozilla says it respects and defend your privacy but makes deals with companies that won't. I'll let you pick a name for that kind of behaviour.
The issue here is about the reason why it was included _as a default_ in the first place.
right-click, "Remove from toolbar". There you go.
In fact, visiting a website is considerably worse. The code may be quite large, and it's not vetted in any way (unlike the pocket plugin), so it might try to escape the sandbox.
If you're going to get fed up about this, at least have some reasonable basis for that. You might complain about the increased download size or disk usage (but the overhead is likely to be ridiculously small). You might complain about the attention pocket - a non free service - gets this way. Of course, this isn't too different from a default search engine. And did you know about https://activations.cdn.mozilla.net/en-US/?
At the end of the day, is your feeling based on anything other than a grumpy gut?
Mozilla has clearly positioned itself as (1) the independent browser-vendor who cares about (2) open source, (3) the open web and (4) your online privacy.
If they start bundling "free" proprietary third-party services, where the price is a piece of the user's privacy, to provide a more seamless experience at the cost of bypassing "normal" rules for web-application integration, they have effectively compromised themselves on all 4 of those criterias.
This one incident is not the end of the world to me, but I've had this feeling for quite a while that Mozilla is losing both direction and momentum, and stuff like this helps cement it.
Had it not been proposed as a joke, I would already be looking forward to those Emacs-patches incorporating Webkit as the new embedded browser.[1]
[1] Embedding Webkit was proposed as a "solution" to the famous Emacs-quote "Eight Megabytes And Constantly Swapping"[2] no longer being valid or relevant.
They were positioned that way, but ever since they gutted the security of Sync[1], it's really hard to take them seriously.
[1] First, your data is now 'secured' on their servers solely by your password, which for most people is memorable and thus breakable; previously it was secured with a high-entropy key, which was secured on your system with a memorable password, if desired. Second, login to their services (which uses that same God password) is performed by downloading JavaScript (and perhaps HTML and/or chrome; I forget now) from their servers, which means that they can at any time choose to intercept as few or as many user passwords as they wish—or as someone with legal authority wishes them to.
> Had it not been proposed as a joke, I would already be looking forward to those Emacs-patches incorporating Webkit as the new embedded browser.
I thought that there was a serious effort to do that. It'd be great IMHO.
Like search engines? Terrible reasoning. Browsers need these or they won't be competitive. There was a judgment call that a read later mode is needed to be competitive, too. We can argue whether it's the right call, but not about the above.
I don't get how that follows...like, at all. The same kind of weird reasoning can be used for setting a default search engine or sending back crash reports, telemetry or even update checks. We understand that some features of the browser have a privacy impact in return for user friendliness. It's not like they aren't upfront about that.
In all cases, you don't get the impact if you don't use the feature. The original post tried to say there was still some impact from having the JS sit unused on disk. That's just bullshit!