←back to thread

1222 points phantomathkg | 1 comments | | HN request time: 0.001s | source
Show context
segphault ◴[] No.44064599[source]
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 readability doesn't align with their new direction.

I'd probably be applauding the decision to shut this down if I thought they were doing it to free up resources to increase their focus on the browser, but Mozilla seems to be institutionally committed to chasing its own demise, so I'm sure they will instead focus on AI integration and other stuff that nobody asked for.

Meanwhile, Firefox is still missing proper support for a bunch of modern web features like view transitions and CSS anchor points that are available in every other browser.

replies(20): >>44064677 #>>44065070 #>>44065265 #>>44065461 #>>44065781 #>>44065800 #>>44066084 #>>44066430 #>>44066456 #>>44066470 #>>44067023 #>>44067313 #>>44067943 #>>44067953 #>>44068655 #>>44069372 #>>44069898 #>>44070277 #>>44071607 #>>44074502 #
bayindirh ◴[] No.44066084[source]
I have another theory, actually.

I'm also a very old user, since the first days of the service, and I don't know how many saves I have it inside (will see when my export arrives).

The latest iteration's search was abysmal, and I normally refrain from using strong words. It failed to find exact matches from titles, the words or excerpts I know that exist in the article I'm searching for, and as a result, it became a FIFO basically. Unless you consume the list directly, hitting something you are looking for was nigh impossible.

After being berated by support to use the search "properly", I started to build my own app, a TUI tool to curate the list, but it was going slow. Honestly, I'm a bit relieved now since I'm free from developing that software, and I can dig the data in my own terms.

BTW, my export is just arrived, and it's a series of CSV files which has the usual suspects as columns. I can import this into a SQLite and dive the way I want.

One less thing to worry about, but this doesn't mean I'm not bitter about its demise, too.

Edit: It turns out I have ~37K saves. Whoa.

replies(6): >>44066706 #>>44066996 #>>44067237 #>>44069659 #>>44070926 #>>44072928 #
grvdrm ◴[] No.44072928[source]
I’m curious: with that many saves, what were you main reasons for using Pocket? Did you glean info at scale or is it just the case that you saved so much, read some subset, and it grew over time?
replies(1): >>44073414 #
bayindirh ◴[] No.44073414[source]
The initial idea was nice: do not lose what you want to read later (the list), keep a list of what you read (archive). Then it became better with “Permanent copies”: never lose content you want to read again later.

That number is a combination of all three, plus more than a decade of active use.

replies(1): >>44074635 #
andrepd ◴[] No.44074635{3}[source]
Damn, any alternatives in mind for that workflow?

My killer feature that led me to start using Pocket was Kobo integration: I could hit a button on my computer and continue reading an article on my ereader, duly cleaned up.

replies(2): >>44075916 #>>44095458 #
1. bayindirh ◴[] No.44095458{4}[source]
Since I'm slowly moving to self-hosting, I'll be installing Wallabag[0] most probably.

I also integrated my Kobo with Pocket with glee, but it turned into gloom when my saves ate all of the free memory of the reader :)

[0]: https://github.com/wallabag/wallabag