home.social

#getpocket — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #getpocket, aggregated by home.social.

fetched live
  1. Can someone recommend me an alternative to murdered #getpocket or #omnivore that has offline storage capabilities for #ios ?

  2. While I was not looking Mozilla has killed Pocket (aka. "read later") without having sent me a notice and now my data is gone (not that I had a lot).

    Since Pocket was one of the main reasons I bought a Kobo ebook reader this spring, I'm somewhat annoyed.

    But Kobo replaced Pocket with Instapaper, where I apparently even have an account I have not used since 2012 :D

    support.mozilla.org/en-US/kb/f

    kobo.com/blog/kobos-summer-202

    #Mozilla #Kobo #Pocket #GetPocket #Instapaper #ebooks #OurIncredibleJourney

  3. With Mozilla's #Pocket shutting down (articles are already unavailable, exports can be retrieved through 8 October 2025, see: web.archive.org/web/2025092720), I've exported the list of URLs I'd logged with the service.

    One of my longstanding gripes was that there was no way for me to get a total of the articles I'd saved.

    (There ... were other gripes.)

    I now know: 30,735.

    In an ideal world, this would have been a useful library of references. I'd tagged many of these (including, eventually, adopting a convention of tagging by archive date which Pocket surely must've known somewhere in its data schema, but petulantly hid from its users), through a loose but somewhat controlled vocabulary influenced in part by both my general interests and some familiarity with existing library ontologies, classifications, and subject headings.

    I'm kicking around what to do with this archive. One question of course is how many of the links have since rotted (I suspect a high percentage). I've got a few leads on readability-rendering (including a bash script invoking JS ... somehow ... I've got to look at). Tracking down archived copies, and spinning up a media server, would also be handy.

    #Mozilla #GetPocket #Shutdown #Libraries #KFC #KnowledgeManagement #WhyIsContentManagementSoShiteStill

  4. Absolut schade, dass #Mozilla #pocket (#getpocket) einstellt. Seit gefühlt 10 Jahren eine meiner Lieblings-Apps. Vor allem die Offline-Nutzung war als Zug-Pendler immer ein großer Vorteil.
    Jetzt teste ich mal #Raindrop. Auch um meine Apps etwas zu verringern bzw. zu konzentrieren.

    Eure Tipps?

  5. Even after the Pocket's web app shutdown the GraphQL API and auth flow are still alive, so export your articles while you can! github.com/jnv/pocket-archive
    The last date to export saves is October 8, I hope the API remains functional until then.

    #GetPocket #pocket

  6. I made a bun app to grab all data from Pocket, including full-text of articles, using Pocket's private GraphQL API: github.com/jnv/pocket-archive

    There's still a week to go, so perhaps it'll help someone.

    #GetPocket #Pocket

  7. I hadn't logged into Pocket in a while, but discovered yesterday that they are shutting down. :( So today I set up a self-hosted instance of @linkwarden and migrated all of my links from Pocket. It all took less than an hour.
    #linkwarden #readitlater #getpocket #selfhosting

  8. With Mozilla shutting down Pocket, folks are calling for open-sourcing it. There's this “pocket-monorepo” project which seems to contain the majority of server code? github.com/Pocket/pocket-monor

    Some parts are missing, notably the parser, but I've found it useful for reverse engineering their GraphQL API, particularly the public API proxy.
    Anyone can confirm what else is missing?

    #GetPocket #Pocket #GetPocketGoingAway

  9. @nikolasdi Thanks for the hint. I tried @readeck now as well and it is great. But I'm still missing the #singlefile integration or at least need to understand how to add it. For my common tasks I may stay with #linkding for now. I also use @obsidian clipper to store really important stuff I need for my active knowledge base and mark and modify the content as needed. #obsidian #pocket #getpocket #bookmark

  10. On my search for a #getPocket replacement I found nocoDB. That's not a bookmarking service. But its a selfhosted AirTables clone. And it has a swagger API thingy build in. That could be handy to build all sorts of PWAs to push to my own data pool...

  11. Wie das im Netzleben so ist, der nächste Dienst des eigenen Workflows wird abgewickelt. Nun ist es Pocket. Ab 08. Juli 2025 ist der Service inaktiv (Zeit für den Export), Anfang Oktober sind dann die Inhalte weg!

    Für mich war #Pocket nicht essentiell aber praktisch, hat viele Jahre zuverlässig gearbeitet und vor allem nicht genervt – schade darum.
    Im Sinne von #unplugTrump werde ich auf eine selbstgehostete Lösung umsteigen.

    #ReadItLater #GetPocket

    support.mozilla.org/en-US/kb/f

  12. Goddammit !

    Pocket the browser bookmarking service -that just happens to synch seamlessly with with Kobo devices - is being Discontinued by Mozilla.

    The service will stop working in July of this year (2025) and users have until October to export any bookmarks before everything gets deleted.

    Full details at this link.

    This SUCKS.

    #Pocket #GetPocket #Mozilla
    support.mozilla.org/en-US/kb/f

  13. Dang.

    #Pocket is getting killed off.

    I’ll need to figure out a new read-later situation.

    I typically add stuff to Pocket throughout the day via whatever platform I’m on at the time (usually via the Pocket Firefox extension) and read it later via the Pocket app on my Android e-ink device.

    #GetPocket #ripPocket

  14. Me: Pocket should up their game, the parser is very unreliable, search is borderline useless, I still can't add notes to highlights nor articles, text-to-speech often refuses to load. I guess I'm gonna switch to Readwise Read—
    Pocket: YOU CAN NOW SELECT CUSTOM APP ICON. CHECK OUT THIS AMAZING PRIDE ICON!

    Pocket really is a lost cause, isn't it?

    #GetPocket #ReadwiseReader

  15. update: using Omnivore on their hosting. pretty good UX-wise.

    Omnivore's only major weakness so far is that it doesn't understand Fedi: for a Mastodon post, it'll capture the Mastodon UI, not the post. (Open Graph tags do get saved as metadata and normally contain the entire text of the post, but you gotta go look for them, so it's only useful for search.)

    haven't gotten around to importing my Pocket bookmarks yet.

    #Mozilla #Pocket #GetPocket #Omnivore #OmnivoreApp

  16. I am currently building my own WIKI with #Notion
    It will be the single source of truth for all links, pics, workshops, templates etc. for my beloved role as an #agile team coach aka #scrummaster

    For this, I have to find all my bookmarks on #getpocket , LinkedIn - Mastodon - Twitter

    Tips welcome!

  17. Why on earth does #GetPocket now NOT render a reader view of some articles, with no override possible?
    YOU HAD *ONE* JOB TO DO, POCKET!

  18. @valvin Yes, daily! I follow blogs, news, podcasts, and even YouTube channels via RSS. I'm mostly using #feedly , together with #getpocket, for reading later.

  19. @mutkitta Thanks, I'm aware of Wallabag but after several earlier transitions (still not fully recovered-from) I'm leery of anything I don't fully control.

    I'll also note that Pocket still haven't replied to my email sent over two months ago.

    (I'm not sure if that's because their spam system is still refusing Protonmail, but that would be yet another strike against Pocket.)

    #Pocket #GetPocket #MozillaPocket #Mozilla

  20. I've considered migrating my personal home page for quite a while. I've wanted to build everything in #infraascode as a #portfolio too, and a fun exercise, but what implications could be from having that as #oss? (i.e #pulumi state etc)

    The idea is I can then easily spin up #microservices (i.e. I'd like to visualize a list of the articles I've been reading on #getpocket or the books I am currently reading via either #goodreads or #Bookwrym). Having it in #iac would make it somewhat trivial.

  21. Are there any #opensource #getpocket alternatives that I should try?

    If you don't know any, please boost! :boost_requested:​

  22. I'll also note that on APK Mirror, v. 8.1.1.0 has more downloads than any release of Pocket dating back to 7.64.1.0, in September of 2022.

    Which would suggest some possible level of agreement that it is in fact preferable to other releases.

    #Pocket #GetPocket #MozillaPocket #ApkMirror

  23. OK, this is getting fucking ridiculous.

    I've installed and reverted three versions of Pocket so far trying to find one that performs with a tolerable level of annoyance. This is hours spent managing a fucking application's brokenness instead of being able to read and research.

    Hint: It's not 8.5, 8.3, or 8.2. Currently trying 8.1, from February, though I swear I'd updated since then (I usually check for updates on apps weekly). I'll update parent when I find it.

    OK: 8.1.1.0 seems to revert both behaviours. That's the 17 February 2023 release here: apkmirror.com/apk/mozilla-corp

    Meanwhile ... the Google Play reviews discussion is illuminating, and the natives are not happy as of April, 2023:

    play.google.com/store/apps/det (Archived as that's a dynamic page: web.archive.org/web/2023070822)

    Also #ApkMirror is a motherfucking godsend for situations such as this: apkmirror.com/

    #Pocket #GetPocket #MozillaPocket #ApkMirror #FuckingFuckAlreadyMozilla

  24. Copy of my support email sent to Pocket.[1]

    Further Pocket 8.6 issue: "Full article view" is no longer supported in the Pocket app itself.

    This is a dealbreaker full stop. I've reverted to an earlier version of the app which doesn't include this functionality (currently trying 8.5.0.1) and will not upgrade the application further.

    There are numerous reasons why having a flawed or even Web view in-app version of the article is useful:

    I use Pocket to annotate articles, mostly by adding tags to them. Often the tags are copied directly from the text itself (personal names, institutional or organisational names, place names, specific concepts, etc.), and having to navigate back and forth between a browser and Pocket's own tag-editing / entry interface(s) is utterly disruptive and destructive to workflow. If your goal is to keep people from tagging articles, well, congratufuckinglations, but as a desired and useful feature, seriously, fuck this shit.
    (Being able to add tags directly based on selected text, or to have that text copied to the tags editor for further refinement, e.g., removing stop characters (commas), and editing down to tag max lengths (25 chars) would also be useful. But well over five years into dealing with Pocket's bullshit, who the fuck am I kidding?)
    Readability.js It's really a killer fucking feature. "Web design isn't the solution, Web design is the problem." The reader-mode view for articles is vastly and indescribably better than the default for 99.999999999999999999% of all online content. Sure, it sucks when the origin item is so utterly fucked up that Readability can't make heads or tails of it, but that's really not your fault, and I've appreciated that bad parsing can be reported and does seem to eventually get fixed.
    Paginated navigation. Yes, as I've said, Pocket's swip-based gesture UI/UX is horrible, but pagination, especially on e-ink devices, is hugely preferable to scrolling. I wish you'd fix this as I've long suggested: a fixed rather than fluid layout, Pocket article tools (select, copy, highlight, etc.) directly accessible from page-flip mode, a region-based navigation as with e-book reader software rather than gestures. But even the shitty previously-existing version is better than nothing at all. Low bars and all.

    I'll further note that the behaviour of the Web-based Pocket client dumping me to the original document rather than Pocket's render of it is similarly absolutely maddening.

    Please, for the sake of all of us, pull your goddamned heads out of your collective asses.

    Notes:

    1. For well over a year now, Pocket seem to be unable to receive (or acknowledge) email from Protonmail accounts. So this is both record and alternative delivery.

    #Pocket #GetPocket #MozillaPocket #Mozilla #PleaseForTheSakeOfAllOfUsPullYourGoddamnedHeadsOutOfYourCollectiveAsses

  25. So, Pocket, the article-archival tool that keeps getting worse the more you use it, has just become immeasurably worse.

    I've reverted from version 8.6.x to no, not 8.5, not 8.4, not 8.2, but 8.1.1.0 from freaking February of this year to revert these completely fucking brain-dead changes.

    The TL;DR: link is apkmirror.com/apk/mozilla-corp

    That's what you want to install and freeze on until Pocket catches a motherfucking clue.

    I've had a long an unhappy relationship with this feature and app. Its sole claims to my continued use are that it holds nearly 5 GB of content hostage, and that it, unbelievably, seems to be the best of what is an immensely shitty application space. See my now-six-year-old rant virtually all of which remains valid: web.archive.org/web/2019051209

    Most recently, Pocket has lost two features:

    • A "page flip" mode, which though itself hugely flawed, is better than scrolling through articles, especially on e-ink devices.

    • The ability to view all articles either in the (hugely preferable, very useful) #ReadabilityJS view, or in-app in a "web view". The latter now revert to your device's default Web Browser app on mobile devices.

    The problem with that latter is that the task of annotating and tagging articles (my principle remaining justification for Pocket) is made vastly more tedious --- and it's already more than adequately tedious in previous Pocket versions. To the point it's not even worthwhile.

    Fortunately, I was able to hunt down a prior version of the app (using the APKMirror app), and I will not be upgrading Pocket beyond the most recent version I can find which still supports both Page Flip and Web View modes, as noted above 8.1.1. from 17 February 2023. (Few if any of Pocket's "improvements" over the past five years have had any value to me whatsoever, so this is little loss.)

    There is of course a Relevant xkcd: "Software Updates":

    xkcd.com/2224/

    I would so like to see a useful document-management solution for tablets and e-ink devices with the ability to managed both offline and online (Web-based) content.

    Boosts and re-sharing this on other platforms is strongly encouraged.

    Edits: I'm updating this toot as I'm finding out more. In particular, what version(s) of Pocket are NOT affected by these changes is not yet clear.

    #Pocket #GetPocket #MozillaPocket #Mozilla #ApkMirror #EInk #DocumentManagement #xkcd #xkcd2224 #kfc #webfs #docfs

  26. Sometimes I take notes when I work with an API. Maybe it could be helpful to someone.
    So here's my write up about authorization flow in #Pocket (#GetPocket) API bitoff.org/pocket-api-auth/