Still trying to wrap my head around this emerging world of 'RSC' .. or whatever we end up calling it.
Is this the same underlying code as rss.chat from Dave Winer .. or something else .. the UI is a massive improvement.
its an implementation from scratch of "textcasting" by Dave Winer, the only parts that were directly taken from rss.chat is the usage of the source elements and the InReplyTo logic to construct the RSS feed, the idea is to interop with whoever wants to.
I initially thought about doing something about this powerful idea in February of this year, I had used Claude to transform the textcasting manifesto and a few linked pages into a Specification that I could use with Claude or another AI tool, then I got very busy at work and personal life and then rss.chat came about and that's when it clicked into my head. What if I could use Fable 5 to replicate the idea but with a different tech stack ? the history of the github repo from its initial commit to current state is how it was done, spec driven development, incremental optimization, careful architecture so that backend and frontend can be interchanged, tho that remain to be tested. Right now RSC federate between RSC implementation, it can also ingest rss.chat inbound but our output (all user feed) has not been tested outbound, neither federation of comments between instance
I have been a RSS fanatic since more than 20 years and have had different ideas about RSS that were never implemented, this time, when it clicked, it took me perhaps a week to come up with this implementation and prove that federation between instance was not just theorical but possible.
Some of the posts in this POC are precisely that : a proof that peope could have threaded conversations over RSS even when posting from different instances.
I'm not going to lie, I'm more than excited about this !