4 ms·

What's wrong with Pocket?

by jacobr 9y ago

michaelt 9y ago
The fact it ought to be an extension that pocket users could add by visiting addons.mozilla.org but instead it was rolled into the core browser. People assume Pocket offered Mozilla a lot of money, as there's really no other reason Pocket shouldn't be an extension. People are naturally nervous when browsers start deploying third-party code in exchange for cash. Especially when auto-update mechanisms are used. Some would see that as an important line to cross - will they be able to resist the much larger sums they'll be offered to "help users see more relevant ads" and "help users keep safe from viruses"?
- oatmealsnap 9y ago
  Mozilla owns Pocket, though. It's more of a bookmarking UI/service than a 3rd party add-on. Sort of like Safari's Reading List feature. That's how I've always seen it anyway. I didn't know there was controversy around it, but I can understand how people would be sensitive to seeing another company's logo in the URL bar.
  - bpeebles 9y ago
    Mozilla bought pocket early this year. The pocket integration was before that in mid-2015.
crankylinuxuser 9y ago
It makes a fine browser extension. It ABSOLUTELY does not make good embedded code. There is no good reason for it to be "core functionality" in a browser, other than the fact that Moz://a got a fistfull of dollars and foisted it upon us. EDIT: For example, what would be a good use of core functionality, is if Moz://a included IPFS resolution and native support. That is a protocol level support, and thus would need native support rather than plugins. Plugins do indeed work, but require significant workarounds. For example, native could be ipfs://hash whereas the plugins need to specify http://127.0.0.1:8080/ipfs/hash http://127.0.0.1:8080/ipfs/hash
- jacobr 9y ago
  I respect that everyone does not want it in their browser, but you could also say that about developer tools, screenshots, even bookmarks are not "core browsing". By this point Pocket is just another feature, fully owned and developed by Mozilla.

What's wrong with Pocket?

by jacobr 9y ago

What's wrong with Pocket?

The fact it ought to be an extension that pocket users could add by visiting addons.mozilla.org but instead it was rolled into the core browser. People assume Pocket offered Mozilla a lot of money, as there's really no other reason Pocket shouldn't be an extension. People are naturally nervous when browsers start deploying third-party code in exchange for cash. Especially when auto-update mechanisms are used. Some would see that as an important line to cross - will they be able to resist the much larger sums they'll be offered to "help users see more relevant ads" and "help users keep safe from viruses"?

oatmealsnap 9y ago
Mozilla owns Pocket, though. It's more of a bookmarking UI/service than a 3rd party add-on. Sort of like Safari's Reading List feature. That's how I've always seen it anyway. I didn't know there was controversy around it, but I can understand how people would be sensitive to seeing another company's logo in the URL bar.
- bpeebles 9y ago
  Mozilla bought pocket early this year. The pocket integration was before that in mid-2015.

crankylinuxuser 9y ago

It makes a fine browser extension. It ABSOLUTELY does not make good embedded code. There is no good reason for it to be "core functionality" in a browser, other than the fact that Moz://a got a fistfull of dollars and foisted it upon us. EDIT: For example, what would be a good use of core functionality, is if Moz://a included IPFS resolution and native support. That is a protocol level support, and thus would need native support rather than plugins. Plugins do indeed work, but require significant workarounds. For example, native could be ipfs://hash whereas the plugins need to specify http://127.0.0.1:8080/ipfs/hash http://127.0.0.1:8080/ipfs/hash

jacobr 9y ago
I respect that everyone does not want it in their browser, but you could also say that about developer tools, screenshots, even bookmarks are not "core browsing". By this point Pocket is just another feature, fully owned and developed by Mozilla.