Live data from Hacker News

Mozilla to shut down Pocket and Fakespot

support.mozilla.org

581–590 of 782 posts

Re: Mozilla to shut down Pocket and Fakespot

#581
post #249

I was a user for so long that I was on it before it even rebranded as Pocket. I finally gave up on it last year, mostly due to frustration with the terrible 2023 redesign of the mobile app. When Mozilla made the unfathomable decision to become an internet advertising company, I figured it was just a matter of time before they had to put Pocket out to pasture. A product that's designed to strip ads from content for re…

> available in every other browser Isn't it because almost every "other browser" reuses the Chromium engine? Or is Firefox trailing even mobile Safari here?

Ever since Microsoft announced Edge was going to use Chromium, I've been wondering why Firefox doesn't do the same. By adopting the same renderer as everyone else, consumers get a consistent rendering experience and Firefox devs can focus on the features that keep us using Firefox.

Re: Mozilla to shut down Pocket and Fakespot

#582
post #543

When Mozilla got Pocket, they advertised it all over Firefox to increase adoption. Back then, I was like "but I already have a bookmark feature". Over all these years I have hidden the Pocket button away because for most people there's no strong incentive to switch from a normal bookmarking solution (and now, with only a hand full of websites in major use, even bookmarks have lost all meaning). Good riddance?

+1, my only interaction with Pocket is annoyance that I had to remove it from my toolbar every time I've installed Firefox on a new computer. Good riddance.

Re: Mozilla to shut down Pocket and Fakespot

#583

Earlier quoted context omitted.

I'm curious what the governance structure of Mozilla is that keeps things this way. People have been upset for quite a while at the direction Mozilla is going in, yet there seems to be no coalition to oust the current leadership. Is this impossible for some reason?

The leadership has been ousted. > This includes major growth in our Boards, with 40% new Board members since we began our efforts to evolve and grow back in 2022. We’ve also been bringing in new executive talent, including a new MoFo Executive Director and a Managing Partner for Mozilla Ventures. By the end of the year, we hope to have new, permanent CEOs for both MoCo and Mozilla.ai... With these changes, Mitchell B…

That doesn't sound like she and her fattened board were ousted at all.

Re: Mozilla to shut down Pocket and Fakespot

#584
post #249

Earlier quoted context omitted.

> available in every other browser Isn't it because almost every "other browser" reuses the Chromium engine? Or is Firefox trailing even mobile Safari here?

> Or is Firefox trailing even mobile Safari here? Short answer: yes. Here are some web platform features Chrome and Safari (desktop and mobile) are shipping but not Firefox: * Container Style queries: https://web-platform-dx.github.io/web-features-explorer/feat... * @scope: https://web-platform-dx.github.io/web-features-explorer/feat... * Picture in Picture: https://web-platform-dx.github.io/web-features-explorer/fea…

[deleted]

Re: Mozilla to shut down Pocket and Fakespot

#585

I really enjoyed https://waldenpond.press/ when it was up and running. They selected articles from your pocket once a month and then printed, bound, and mailed them to you. When I discovered the service I had a 500 hour reading backlog, and for $14/mo I was getting 100+ page books of self-curated content. They were perfect for flights, trips, and lending out. I was able to force it to include recipes as well, and I s…

Wow this is so neat.

Re: Mozilla to shut down Pocket and Fakespot

#586
post #272

I built Obsidian Web Clipper (open source, MIT) to replace my read-it-later app and save everything to local markdown files. Now that Obsidian Bases is available, it makes for a very nice web archival tool and reading experience. Here's a video: https://mastodon.social/@kepano/114553164915046938 You can use Web Clipper with any app that supports Markdown, not just Obsidian. Defuddle is the underlying HTML-to-Markdown…

Do you have a trick for getting the images as well, as opposed to them being links to the remotely hosted?

Obsidian recently introduced a native 'Download attachments for current file' which you can invoke with cmd / ctrl + p.

I like this as I don't always want all the images for something I've clipped from the web. This gives me the choice.

Re: Mozilla to shut down Pocket and Fakespot

#588

I was a user for so long that I was on it before it even rebranded as Pocket. I finally gave up on it last year, mostly due to frustration with the terrible 2023 redesign of the mobile app. When Mozilla made the unfathomable decision to become an internet advertising company, I figured it was just a matter of time before they had to put Pocket out to pasture. A product that's designed to strip ads from content for re…

If you look at their finances you will realize that there is nothing left in that company.

You'd imagine they try to stretch it a bit rather than throwing it at the most ineffective charity projects they could come up with whilst firing staff.

Re: Mozilla to shut down Pocket and Fakespot

#589

I really enjoyed https://waldenpond.press/ when it was up and running. They selected articles from your pocket once a month and then printed, bound, and mailed them to you. When I discovered the service I had a 500 hour reading backlog, and for $14/mo I was getting 100+ page books of self-curated content. They were perfect for flights, trips, and lending out. I was able to force it to include recipes as well, and I s…

If I’d have known about them sooner, they’d have all my money.

I had the same thought! I've been attempted to cobble together a solution to do essentially this over the years!

Re: Mozilla to shut down Pocket and Fakespot

#590

Earlier quoted context omitted.

Yeah, bit weird - surely the population of HN is either going to be - people who _can_ code it themselves, or - people who believe they can get AI to code it for them

I'm in a third group: people who can decide if somebody else's code is "good enough" to host it themselves

For my definition of code in this context you're in the first group, as you're doubtless going to have to modify some Dockerfile/.env/config.yaml to point the flapdoodle_cache setting to /usr/local/.this/fnar
Post reply on HN