|
|
|
|
|
by soapdog
3993 days ago
|
|
You know what? You're right. Defaults are extremely powerful and I haven't thought about that angle. I too would have loved a public, federated and open API for a "read it later" feature but right now we don't have one. The only way to solve this was to build it or bundle some ready made solution. You can ask the Firefox Development team at their mailing list why they chose to bundle Pocket instead of developing a new standard. As for the submission of data, the same could be said for all search engines. A browser is a communication tool, it sends data around. What we need to make sure is that it sends only the data you consent and only when/if you want. Now, lets do a little exercise because you might know more then me about alternatives and I am using this thread to learn new things. If we want a "read it later" feature and we can't build our own, what solution you'd rather have instead of pocket? Is there any other service that you're more comfortable with? If you're not using Pocket and it is not sending any data because you're not using it, having that feature present is actually harming you? |
|
>> If you're not using Pocket and it is not sending any data because you're not using it, having that feature present is actually harming you?
Pocket doesn't "hurt" me, it hurts Mozilla's reputation and it hurts Firefox's less knowledgeable users, particularly because it was made a prominent default. You're handing your users over to a closed source company and not even getting paid for it!
In my opinion if Mozilla was really focused on what it says are its values, it would never have shipped with Pocket integrated like it did. Instead it would have have taken the time and developed the feature in Sync and allowed users like me to host my own. Integrating Pocket to simply rush a feature to get a PR win is the problem.