tinyfeed is a CLI tool that generates a webpage from a collection of feeds. It's dead simple: no database, no config file, just a CLI and some HTML.
This release focuses on making tinyfeed a more stable and deterministic program. A stable experience is always better for users, and it also allowed us to design a new snapshot-based test suite, so regressions are much less likely to slip through.
It also included a bunch of fixes related to the --order-by option that was added in the previous release and was, sadly, quite full of bugs ๐ฌ.
Main items on the menu today:
- Stable ordering: Feeds and items now come out in the same order on every run.
- Discoverable sorting: --help now lists the values
--order-byaccepts: publication-date, update-date, feed-name and author. - Lighter dependencies footprint: upgrad to gofeed v1.5, which removes 6 indirect dependencies.
- Lots of refactoring and a brand new test suite.
And the cherry on top: tinyfeed now publishes an Atom feed, so you can follow its releases! WHY DIDN'T I THINK OF THIS EARLIER? A FEED FOR TINYFEED!
AI Disclosure:
- Implementation - Pair: I like directing IA when I have a refectoring in mind. On new feature I prefere avoiding it. I find that using IA for feature mean I spends less time time using the software myself during dev and then I miss the bugs.
- Testing - Hint: the new integration tests suit is 100% me, but the new unit tests are often generated by IA then reviewed / refactor by me.
- Review - Pair: for contributions it's 100% myself, I don't have much MR but I take a lot of time to review them. For my own code, as im a solo maintenr, the IA is the only one giving me reivew.
Lots of options to handle your feeds on a self hosted setup. What are your criteria? What are you trying to achieve? We need something specific to make recommendations.
I would argue that where tinyfeed shines is that it does not require any dependency of any kind: not database to setup, not configuration, no nothing. You just give it a list of feeds and it generates a page for you. What you do with that page is up to, so it adapts well to lots of workflow. The trade off with that approach is that it is stateless so if you like to do bookkeeping (like read later / favorites features) then it's not for you.