omnivore VS obsidian-releases

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

The solution was already installed on both my computer and my phone: Obsidian.

> why does open source need to "win"

Open source does not need to win.

But your ability to be in control of your computer needs to be preserved. A proprietary fridge cannot control your diet, while a proprietary App Store can control what software you install on YOUR phone (unless you live in EU, hello DMA!). The tail wags the dog, so to speak. Proprietary software has also been shown to break user workflows or remove functions in an update while leaving users with no choice whatsoever.

One alternative to having open source win is to ensure software must come with a robust warranty and other assurances you expect from the things you buy. EU's CRA will make software vulnerabilities in WiFi routers covered by warranty, for example.

You can also ensure robust and interoperable data storage options. For example, https://obsidian.md/ stores all notes in Markdown, not holding the data hostage in case users will not like how future versions will work. GDPR actually has a provision for data portability (Art. 20), but it does not seem to have a requisite effect on the industry yet.

And until the above issues are solved, open source remains the best way to ensure that a software tail cannot wag your computer dog.

[2] https://obsidian.md/

So I've had my fair share of personal websites and blogs. I have built them on stacks ranging from the most basic HTML and CSS, to hosted frameworks like Wordpress and Laravel, to the more modern single page applications built in Vue and React. For a simple content blog I think you can't go wrong with a Static Site Generator though. These days I am almost exclusively writing everything in Obsidian. Which is great because its all in standard markdown format. This allows for a really neat and easy content publishing workflow.

Consider making an Obsidian[^1] plugin, or writing to Obsidian-compatible Markdown files :)

[^1]: https://obsidian.md/

Obsidian is a writing application created to allow for offline / private note taking in markdown format, in an interface that looks a lot like our regular programming IDE. It is very flexible, with a good collection of community plugins that you can use to customize Obsidian to your heart contents.

Obsidian support via our Obsidian Plugin

Thank you!

In the beginning, I used kognise'z water.css [1], so most of the smart decisions (background/text color, margins, line spacing I think) probably come from there. Since then it's been some amount of little adjustments. The font is by Jean François Porchez, called Le Monde Livre Classic [2].

I draft in Obsidian [3] and build the site with a couple python scripts and KaTeX.

[1] https://watercss.kognise.dev/

[2] https://typofonderie.com/fr/fonts/le-monde-livre-classic

[3] https://obsidian.md/

Great job!

I played around with this on a couple of small knowledge bases using an open Hermes model I had downloaded. The “related notes” feature didn't provide much value in my experience, often the link was so weak it was nonsensical. The Q&A mode was surprisingly helpful for querying notes and providing overviews, but asking anything specific typically just resulted in less than helpful or false answers. I'm sure this could be improved with a better model etc.

As a concept, I strongly support the development of private, locally-run knowledge management tools. Ideally, these solutions should prioritise user data privacy and interoperability, allowing users to easily export and migrate their notes if a new service better fits their needs. Or better yet, be completely local, but have functionality for 'plugins' so a user can import their own models or combine plugins. A bit like how Obsidian[1] allows for user created plugins to enable similar functionality to Reor, such as the Obsidan-LLM[2] plugin.

[1] https://obsidian.md/