j12y VS osmosfeed

The configuration file for my project is .github/workflows/build-readme.yml. The folder naming convention is critical, but the YAML file can be named to suit the purpose and there may be multiple workflows kept in separate configuration files.

and configured tsconfig.json and package.json to run my build with npm start by executing:

You may be interested in Osmosfeed: https://github.com/osmoscraft/osmosfeed

It is a static site feed aggregator primarily designed to go with GitHub Pages. I host one to aggregate my own writing on different sites. I think it may fit your use case because your Osmosfeed site itself outputs a single Atom feed. So, for example, if I have an Osmosfeed site that aggregates feeds 1, 2, and 3, the Osmosfeed site has a single feed which will include the three individual feeds. Mine has about 10-12 feeds and it has worked perfectly thus far with no issues. Not sure if it would have problems at higher numbers.

I have been using osmo feed [0]. Rather than self hosting, it uses GitHub actions. I have my own usename.github.io/to-read linked to it, to access it from anywhere. So far I have liked this approach.

[0] https://github.com/osmoscraft/osmosfeed

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.

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) is still in super early stage. Would love to let the community give it a spin while I keep iterating.

Thanks again for the ♥

GitHub