When we're talking about the rules for interop with rss.chat, is there a specific name we're using? Like, would it be an "rss.chat" WordPress plugin?
I read the interaction here: https://demo.rss.chat/?id=57 and the part where you said "treat comments as blog posts with their own permalinks" made me wonder, because this is not a rule from Textcasting.
For instance, I could in the main feed add `` and link to a comments feed (like https://test.geekity.com/2026/07/16/hoopla-world/feed/), but those comments don't have permalinks, just an anchor tag to the main post. So this wouldn't be compatible?
1. Yes -- the name is rss.chat.
2. It's not part of textcasting because it isn't about text, it's about structure.
3. Is all that's in the way is having a permalink for a comment? Can comments in WordPress have comments?
I don't want to be held back by trying to work with an existing product that has a different view of the web. WordPress is very close, because they support textcasting, but their view of discourse is not as simple as rss.chat's view and at the same time not as powerful.
They do it the way comments on blogs have always worked, more or less, although I should point out that discuss.userland.com didn't make a distinction between comments and posts, nor did its predecessor LBBS. We had those kinds of discussions while this was under development. I did offer to work with WordPress on this stuff, but they went in a different direction -- ActivityPub and AT Proto. I do think eventually they will want to be involved here. Since they've been pioneering a new path here, maybe we should find out what they think?
Anyway -- I will send a link to this post to Jeremy Herve at Automattic, he commented on this last week when we rolled it out publicly, and he's a good guy -- I think they went the wrong way, but I've made a few bets like that myself. ;-)