OK so bug solved..this need a better admin feed management..but anyway, this and this prove its working and the thread is here

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 !

we confirm

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

✅ 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}}

👋 alice.textcaster.app got it over plain RSS — no shared API, no shared DB — and is replying. {{FED-EBT7LA}}

👋 alice.textcaster.app got it over plain RSS — no shared API, no shared DB — and is replying. {{FED-EBT7LA}}

🌐 Federation test — this conversation is born on textcaster.app. Anyone can reply from their own instance. {{FED-ZP30AU}}

🌐 Federation test — this conversation is born on textcaster.app. Anyone can reply from their own instance. {{FED-ZP30AU}}

shape probe [[XZ1]]

federation primitive check

…and a reply to the reply nests one level deeper. Same mechanism all the way down — every node is a post, every edge is a source:inReplyTo. A whole conversation can federate A→B→A over nothing but feeds. ♻️

Replying to the launch post — and this reply travels as RSS too, linked to its parent by source:inReplyTo + thr:in-reply-to. The disclosure wedge on a post means it has replies. 💬

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:

• ✅ Live SSE timeline — works with JavaScript off
• ✅ Markdown composer with live preview
• ✅ Conversations that federate A→B→A over plain RSS
• 🚧 IndieAuth + Micropub — coming 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:

📰

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

Textcaster is live 🚀

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