←back to thread

1222 points phantomathkg | 1 comments | | HN request time: 0s | 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 #
gxqoz ◴[] No.44067237[source]
Yeah I have 32k saves and hit the same problems with search being extremely unreliable. About 5 years ago quotes stopped working in search. Trying to find "The Grapes of Wrath" would return all instances of "of" and "the." You could sort of hack it by searching for the most distinct word (maybe "Grapes") if you already knew exactly what you were searching for. I long suspected there was some architectural change they made on the backend that broke this and they didn't want to admit in support articles. Perhaps the Mozilla legal department determined that having a text copy of all articles in their database was some legal risk and they moved to just having the URL and maybe the title (this would also explain why "permanent copies" disappeared).

Anyway, as the 32k articles indicate, I was a power user of Pocket so part of me is sad it's going away. But they've really been checked out since maybe 2019 with regards to any real support for this product.

replies(4): >>44070561 #>>44070958 #>>44073853 #>>44188229 #
alias_neo ◴[] No.44070958[source]
Is something like Apache Solr (a search index) well suited for something like this?

I've deployed and used it at work for searching specific, well-specified bits of information, but I don't know how well it would work on large chunks of text like articles etc; I assume this is its real purpose and it should fit, but I'm guessing.

replies(1): >>44071444 #
retinaros ◴[] No.44071444[source]
Just pgsql is enough. Even a chache db or sqlite do full text search
replies(1): >>44074827 #
1. alias_neo ◴[] No.44074827[source]
I'm not familiar with the various search features of different databases.

Do they offer things like the phonetic search that Solr does?

With Solr you can search a noun for example even if you only know how to say it and not how to spell it.