Why feeds mattered more than Reddit thought
RSS was the quiet backbone of a lot of Reddit tooling. People read a dozen communities in a feed reader without opening the site. Community Discord servers echoed new threads into a channel through an RSS bot. Moderators watched a comments feed for a thread that was heating up, or a search feed for a phrase their automod rules could not express. Reddit's announcement that feeds end on 13 Nov 2026 with no replacement takes all of that away at once.
Redlisten serves the same feed paths in the same Atom layout, at api.redlisten.com, with a key in the URL. A reader, a bot or a queue that read the old feed reads the new one after the URL is edited.
For readers
Any listing path takes .rss: /r/{sub}/new.rss for a community, /r/{sub}+{sub}/new.rss for several in one feed, /r/all/new.rss for everything, /user/{name}.rss for an author, and /search.rss?q= for a query. Entries carry the title, author, link, published time and content as before, so folders, read state and filtering rules in the reader keep working.
Edit each subscription's URL in the reader, or remove and re-add the ones that cannot be edited. Do it before 13 Nov 2026 so no reader marks the feed dead. A free key has 250 requests a month and each feed fetch is one request, so one feed checked every three hours fits; a reader with many feeds or a short interval belongs on a Pro key with 50,000 requests a month, as listed on 6 Nov 2026.
# New threads in your community
https://api.redlisten.com/r/yourcommunity/new.rss?key=rl_live_YOUR_KEY
# Every new comment in your community, for the review queue
https://api.redlisten.com/r/yourcommunity/comments.rss?key=rl_live_YOUR_KEY
# A watch on a phrase, across your community and two neighbours
https://api.redlisten.com/search.rss?q=%22giveaway%22+subreddit%3Ayourcommunity+OR+subreddit%3Aneighbour&key=rl_live_YOUR_KEY
# One author, everywhere
https://api.redlisten.com/user/example_user.rss?key=rl_live_YOUR_KEYFor Discord and Slack servers
An RSS bot in Discord takes a feed URL and posts each new entry into a channel, and the Slack RSS app does the same with /feed subscribe. Give either the Redlisten URL and the channel keeps filling. For a community server that wants new threads posted, /r/{sub}/new.rss is the whole setup.
If you would rather keep the key out of a chat tool, a keyword stream on a paid plan posts matches straight into a Slack or Discord channel through an incoming webhook, with no feed URL involved. That route also filters: a stream can carry words that must or must not appear, so the channel gets the threads that matter rather than every thread.
For moderators
Three feeds cover most moderation watches. /r/{sub}/new.rss is the new post queue. /r/{sub}/comments.rss is every new comment in the community, in order, which is the feed Reddit made awkward and the one moderators ask for most. /search.rss?q= with subreddit: in the query catches a phrase, a link domain or a username across your community and its neighbours.
A feed reader with keyword rules, or a Discord channel per feed, turns those into a review surface that is faster than refreshing the mod queue. Removed posts show [removed] in place of their text, as they did on Reddit's feeds, so a reader shows the action without exposing the content again.
For a watch that needs more than a feed can say, a keyword stream over your community with an author filter, a score filter or an exclude list collects matches on paid plans and can email a daily digest on the free one. The RSS switch page shows the URL form in detail and the docs list every feed path.
What stays private
A key in a feed URL is a secret. Keep it inside the reader or the bot configuration, not in a channel topic or a wiki page. If it leaks, revoke it in the dashboard and mint a new one; the paths do not change, so re-adding the feed with the new key is the whole repair. Redlisten serves public content with no logged in view, so a private community does not appear in any feed.