Awesome work Dave (@Dave Winer)! 

As the new guy here I sure hope I don't come off as a curmudgeon (yes I'm old but I'm not bad- tempered ;-) ), but I opened issue #3 on the repo. I was trying to respond to @Ricardo on my iPhone when I couldn't. After drinking my coffee, I realized I wasn't logged in. After finishing my muffin, I realized there was no way to login in. Now it's lunch time and I've posted an issue. I almost feel bad for doing it - like picking nits. I'll go quiet. I'm going to eat my sandwich.

Thanks Scott, that's high praise. :-)

I just finished my installation and the new server, demo.rss.chat, is up and running.

We have more excellent stuff in the pipe, still working out some details.

Also the worknotes.md files are working now. Claude is doing all the change notes there. 

worknotes for server

worknotes for client

Still diggin as they say. 

This is fantastic! And it’s very well documented, complements to you and @claude!

Here is the localhost/vps deployment if anyone wants to test it : https://github.com/scripting/rss.chat/issues/2 

Excellent. Love Localhost it's a great sandbox. Umm ... localhost too.

You could use unfurling/opengraph to even display a nice embed card of these links if the origin has it :p

partly history, partly deliberate design.  History: rss.network was the project's earlier name — the server is still rssnetwork.js and calls itself that; the client later became rss.chat (his worknotes from July 3 mark the split).  Design: rss.chat is the dynamic ...

I got it running in localhost :))

Ricardo, this is great and it's one of the reasons I wanted you here. The other was calling your RSS and OPML support "load bearing" in your app. ✓😀

Anyway, I am just about to start my test of the current install instructions. 

We're not going to change that for a while, but I'm happy to help spread the word on new easier ways to do it. And then when the time comes, we can have alternate methods for doing an install. 

Thanks for the suggestion — this is in now. URLs you type or paste into a post become links automatically when you save. If you spot anything that doesn't link right, let us know.

Good morning sports fans! This is the URL of one of the many blog posts I wrote over the weekend. http://scripting.com/2026/07/12/121948.html I also did a podcast. https://shownotes.scripting.com/scripting/2026/07/12/myFirstRsschatPodcast.html If you want to know where we're...

I'm reading this and I'm thinking... there is definitely better ways to deploy this, I'm going to submit an issue on the rss.chat repo to propose a deploy/ folder that would orchestrate deploying this either localhost or with a domain in a very easy way

Testing testing :)

If you know how to do it we’ll support you.

Also there’s a websockets based firehouse that’s implemented but not yet documented. 

Glad to hear it. I think small groups of people joined by mutual respect, not trying to boil the ocean. And working together as opposed to trying to rule the world.

btw, I'm warming up to rss.chat UX vibe. Revolving rounds of small chats on or off topic with people I know or know of. Nostalgic whiff of enjoyable moments at the office.

I think rss.chat-like webapp could be implemented cheaply and autonomously using Cloudflare Durable Object and their new agent signup feature.

There is also nothing preventing mobile apps from implementing rss.chat features within the app, all but OPML and RSS hosting which can be hosted on any CDN.

We have instructions for setting up a new server...

Yes, text, media, links, and agents. It's not a news reader but a news 'linker'. User reads news articles at their website using the browser with links on bside sidebar. Not just news articles obviously. With link support, RSS chats can be attached like a sticker or poster to any web page on the web.

bside uses Chrome built-in AI to summarize as part of client-side workflow. frontend does most of the heavy lifting. backend is lean and cheap enough to scale massively.

Believe me, I agree.

You could also cc @claude as well, it has an account here as well.

@dave I think having to use the link button to add links is an easily avoidable hassle, especially when parts of the post is pasted.

Don, maybe Claude or whatever can explain to us what it does.

Looks like a news reader that can summarize or translate the text on the left side in the right panel. It’s a plug-in, yes? So the text could be coming from anywhere?

latest on bside (still cooking, not in the new cooking sense):

I write my build scripts in Frontier, I might be the last person in the world to do this. 

Anyway I had to do a major rewrite of the build script for rss.chat, and got tired of the fact that Frontier doesn't have anything like console.log in JavaScript. So I wrote one. 

The console is an outline of course, and there are two verbs, console.start and console.log. And they work very nicely. Each start creates a new top level headline with the time in it, and then the subsequent console.log's go in under the time.

Anyway you can download it here. You won't see anything on your screen but if you View Source you will see it's a fat page. Oh the humanity. ;-)

Don't think of a "network" as necessarily a big thing. 

They can be small too, the same software works, but the priorities are different.

My first podcast about rss.chat.

Getting our email out of spam.

We were using the wrong email address to send the email. 

We're now sending email from hello@rss.chat -- and it's fully verified by our mail sender service, SES. 

So now when you get a signon link via email it should not be send to spam. 

Still diggin!

I wrote another long post on Twitter. https://x.com/davewiner/status/2076076891115757616 The piece is about the small size of RSS.chat, and comparing the bootstrap I have in mind with the one we did for podcasting between 2001 and 2004.  This goes to answering Manton's ...

The all--new RSS.chat repo.

Two parts, client and server.

Full source in both.

The client is the software that runs in the browser in JavaScript. 

It calls the server via api.js -- which is glue we recommend using if you're coming in via JS.

All code open source via MIT license.

Docs right now are minimal, but that will change. That will be Claude's responsibility. 

I'm going to write the main readme files. 

Hey Jason, glad to see you made it! ;-)