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! ;-)

I think it's cool if there's something micro.blog can add to rss.chat -- so we create the idea that people use both our products because they're different and they interop. Not saying I won't do it, but it's also cool if we don't have to. In the back of my mind I was thinkin...

hello world 

Because RSS already has a link element, it would be really ugly to recommend that people do something so heinous that depends on a reader being liberal to work.

It would have to be <source:link>. If that works I'll be doggone. 

Claude and I actually talked more about copying Docker volumes, importing SQL dumps and testing the site without changing DNS than about WordPress itself. 😀 

That's cool. The interesting thing is that what tags or discovery method you use is actually irrelevant to my server. You could try putting it in without the namespace and we could test out different feed readers and see what is supported.

I imagine the WordPress community is on top of this?

Wonder if they discuss this somewhere..

Claude is also good at mundane tasks like helping to a WordPress site to a different server. We first did a dry run. It caught some things I missed, I caught some things it missed, and we ended up with a pretty good check list. The next day we went through the list, changed the DNS, and everything just worked.

Jeremy Herve, who I know from Automattic, asked a few questions which I answered.

that's an interesting idea. a group of us get together and decide that since html already has a link element that works the same way atom's does, why bother with the atom part. 

their motive goes back 20 years, that little thing has been over forever. i think it's better if we try to fix it, and this idea gives a whole new approach. 

andrew, are you tuned in?

For whatever it's worth, my parser in Micro.blog isn't strict with link tags. It would find your rel="hub" example even without the namespace.

I heard about technography from you when we worked together at UserLand, and the concept stuck with me even to today. 

Back in 2014 I did a presentation at work about some of the tools I was using for my job, one of which was an outliner (I've actually forgotten now which one). Of course the presentation and discussion were facilitated in an outline, and discussion notes landed there. I shared the OPML file with attendees afterwards, including notes taken during the meeting. More than one person asked me later how I thought drive the presentation this way, and I was happy to pass my own spin on technography forward.

That’s fine. It’s all 100% opt in. :-)

It’s been quite a day. At the end, rss.chat is a thing.

More new stuff tomorrow.

Claude is a great freaking partner.

It's very low on my list of things to do, unless it rises to the top, say Feedly, for example, really wants to incorporate our stuff, and they refuse to look for the cloud element. (Which on its face sounds ridiculous.)

I'm more concerned with peering with apps that are trying to create a social network with RSS. That's who I want to work with most.