Hacker News Reader

Comment by drb91 | Hacker News Reader

> Now, tell me how to disable that again?

You can disable it in about:config.

Even better: You can use a Group Policy (Windows) or drop a JSON file in the right place (all platforms) and you're done. https://support.mozilla.org/en-US/kb/customizing-firefox-usi...

extensions.pocket.enabled => FALSE

is what you're talking about, right?

Why the hell is a bloody plugin compiled in with a browser?! I should be able to click "delete" on the plugin screen and purge this trashheap from my system. I shouldn't have to use "hope and prayer" that a plugin isn't used.

Instead, I have to go traipsing in about:config. It's not even in preferences, or plugins, or wherever.

You're better off just going the power user way and making your own user.js file

https://github.com/pyllyukko/user.js

You can use version control, options persist between restarts if you accidentally change something, you can use comments, easily make new profiles that share the same settings

Or you can keep complaining until every piece of software have like 3 options inside a hamburger menu

I happen to agree, but it doesn’t really change much about how I interact with firefox after I disable it.

Have you checked out the alternatives? I remember IceWeasel at one point in Debian.

It's not a plugin, it's a browser feature, like bookmarks and the web inspector.

The line between plugins and features is only useful if it's meaningful. Pocket is, by every appearance, a bookmark service. Why is that integrated into the browser? There's already Firefox Sync. It should be opt-in; I'm in agreement here.

I really like Pocket and use it all the time, but I still agree that it should be offered as a plugin, rather than built-in to the browser.

Pocket is cross-platform whereas Firefox Sync is not. You can still install Pocket for Chrome, etc.

Reply on news.ycombinator.com