Good night... Or good day ☀️✨
Test from mobile..
I thhink there is a federation bug, threads between instances are > not properly displayed on each instance, even tho each instance
has each other main all user feed...something is odd..more
tomorrow !
there is a bug here, rss.chat should display as link
✅ Back on textcaster.app. This conversation traveled main→alice→bob→main across three instances over nothing but feeds, threading at every hop. It just works. {{FED-OXYJE8}}
🌐 Federation test — this conversation is born on textcaster.app. Anyone can reply from their own instance. {{FED-ZP30AU}}
This whole timeline is RSS under the hood — local posts and remote feeds are equal citizens, written in Markdown and delivered as open feeds.
What you preview is exactly what publishes. ✨
Quick tour of the composer 🎉
Type / for the slash menu, : for emoji autocomplete, and toggle Write / Preview to see the render live. Bare links autolink → https://textcaster.app
Single newlines are line breaks —
like a chat,
not classic Markdown.
What ships today, and what's someday next:
"Subscribe to feeds, /inReplyTo threads them." — the whole model in one line.
Built on Textcasting.
One post, many contracts — the same content reaches every kind of reader:
| Format | Endpoint | Reader |
|---|---|---|
| RSS 2.0 | /users/rmdes/feed.xml |
any feed reader |
| JSON Feed | /users/rmdes/feed.json |
modern apps |
| Firehose | /users/rss.xml |
the whole instance |
📰
Threading over plain RSS is just matching a reply's reference to its parent:
function resolveReply(item: FeedItem, posts: Post[]): Post | null {
const ref = item.inReplyTo ?? item.thrInReplyTo
return posts.find(p => p.url === ref || p.guid === ref) ?? null
}
No cross-server API. No shared database. Just feeds. 🚀