nntpit VS RSS2EMail

For myself I use https://github.com/taviso/nntpit which uses the subreddit's .json endpoint and is done by an indy developer not a business. So changes to Reddit's API negatively impact FOSS tools like this.

It looks like this: https://github.com/taviso/nntpit/blob/main/doc/screenshot.png

Do you see any future in bridges like nntpit?

well

I don't know the answer to your question, but I see no reason I couldn't add hn support to nntpit, if there was interest.

https://github.com/taviso/nntpit

hrm, not sure I've tried to go the other way. I use rss2email to bring most of my RSS feeds into my inbox where I have all the power of mutt or mail(1) to mow through my feeds. I've never wanted to go the other direction.

as a twist on this, I like rss2email which drops my RSS feeds in my inbox, letting me use my existing MUA (no new keyboard commands to learn, syncs read-/deleted-state across machine via IMAP, works with multiple clients, etc).

However, I found it wanting, so I returned back to my previous habits of using old-Reddit for a few sub-reddits with which I regularly interact, and use my RSS reader, (rss2email ) for the sub-reddits that I read without interacting much. You can tack .rss at the end of any subreddit URL to obtain the RSS feed for it. And I find that much more pleasant (having all the power of mutt for mowing through posts of mild interest)

Alternatively, for myself, I use rss2email to pull my RSS feeds into my inbox, reducing the syncing problem to one that IMAP has already solved for me (and no new UI to learn, just the same mutt/claws interface I use for my email).