rssify VS subscriptions-digest

Since everyone is pitching their own, I built https://github.com/fran-penedo/rssify, which started as a fork of https://github.com/h43z/rssify. The basic functionality is similar to Vinnl's: give it a URL and some selectors and it builds the RSS feed. From this, I added a few things: templates (if you want to subscribe to individual projects within a webpage, like fanfics in ao3), transforms (when the data is not quite the text of the DOM element), a flask server you can use to add new URLs you have a template for and update the feeds, and a userscript to add the current URL using the server.

This could nicely supplement my GitHub automation that emails feed digests https://github.com/mhitza/subscriptions-digest

Similarly to my repository, I think I would suggest the option to fetch the configuration file from an external resource defined via an action secret. For my automation I'm using a Gist (not sure if Gitlab has same thing; also private but publicly accessible snippets).

At least that way you can keep your own feed configuration while allowing those that fork the repository to not have to manually fix conflicts within the feeds.toml config.

Being displeased with feed reader experience I wrote up a quick script and GitHub automation that generates a daily digest email for my subscriptions.

I have been using this setup for a week at this point, and I found it pleasant enough that I thought others might find a use for it as well.

https://github.com/mhitza/subscriptions-digest