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. ;-)
Andrew I sent an email to Jeremy Herve at Automattic, cc'd to you.
I authorized his email account to be part of the discussion here.
At some point you should open a thread where everyone can participate on the repo.
Here is the thread to discuss on GitHub: https://github.com/scripting/rss.chat/issues/13
Andrew, I just wrote a post on my blog about Mastodon, and how it assumed Twitter's feature list as their todo list, and why imho that was a mistake.
We're just getting started here, and I want to go easy on nailing things down. I wouldn't limit rss.chat to only working with AT Proto (for example) as lots of developers do. Instead I'm not working with it, and hope to pull Bluesky out of their non-web architecture out into the wild web, that may not have made Bluesky possible (they grew out of Twitter) but it certainly made Twitter possible. ;-)
So that's why this might not be a solvable problem at this time. But starting the discussion with the WordPress people, well, it's always a good time to do that. :-)
Doubt you can move Bluesky out of its current track, the direction they seem to take is to expand their lexicon to all kinds of usage (blogs, instagram clones, livestreaming, even federated code repositories etc) this link gives an overview of the current diversity being built in the open ecosystem
overview of shared data types here :
https://atstore.fyi/apps/lexicons
But that being said, the community is very open, its easy to build uppon and even to diverge from the current protocol akin to what https://standard.site is doing
I'm glad you're looking at this, of course I am too. Been using Twitter for 20 years, and gave up trying to get cross-posting working in 2017.
I would love to talk about this, because the text limits are the only thing holding their dynasty up, the fact that their limits are different from all their competitors. If there was a universal definition of what "web text" is -- well they'd be screwed. It wouldn't matter where you wrote the text, it would still play on Bluesky.
And if we didn't have to no one would use their editor.
Same for Substack btw. I wanted to do my writing in my editor. No can do, they say.
I think that incompatibility is the only thing holding up their dynasty, the idea that 300 is better than 10K as a character limit.
The pressure on them to do it is coming from Leaflet et al. Either Bluesky relents, or we'll eventually get them working with us on the web, where there are no freaking character limits.
What do you think of that?
PS: They would also have to support inbound and outbound RSS.
PPS: I chat regularly with the Leaflet people. Very smart and business-like. I also know the new Bluesky management, somewhat -- he comes from Automattic. I had a meeting with him a couple of years ago basically to talk about storage and identity -- they were launching a new identity service, and I desperately wanted them to add storage so we could have an ecosystem of apps sharing data. That part of what AT Proto is doing -- I support, but the business model is all wrong. The users should pay for the storage, and give permission to apps. The Leaflet style app is reselling Amazon S3 storage, which is a shitty business for a smallish entrepreneur.
PPPS: If Toni reads this, I'd be happy to chat. It's all getting sooo interesting now.
I've been thinking about this too, tried to leave a long comment here but that didn't take. I ended up leaving a reply on the GitHub issue you started:
https://github.com/scripting/rss.chat/issues/13#issuecomment-5004476275