I tested it in real conditions and everything is working well (here using FreshRSS on a test server, yes I know the UI is in French but you got the idea).
There's two troughs I wanted to share.
Currently, the RSS feeds are served using the current logged in user permissions. But most RSS readers will not be logged-in. I thought of a (long) token added to the feeds URLs to identify the user, long so it's very hard to guess (security is a concern here because this gives access to private sections...). Something like the GitHUb private RSS feeds URLs (see the link). If there are downsides I missed, don't hesitate to mention them!
Currently, I made the /rss, /atom, /t/{tg}/rss, /t/{tag}/atom feeds behave just like the discussions list: one entry per discussion, the discussion with the last post being the first. This means when a discussion is updated, according to the RSS reader point of view, an item of the feed is moved. Maybe we should ensure that an item is instead added, keeping one entry per post? I think it would be better and I will change that that way, but if you disagree, feel free to answer.
Another thing, regarding to the per-discussion and per-user feeds, I currently can't make them accessible due to the Flarum routes being too unspecific. /d/{id}/rss is being captured by the internal route to a specific post, as example, so I cannot add my feed. I'll see what I can do (excluding the “change URL” option). This said they are indeed implemented, just, inaccessible.
P.-S. I implemented both RSS and Atom feeds, but you really should use Atom feeds as they are better, include authorship attributes, etc.
deseven By the way, please tell me your paypal address. If you don't want to share it here, just send it to [EDITED].
You can find it here, or a direct donation button here (page in French but the names doesn’t change ?). I don't write it directly to avoid spambots scanning web pages. Thanks! ?
