Mozilla to Shut Down Pocket on July 8th, 2025

[shuvashish76]

https://wallabag.org/news/20250524-pocket-shutdown/
"So Long, and Thanks for all the Fish" Pocket shuts down but open web remains

They're working on CSV import from Pocket: https://fosstodon.org/@wallabag/114562291073727070
Edit: https://www.wallabag.it/en/news/welcome-to-pocket-users

[gionebook]

Hello I'm very sad

Probably you know the information

I receive email down in Italian when is write Pocket will be no longer exist.

I use a lot and i found it excellent

Pocket

Grazie per la lettura di: Pocket saluta e se ne va.

Abbiamo alcune importanti novità da comunicare: in seguito a un'accurata riflessione, abbiamo a malincuore deciso di chiudere Pocket, la nostra app per salvare e consultare contenuti in un secondo momento.

Ecco cosa dovresti sapere al riguardo:

Pocket non sarà più disponibile dall'8 luglio 2025
Fino a quella data potrai continuare a usare l'app e le estensioni per browser. Tuttavia, a partire dal 22 maggio 2025 non potrai scaricare l'app o acquistare un nuovo abbonamento Pocket Premium.

Potrai esportare i tuoi articoli salvati
Riconosciamo il valore dei tuoi contenuti salvati. Per questo, potrai scaricare i tuoi articoli salvati (inclusi URL, titoli, note e riassunti) tramite la nostra Pagina Esporta fino all'8 ottobre 2025. Successivamente, tutti gli account e i dati di Pocket saranno eliminati in modo definitivo.


Best regards

[Frogm4n]

I did the Pocket API pull into my selfhosted Wallabag server and it went fine, if a tad slow.

[rcentros]

Originally Posted by compurandom

Have you seen https://github.com/Pocket

No, I hadn't. I relied on others (not on this forum) who said that Pocket was never open sourced. I guess they didn't know about it either.

Does this mean anyone can use the code to create a new Pocket?

EDIT: Is this the Github site for the actual Pocket "engine" or the clients using Pocket?

[Aleron Ives]

It looks like the repo has both the mobile clients and at least some of the backend code. It looks like they're using the Apache license, so I'm not sure what kinds of requirements that might impose. Thankfully it isn't GPL, or nobody would be able use it commercially.

[shuvashish76]

Originally Posted by Aleron Ives

Thankfully it isn't GPL, or nobody would be able use it commercially.

GPL has no such restriction on commercialization.
See: High or low fees, and the GNU GPL section of https://www.gnu.org/philosophy/selling.html

Free software is about freedom, and enforcing the GPL is defending freedom. When we defend users' freedom, we are not distracted by side issues such as how much of a distribution fee is charged. Freedom is the issue, the whole issue, and the only issue.

[Aleron Ives]

Originally Posted by shuvashish76

GPL has no such restriction on commercialization.

The GPL's requirement to release source code impacts any product you integrate GPL code with, which then forces you to release the source code for the rest of your product. As a result, you can't use any GPL code in a commercial product that you want to keep closed source, which tends to mean that GPL code is not used in commercial products. You need to use LGPL instead to avoid that problem, assuming the LGPL code can be contained within a separate library.

[Quoth]

Originally Posted by Aleron Ives

The GPL's requirement to release source code impacts any product you integrate GPL code with, which then forces you to release the source code for the rest of your product. As a result, you can't use any GPL code in a commercial product that you want to keep closed source, which tends to mean that GPL code is not used in commercial products. You need to use LGPL instead to avoid that problem, assuming the LGPL code can be contained within a separate library.

I'm not sure that's quite true either. Or else it's ignored.

[shuvashish76]

https://gitlab.com/anarcat/wallabako
Wallabag client for Kobo readers. Downloads unread articles as individual EPUB files.

[jgneff]

Originally Posted by Quoth

I'm not sure that's quite true either. Or else it's ignored.

It's not quite right. Otherwise, Kobo would be unable to distribute its proprietary user interface with the GPL version 2 Linux kernel on all its Kobo e-readers.

The GPL license requires that any code linking to a GPL library be released under a GPL-compatible license, where linking is a technical software term. Yet many GPL software projects, such as the Linux kernel and the Java virtual machine, remove even that requirement through the GPL linking exception.

In any case, all the Pocket code is released under either the Apache License Version 2.0 or the Mozilla Public License Version 2.0, which are very permissive licenses.

[shuvashish76]

Originally Posted by Aleron Ives

The GPL's requirement to release source code impacts any product you integrate GPL code with, which then forces you to release the source code for the rest of your product.

Would have been better to quote with legitimate source reference. But well it's not the thread to discuss licenses, sorry for dragging license topic.

[PeterT]

Originally Posted by shuvashish76

https://gitlab.com/anarcat/wallabako
Wallabag client for Kobo readers. Downloads unread articles as individual EPUB files.

I tried it and wallabag. One major complaint is that the epubs created by Wallabag and loaded by Wallabako do not contain an indicator that they are from Wallabag (ie either say the author beibg set by Wallabag to inbclude a prefix, or a collection being set by Wallabako).

While the basic functionality is there, it looses a lot in the integration into Kobo.

[shuvashish76]

Originally Posted by shuvashish76

For KOReader users there is https://github.com/koreader/koreader/wiki/Wallabag plugin.

https://matija.suklje.name/trying-ou...ays-and-months
Trying out KOReader and Wallabag (the first few days and months) Getting excited about reading again

Somebody wrote a blog with their experience/review with Wallabag+KOReader on kobo...
For some people this might be interesting to read before trying it.

[ChrisHistorian76]

I just logged in for the first time in a while, and I'm stunned by this news. I'd gotten away from using the app, probably to my own detriment by keeping tabs open, assuming (incorrsctly) that I'd just read the article later, but it's really surprising they're killing it, and Fakespot, entirely.

I'm not sure if these work with Kobo, but Techradar's article on the Pocket shutdown recommends Instapaper, Readwise Reader and Raindrop. I've had experience with Instapaper, although it was years ago. For some reason, I thought it had stopped working quite a while ago, I guess not!

https://www.techradar.com/computing/...g-alternatives

[DNSB]

I'll miss FakeSpot more than Pocket.