Developer here. I super appreciate the support. Some context: - I'm a big fan of RSS and there is a thriving community behind. Just check out this list: https:

Developer here. I super appreciate the support. Some context: - I'm a big fan of RSS and there is a thriving community behind. Just check out this list: https://github.com/AboutRSS/ALL-about-RSS https://github.com/AboutRSS/ALL-about-RSS - I'm also a firm believer of web as a platform, a distributed document database, and an open library of knowledge, as opposed to a "compile target" for cryptic JavaScript apps that take control and freedom away from users. Jim Nielsen has a timely critique: https://blog.jim-nielsen.com/2021/web-languages-as-compile-targets/ https://blog.jim-nielsen.com/2021/web-languages-as-compile-t... - The bigger picture behind the osmos project is to create an IDE for personal knowledge management. On the surface: 1. I read my rss with osmos::feed. 2. I capture reference links from the feed with osmos::memo. 3. I digest the knowledge and connect them into notes with osmos::note. - All of them are done with plaintext (some sprinkle of markdown), remote hosted on GitHub, so they are easy to run NLP and ML against. Potentially with GitHub actions, or locally with some bot, with a cloned repo. - In the long term, I was hoping to create a "positive feedback loop". Use ML to extract patterns from my notes, make connections for me, and recommend interesting reading in the osmos::feed. On the other end, osmos::feed can use NLP to detect how each article in the feed might connect to ideas from osmos::note and make note-taking even easier. - The parent project (https://osmoscraft.org https://osmoscraft.org) is still in super early stage. Would love to let the community give it a spin while I keep iterating. - Thanks again for the ♥