Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sure, living with the nuisance of the advertising and UI clutter is an option, as I said. But the fact that they were relatively minor nuisances compared to eg. Windows 11's BS doesn't change the fact that they were still unwelcome and unnecessary and disrespectful.

I don't think there's anything radical about my stance that a new toolbar button showing up—with advertising calling attention to it—integrating a proprietary service into my open-source browser is inappropriate behavior on Mozilla's part.





I found it unnecessary and annoying, but there was a toggle for it in the settings, it wasn't even hard to find.

> Sure, living with the nuisance of the advertising and UI clutter is an option

    about:config<enter>
    extensions.pocket.enabled
set to `false`.

That's how hard that used to be.


Anything requiring messing with about:config is an unreasonable way to treat non-technical users. And the point I've already made that you're ignoring is that the complexity of the workaround is not the problem—the necessity of taking action to disable Pocket is what was most concerning about what Mozilla did.

I simply removed it from the toolbar, same as I did with the Firefox sync icon. Out of sight, out of mind. Granted, they were much more pushy about other features and services. Much less pushy than other vendors and it was, in some respects, understandable. (How do you convince people your product is relevant if they think it does less than the competition because they aren't aware of what's there?)

I found no value in Pocket and it was annoying to have to disable it once per machine but you didn't have to "live with it" as claimed. That's just ridiculously overdramatic.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: