rss2email VS ttrss_plugin-feediron

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.)

It Technically could but as far as I am aware it doesn't.

Some alternatives

TT-RSS has multiple plugins, including the one I currently support https://github.com/feediron/ttrss_plugin-feediron

FressRSS has CSS selector support out of the box and has a readability extension that supports Readability or Mercury

I've been dreaming of porting Feediron to both FreshRSS and Nextcloud news. But I barely have any free time as is... one day

Back when I was using Tiny Tiny RSS I've developed af_feedmod to download the article from the linked webpage so you'd end up with a full feed. This was later forked into FeedIron and seems to be somewhat popular by now.

I'm a die hard TT-RSS user, mainly because of the Feediron plugin (A full text page parser) that I now maintain.

The official plugin uses a php port of Mozilla's Readability, which is used for Firefox Reader Mode. There is also the 3rd party FeedIron that is more configurable.

https://github.com/feediron/ttrss_plugin-feediron

Always good to see RSS projects pop up on hackernews. I'm still maintaining the Feediron plugin for TT-RSS - https://github.com/feediron/ttrss_plugin-feediron

Unlike this project Feediron is only for modifying existing RSS feeds to extract the desired information. Typically uses xpaths to select content

> I've never open sourced it though because I guess it's a bit of a grey area

I'm maintaining the TT-RSS plugin feediron https://github.com/feediron/ttrss_plugin-feediron that fetches full-text data, so my thinking is this:

At the end of the day if it's a openly available website and you are personally (through your own server) fetching the resources I don't think anyone has a right to complain.

Now if you were offering it as a service it might arguably be a bit more grey, but only if you're ignoring the robots.txt file

So you plan something like the FeedIron TT-RSS Plugin (https://github.com/feediron/ttrss_plugin-feediron) to allow customization of a feed to get relevant content?