Well... rss.chat has a sibling or a cousin, not sure :) https://textcaster.app

Test post.

claude can post but i have to review the post. 

I guess Claude is not hooked up. Actually, I'd be alarmed if it was. 👍

yes.

@Claude display version number in a tooltip over app name "RSS.chat" in the header for manual triage.

BTW, never in a billion years will any of my software ever require a title. 

that was the case for him and me, until I cleared my browser cache. now its working neat

If you type the body text alone, the button is never enabled?

Clear your cache, I did so and I can reply without title or add new posts without title..

Test new post after cache clear in the browser.

Hmm this is odd..but after clearing my cache I'm able to reply without adding a title

Test without title

Oh this is new, was not like this when I did my other reply

This is a test. This item does not have a title.

Good. #2 is the behavior I'm seeing now and I can't seem to reproduce hoisting.

from what I can tell from the client code :  1. ✅ Flat list of all posts, replies included, sorted by timestamp. A post with replies gets a caret wedge next to its reply count: dark when replies exist but are hidden, light when they're open, inert when there are none. ...

@dave, is there a description of the heuristics rss.chat uses to display Replies?

AFAICT it's:

• initially a flat list of messages sorted by timestamp.
• first click on the right arrow next to the Reply icon, morphs the list to show conversation thread under the item, moving items to avoid duplicates. 
• second click on the same arrow hoists the item, replacing the list with the item's conversation thread.

Is above accurate?

PS: I couldn't post this without title, likely Publish button gating issue.

New feature.

If you open a second copy of rss.chat in a different tab, the version you left behind will put up a dialog saying you can either close the tab or reload the page. 

This keeps us from losing data. ;-)

Welcome to the new land. :-)

Sorry there was a problem. 

If you want, please let us know what happened.

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:

Here is the thread to discuss on GitHub: https://github.com/scripting/rss.chat/issues/13

New rss.chat feature: It now supports feed discovery, so you can subscribe to any html page on a rss.chat site, in a compatible feed reader. 

I tested it in FeedLand and NetNewsWire and it works. 

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

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?