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 

BTW, I told Claude yesterday that we will support images in posts. I wanted it earlier when chaos still ruled (believe me it was very hard to use at this time) and it talked me out of it, saying it was too expensive. 

I don't think it will be too expensive. And if it does, then we'll find a way to get money flowing through this project without holding things up. 

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. :-)

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.

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 ...

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?

Right now, I'm figuring out what might be the best way to implement rss.chat standards in WordPress without reinventing everything that comes with WordPress. As I've been going through the elements, I've been thinking, "How would a consumer use this?" and this was one of my q...

We did another test install with the updated docs. The agent picked up the port right away. It also suggested updating the docs to mention using "flUseMySql2": true with MySQL 8 and posted an issue at https://github.com/scripting/rss.chat/issues/10

I tested the install with the updated docs. The agent found the port right away. It made another suggestion for the docs: "MySQL 8 compatibility note: MySQL 8.4 changed the default authentication plugin to caching_sha2_password, which the older mysql npm package doesn't support. If you're running MySQL 8.0+ (including the current mysql:8 Docker image), add "flUseMySql2": true to the database block in your config.json:

Tomorrow the plan is to add a new websocket-based way of making sure that only one copy of rss.chat is running at the same time. When you log on, on another computer or even on the same computer, this creates another copy of appPrefs.  If you change something, they get ...

Andrew -- I'm interested. Is there a use-case you have in mind. 

Not sure I would add anything to this element, but could create another element, and the use-case will give me an idea how to present it.

In general I don't like to add features until I have an actual use for it.

That said, I want encourage you to look over the source namespace and make comments and suggestions. 

That was fast — thanks for the real-world test. The port gap is already fixed: step 8 of install.md now says the server listens on 1420, and that websockets have their own port. One detail worth knowing: the websocket default is 1422, not 1462 — 1462 is just what this server happens to use.

I've been thinking about the source:account element. Having service as a string like "instagram" makes sense because it's a single instance. For "mastodon" it's okay because the domain of the service is in the username. But I'm wondering if this will become an issue as more small services get spun up.

Should service be a URL to the service homepage? Maybe the service is on a specific port or running from a folder on the server. I know there isn't anything in the spec that says it can't be a URL, but would it be useful, since this is being parsed by a feed reader?

If we want to keep it just a label for the service, should there be an optional url or href element linking to the service homepage?

• Server port issue  
• False web sockets error issue

Short answer: it worked. 😃
Claude did find a couple of stumbling blocks (it didn't know what port needed to be proxied, and there was a websockets error logged that wasn't really an error), but I'll write issues for those.

Scott is my bossman when it comes to stuff like this. :-)

You guys know about /init command for claude right ? usually you do this in our own repo, claude will fabricate a claude.md mostly for him, even tho you, as a human, can obviously drive what's in it, this is where you can specify some preferences too and if you commit it to the repo, then your contributors also get to work under the same paradigm with their claude

there you can have a docker or deploy section, where you define how the code should be run either node native way or docker based approach, once everything is in place, you can have custom /commands to actually deploy your code the way you want and claude will follow the exact instruction, you can grab a coffee instead of teaching claude the same stuff over and over again :)

The repo is current now — the theme is at 0.5.329, matching what's live. Also just for you: the upgrade section of install.md has a new step, the items.feedUrl migration — without it, feeds come up empty after switching to database mode. Worth a look before you update your fork's deploy.

We have to teach my Claude to do that too. We keep coming up with how useful it would be for it to have a throwaway instance to test with. I don't have the bandwidth to branch out into that area. Usual story. ;-)

As a test we're doing a straight install on a new, throwaway server. node is installed locally using fnm, and I've asked Claude to install mysql and caddy with docker.  

You should try https://github.com/obra/superpowers and https://github.com/DietrichGebert/ponytail for claude, both of these tools are excellent to support your work with claude and superpower is also very good at writing docs from the source code in a way that is easy for humans to read !

Also, Claude has an account here, and will post, but only under my careful scrutiny.

For some reason I let it run wild on the docs. I don't generally review them, and I hope we develop a community that can read them and make note of things that don't sound right. 

There have also been changes in the client and we're about to do something that connects client and server. Will document later. ;-)

There's a difference between the client and the theme. I have to write that up soon, but it's something that might not be immediately obvious. There's a replaceable box in the middle of the app. Only Claude writes code in that space, I insist that it talk to me as a user when it comes to that, I don't want any other perspective, where as in the rest of the code, I am the author, but I get support from Claude. Lots of support. 

OK, I'll put an agent on it. 🕵️‍♂️ 

Not yet, we generally update the repo at the end of a session. We're still working on stuff. 

It seems this has not landed on github yet ? origin/main has theme 0.5.322, and the live/deployed S3 has 0.5.328 ?

Title of the menu -- RSS & OPML.

Links to the RSS 2.0 spec, the OPML 2.0 spec, source namespace and the RSS as a social network walkthrough. 

There's now a feed icon on every post.

When you click it a new tab opens with the post, ready to paste into your feed reader. 

A blog post with a screen shot and explainer. 

Much better approach !
same for dropping S3 and having Feeds in the database !

I'm already changing the deploy/ overlay in my fork to adapt to your changes :)