I've been using FF since it was Mozilla Phoenix and I never once tried Pocket.
Mozilla to shut down Pocket and Fakespot
291–300 of 782 posts
Re: Mozilla to shut down Pocket and Fakespot
#292Huh, that’s annoying. Been using pocket since around 2008, mainly for when I was abroad and roaming was costly. Looks like I’ll need to export my library of stuff.
Do I have any other similar options?
Re: Mozilla to shut down Pocket and Fakespot
#293I loved Pocket. I used it nearly daily. I was often in their top n% of users. I paid for it. Then one day they changed the way their rendering worked on iOS. And it destroyed my workflow. I also bought a Kobo E-Reader specifically to use Pocket with it. In short order I found an open-source alternative - Omnivore - and spent my time hacking away at my Kobo to get it to pull from there instead. https://github.com/Podg…
Check the barebones but functional Wallabag. Hosted version available for a fee.
Just to add that you can also self-host it, and it supports Kobo as well. I once stumbled upon but didn't investigate further since Pocket just worked so well. I guess now I will have to.
Re: Mozilla to shut down Pocket and Fakespot
#294I loved Pocket. I used it nearly daily. I was often in their top n% of users. I paid for it. Then one day they changed the way their rendering worked on iOS. And it destroyed my workflow. I also bought a Kobo E-Reader specifically to use Pocket with it. In short order I found an open-source alternative - Omnivore - and spent my time hacking away at my Kobo to get it to pull from there instead. https://github.com/Podg…
Check the barebones but functional Wallabag. Hosted version available for a fee.
It’s the lack of nice sync to an articles directory that’ll be missed. I’m also bitten by this shutdown.
Re: Mozilla to shut down Pocket and Fakespot
#295Earlier quoted context omitted.
Safari exists, and is quite popular.
Safari is the only reason we don't rename (yet) Web as ChromeOS development platform. Thanks everyone, especially all those Electron crap apps.
The real death knell is that Microsoft decided not to go with Mozilla in building the relaunched version of Edge.
That would have been a very fruitful relationship, but they couldn't make it work. My understanding is - albeit its second hand - that they really didn't want to simply jump to Chromium, but Firefox proved far more complicated to do what they wanted to do.
Ultimately, Microsoft Edge went from a pretty good browser to loaded with of things I dislike, which is a real shame, but I know it would have significantly boosted usage numbers of Firefox and its engine, which in turn would drive more investment into Firefox itself.
Re: Mozilla to shut down Pocket and Fakespot
#296I've never used Pocket, so I can't comment on feature parity, but for people looking for an alternative I've been using Instapaper for years and have been very happy with it. The founders recently bought it back from Pinterest and have been making steady improvements.
Pinterest sold it in 2018. The founder is Marco Arment, he's not the one who bought it back. But yes, instapaper is still alive. https://techcrunch.com/2018/07/16/instapaper-is-leaving-pint...
Ah, OK - I must have misread the bit about who bought it from Pinterest.
Re: Mozilla to shut down Pocket and Fakespot
#297Earlier quoted context omitted.
anyone have any good suggestions for a self-hosted option?
I've tried all of the options: Linkwarden, Linkding, Karakeep, Shiori, Wallabag, Grimoire—you name it, I've tried it. These are all great tools, and I use Karakeep myself, but I use it to bookmark and archive links, not as a "read it later" tool. In my opinion, no self-hosted read-it-later tool can replace Instapaper or Pocket, as they focus on providing an exceptional reading experience in a native app that works of…
They open sourced some stuff already https://github.com/Pocket
Re: Mozilla to shut down Pocket and Fakespot
#298Earlier quoted context omitted.
Are we on Hacker News?
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
Re: Mozilla to shut down Pocket and Fakespot
#299I've got years of saved articles in there and the export situation is pretty bad. It only gives you the URLs, not the actual content. So if a site goes down (which happens all the time), you're basically screwed.
I'm thinking about throwing Claude Code at this problem and building a proper exporter that actually saves the content.
Re: Mozilla to shut down Pocket and Fakespot
#300Earlier quoted context omitted.
You can connect Pocket to Readwise Reader ( readwise.io/reader ), via Pocket's API, which will let Reader view all the tags, metadata, highlights, etc. Even if you didn't want to use Reader, you could then export from inside Reader and Readwise to pull out CSVs of all of your articles+highlights -- no subscription required. (full disclosure: founder of Readwise here, obviously if you want to try our Reader app that w…
seems to work better with https://fabiensanglard.net/rss.xml than most readers although it still gets 403s fetching images but I'll still give it a run to see how it works for me.
I think the image urls provided in the RSS feed are just broken, eg this one is linked in the latest article:
