I've been using RSS-to-email since forever. I now run my own RSS-to-email service.
I filter (almost all) of them into folders that don't notify and then they are there ready to read across all of my devices that are logged into my email.
I find that email clients are quite suited to RSS reading. They have folders, searching, filtering and unread/read/deleted tracking that is synced cross-device. And for the few feeds that I want to be "urgent" it is easy to send them to my inbox.
Yes! My favorite RSS feed reader is mutt (and the email ecosystem around it like procmail).
With email I already have infinitely flexible filtering, sorting, on-the-fly modification of headers and content, and a reader with best in class threading and TUI.
So I use RSS to email to inject all the RSS content into this ecosystem and inherit all the goodness of email for RSS as well.
I know. Everyone is different and there is nothing wrong with that. I don't think RSS-to-email is for everyone. And I definitely don't have (most) feeds going to my inbox. That would be far too much. The vast majority of my feeds go to a "Not Important" folder.
I also find it interesting that running an RSS-to-Email service I have noticed that we both fetch feeds from and send mail to kill-the-newsletter.com. I would be curious to know what their use cases are.
I filter (almost all) of them into folders that don't notify and then they are there ready to read across all of my devices that are logged into my email.
I find that email clients are quite suited to RSS reading. They have folders, searching, filtering and unread/read/deleted tracking that is synced cross-device. And for the few feeds that I want to be "urgent" it is easy to send them to my inbox.
I have written about my workflow in the past:
https://kevincox.ca/2013/06/27/email-as-rss-reader/
https://kevincox.ca/2023/06/27/decade-of-rss-via-email/