Omnivore is the free, open source, read-it-later app for serious readers. I’m looking into setting up this read-it-later service. I have a lot of URLs saved in my browser and need a place to bookmark them as well. Thinking this is a good place to start.
Anyone else using omnivore?
I haven’t used it (yet), but I came across it recently as what looks like the best alternative to Pocket. Pocket just changed their app for the worse (in my opinion).
Out of the loop. Mind telling me what changes have Pocket made to their app?
They generally seem to be shifting away from it being a basic “read it later” app primarily used to save articles that you come across and want to read later and are putting content discovery more front and center. When I opened the app recently a home page came up that had a few of my saved articles but it was mostly filled with suggested articles from the editors or recommended based on an algorithm. I then have to navigate to a different tab that has my “saves”. Looking at the list there is no longer an “archive” button, though I found out swiping will archive the article. Generally the UI has changed to be less intuitive and less focused on the articles that have already been saved.
I used the app to quickly save articles I want to read but don’t have time in the moment and then to go back and read later with a cleaner, more standard format.
I’m working through the selfhost install now! we’ll see how it goes and works. I asked them yesterday about their app support for mobile and custom domains. iOS is supported and they are working on adding that support for Android.
https://docs.omnivore.app/development/local.html
Interesting. So their docker-compose file can be used to start up a local server? This might be worth trying out sooner than I thought.
Looks that way! I am getting an error on the elastic search container though.
Starting omnivore-elastic …
omnivore-redis is up-to-date
Starting omnivore-elastic … done
ERROR: for migrate Container “cb29db590585” is unhealthy.
ERROR: Encountered errors while bringing up the project.
The way it’s set up it likes to error out because it takes a while to get the elasticsearch container up and running. If you do
docker-compose upagain 10-15 seconds later, it should spin up and run the migration script.I’ve tried that as well, but might have stopped the containers then started them. Might try having them run in and try the up again
I tried removing everything and stating over. Made sure NodeJS was also on v14 as well according to the website. Still no dice. Is there a way to exec the migration script otherwise?