Live data from Hacker News

Firefox Bugzilla: Remove Pocket Integration

bugzilla.mozilla.org

21–30 of 196 posts

Re: Firefox Bugzilla: Remove Pocket Integration

#21
post #2

This bug report is not really clear. Does the submitter consider it bloat, or a privacy violation, or what? It should be obvious that the way it appears in Developer Edition (two releases ahead of "release") is not the way it will appear in the final version. This report should be about the way the feature is explained to the user, or about how hard it is to disable the feature, so that it can be improved.

At least in my opinion, it's unnecessary bloat - just like that video chat thing they added a couple months ago.

Remember when Firefox, the lean, scrappy browser, first came out and ran circles around the bloated Netscape browser/HTML editor/IM client/mail client/newsreader? The Firefox team seems to have forgotten.

If anyone is maintaining a "Firefox: Browser Only Edition" fork, I'd love to know about it so I could use that instead.

Re: Firefox Bugzilla: Remove Pocket Integration

#23
post #11

What I don't understand is that Firefox also include its own read later service that sync to Firefox users account. Are they planning to drop its own implementation and partner with Pocket?

It has a read later service? There's a new Readability button but it doesn't seem to sync anything. Edit: according to chimeracoder, there was one in Nightly for a little while but it was removed.

Re: Firefox Bugzilla: Remove Pocket Integration

#26

It is so unlike Mozilla to introduce something like that, I ran a virus scan and checked what programs had been installed recently -- I assumed it had been put there in the same way that IE users used to get the Ask Toolbar installed. Exactly how I felt. What the hell were they thinking? I'm generally very supportive of Mozilla, I even supported their initiative to put advertisements on Firefox's start page. But bund…

You really start to wonder what pot they are smoking over there at Mozilla. Standard things you would expect from a browser, like a way to easily disabling javascript are apparently left to third-party extensions, because oh you don't want to bloat the browser. But hey, video conferencing on the other hand is such an essential part of the browsing experience.

Re: Firefox Bugzilla: Remove Pocket Integration

#27
Since all of the comments on this page so far seem to be opposed to the integration:

I love Firefox's "Reader View". It's the only way that some pages are readable on my desktop or mobile device, because so many websites try to hijack scrolling, insert modal overlays and ads, or do all sorts of things that make it unbelievably frustrating to just read static text.

On the other hand, Reader View lacks a sync feature. There was one for a few days in Nightly, but it was buggy for the short time it existed, and it was removed.

I was hoping Firefox would improve the sync feature and bring it back eventually, but in all honesty, this is way better. The work that goes into making a seamless, syncing reader view is not trivial[0], and it makes more sense for Mozilla to focus on building a browser than to reinvent the wheel when Pocket already exists and works incredibly well with the same use case.

As for whether this should be "bundled" into the browser vs. an extension: I agree that it would be nicer philosophically if Pocket were a preinstalled extension. On the other hand, Firefox Hello is literally a preinstalled extension with no special integration or privileges (other than being preinstalled), and still some people made the same complaint about it when it launched[1]. So I take that complaint with a grain of salt.

And as for the performance impact of either, I'd have to see some data demonstrating that this actually leads to an appreciable (let alone measurable) increase in memory or CPU usage to be convinced that simply not using it is not an acceptable alternative.

[0] it may look that way, but there are a lot of corner cases

[1] From what I understand, Firefox Hello is simply an extension that leverages WebRTC features already built into the browser to enable video chat (with the assistance of a service provided by Telefonica, which assists in the routing).

Re: Firefox Bugzilla: Remove Pocket Integration

#29
post #2

This bug report is not really clear. Does the submitter consider it bloat, or a privacy violation, or what? It should be obvious that the way it appears in Developer Edition (two releases ahead of "release") is not the way it will appear in the final version. This report should be about the way the feature is explained to the user, or about how hard it is to disable the feature, so that it can be improved.

At least in my opinion, it's unnecessary bloat - just like that video chat thing they added a couple months ago. Remember when Firefox, the lean, scrappy browser, first came out and ran circles around the bloated Netscape browser/HTML editor/IM client/mail client/newsreader? The Firefox team seems to have forgotten. If anyone is maintaining a "Firefox: Browser Only Edition" fork, I'd love to know about it so I could…

icecat, follows gnu teachings

waterfox, pale moon, also exist

https://en.wikipedia.org/wiki/List_of_web_browsers#Gecko-bas...

Re: Firefox Bugzilla: Remove Pocket Integration

#30
post #26

It is so unlike Mozilla to introduce something like that, I ran a virus scan and checked what programs had been installed recently -- I assumed it had been put there in the same way that IE users used to get the Ask Toolbar installed. Exactly how I felt. What the hell were they thinking? I'm generally very supportive of Mozilla, I even supported their initiative to put advertisements on Firefox's start page. But bund…

You really start to wonder what pot they are smoking over there at Mozilla. Standard things you would expect from a browser, like a way to easily disabling javascript are apparently left to third-party extensions, because oh you don't want to bloat the browser. But hey, video conferencing on the other hand is such an essential part of the browsing experience.

They don't let users easily disable JS because that breaks so many webpages, and they didn't want to deal with supporting users who complained that Firefox wasn't working. http://limi.net/checkboxes-that-kill/
Post reply on HN