readeef VS rss2email

I self host https://github.com/urandom/readeef which I wrote some time after the demise of google reader

I've been using my aggregator since google reader died: https://github.com/urandom/readeef

I personally prefer to read my feeds via my email client, and hacked up an RSS to email script:

https://github.com/skx/rss2email/

Having the feeds in your mail client makes sorting, and searching trivial. Plus you get the content archived for future reference.

I use rss2email to send feed contents to my inbox, from there I have a good searchable archive wherever I am - be it desktop or mobile.

https://github.com/skx/rss2email/

I never got the hang of using a browser to read feeds, email suits me much more naturally.

I wrote yet another "rss to email" tools, which is what I use for consuming feeds:

https://github.com/skx/rss2email/

(Rewritten in go, primarily because the standard r2e was the last daemon/program on my host that required python. So switching let me drop a whole bunch of dependencies.)

I currently use a go based version of rss2email from https://github.com/skx/rss2email . Works great, and the dev is very responsive to bugs or feature requests.

RSS is awesome! I never got the hang of using a read-application, instead I use rss2email to get copies of posts delivered to my inbox.

There are a few different tools for getting the feeds to email, my own is a pretty simple golang application I run in a docker-container:

https://github.com/skx/rss2email/

You can build from tip, or install the 1.16beta1 release, if you want to experiment. (Something I did for a couple of my projects, for example.)