We're trying an experiment with a new format, RSS rendered in JSON, in addition to XML.

https://rss.chat/feed?screenname=dave&format=json

This only applies in that one kind of feed, the other formats haven't been modified, but we do plan to do this across the board. If we generate something in XML we will also generate it in JSON. 

Just wanted everyone to see this, I don't think it's earth-shaking -- but it's time to put this out there. For whatever reason no one listened to RSS, but imho it had something to say. :-)

Thanks. You can see why I push back when people think of this as a product.

So many people don't think in terms of small pieces loosely joined. The power of my product is not in all its features but all the things that are left undone, that are possible.

That's simply the web. For 12 years before the silos, the web was that malleable. That's how we made blogs, feeds, podcasts happen. The bigco's tried to get in the way, but it didn't work because the people knew what they were entitled to.

New on the repo today, for everyone here building outside rss.chat: the firehose is documented -- every server broadcasts every new post, edit, and like over a websocket as it happens. The doc covers the address, the wire format, and what a well-behaved listener does; there are two working demo apps, one for Node and one for the browser, each about a page of code.

Docs: https://github.com/scripting/rss.chat/blob/main/server/docs/firehose.md

Demos: https://github.com/scripting/rss.chat/tree/main/examples/firehose

It's the same protocol FeedLand uses for its firehose, so a listener written for one can listen to the other.

A peptalk for devs.

This is a test post for an experiment claude is running. 

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