omnivore VS flyctl

Omnivore is a complete, open source read-it-later solution for people who like text.

If only they can add RSS support and newsletter subscriptions backed by Firefox Relay in Pocket, it can actually become a whole lot more useful.

If you need something like this today, try Omnivore[1]. Their RSS support is a bit wonky but very promising.

[1]: https://omnivore.app

Use https://omnivore.app/ it's free.

I'm quite happy with Omnivore: https://github.com/omnivore-app/omnivore

It's open source, I can host it myself it I want to but the reference hosted version on omnivore.app is free and quite reliable. Dark mode, progressive webapp, native apps, full text search, Obsidian integration, Pocket migration.

Compare that with instapaper: Terrible Android app that looks like Android apps from 2015, okayish iPad/iOS apps, quite expensive now, every interesting feature behind a paywall. I guess if you're into the minimalist aesthetic or if you've grown accustomed to it, sure, keep on using it. But it feels as if this product has been somewhat on extended life support and people would care a lot less if it wasn't run by Marco Arment.

I used to use Pocket extensively until I realized it wasn't going anywhere with features. I have since moved to Omnivore [1] and I couldn't be happier.

The devs are also ex-Pocket users and have worked hard to get feature parity and then some. There are mobile apps too for reading on the go (and work offline) which I use extensively when I am on flights. There is a graphql API and webhooks you can use for extending its functionality. Search could be a little better, but I use the labeling system which works well. I also use the logseq integration to keep a persistent log of articles I read on any given day.

[1] https://github.com/omnivore-app/omnivore

I briefly tried Omnivore and it seems to be have a good system for scraping web articles, especially for downloading them into Obsidian as markdown. I want to isolate that and have my script that that I can feed URLs into and get the contents as markdown files. I tried looking at the repo to see how it works and at this index.js file since the folder is called "puppeteer-parse". I tried reading it line by line multiple times it feels like too much to keep in my head at one, it makes me wonder how SWEs work with large codebases. I wonder if there are tools or ways to make reading large code files faster or easier.

This looks very nice, but self hosting requires reliance on google cloud.

https://github.com/omnivore-app/omnivore/issues/25

For frontend deployment, I used Netlify (for the generous free package) and the recommended fly.io for server + database (also cheap package).

Create an account on Fly.io.

You can learn more about fly.io and tigris, we will need to create an account on both platforms for this project regardless. Anyway with the theory out of the way let's get started in the next section as we create our accounts and start building the app.

Fly.io is a platform that helps you run your apps and databases closer to your users all around the world. It takes your app code, packages it up neatly, and puts it on virtual machines that can be quickly started or stopped. This makes your app faster for users and more reliable. Fly.io is easy to use, works well for small projects or personal apps. It's a great way to make sure your app runs smoothly for people no matter where they are.

In this post, we'll start from scratch, running FerretDB locally via Docker, trying out the connection with mongosh and the MongoDB Node.js client, and finally deploy FerretDB to Fly.io for a production ready set up.

2- fly.io

Fly is a cloud platform that focuses on global edge computing. Fly specializes in high-performance hosting and provides a global network of edge locations. Fly is known for its scalability and performance optimizations.

But videototextai.com is built using NextJS + Firebase auth + Firestore and a backend deployed at fly.io . Fly makes it really easy to deploy docker containers and that is IMO the fastest way to develop, you can setup a local setup

Alternatives explored: * northflank: While running the wrk test, requests were taking 3-7 seconds. Couldn't repeat Heroku's phenomenon of "400ms-800ms" during such a load test. * fly.io: Reliability: It’s Not Great * render.com: I remember the time when indiehackers.com was down because of an outage on Render, not sure if it's worth trusting.

For personal/portfolio projects fly.io and render.com both have free tiers that support the major backend frameworks and Postgres at the very least (although I think with Render at least the DB expires and has to be reloaded after a certain amount of time, have not personally tried it).