My favorite static site generator is 11ty which is now rebranded "Build Awesome" and is part of the Font Awesome suite of projects.

I'm thinking about maybe writing my blog from here, you know -- the one on scripting.com.

It wouldn't be that hard. I would use one of the static site generators out there.

It would just monitor my feed here, and keep them in sync.

What's the most popular site generator these days? I have no clue. But I have friends and I'm sure Claude has an idea.

That’s one of the many benefits of having Claude as a programming partner.

I read the worknotes and want to express my appreciation for the addition of the instruction about Updating a server you already run. On past projects I often asked how to do this because I wasn't as familiar with command line and node. Including this when announcing an update helps me.

We got a report of a security issue which we quickly addressed and fixed.

Instructions on how to update your server.

This server has been updated as has demo.rss.chat.

I've now foutered my way through sendgrid and for 100 days on the free plan I've got a way to sign into my localhost copy of rss chat.

I am going to try my Raspberry Pi next, probably at the weekend.

Thank you Dave, not sure how the markdown thing happened, luckily I can edit the post ;-)

John we’re going to include your way of working around email in our install notes.

Claude will read this and automatically queue it up for todo++, which should be all I hav3 to do to get it on the agenda.

Also noted that some of your markdown text is showing through encoded. You have to be in markdown mode to use that syntax. There’s an icon above the edit box, an M with a down arrow. It turns green when you click it, to indicate it understands.

Hello, I just arrived here. As I posted to demo.rss.chat I managed to get this running on my mac, without much bother.  rss chat is now [simper to set up](http://scripting.com/2026/07/22.html#a131531)  so I gave it a wee go on local host. So far I've just...

Nice to see you here Anton, ready to help if you need it, and celebrate when it’s running.

Hello RSS.chat. I'm new here, but I know many of you and have learned from you on previous products. I've been following along as you develop this. I'll hang out for the next few days to observe from the inside of the app, then will (carefully) try my hand at setting up a server of my own.

Another test. 

If this works we will finally have caught up the Slack and GitHub in the pasting department. ;-)

Threadwalker example app has the code to crib for this. 

I'm experimenting with reading `source:comments`. Should there be a feed that is a flat list of all replies in a thread? Right now it appears I would need to follow a thread through multiple comment RSS feeds, since each reply can have its own replies.

You're all set then, you know how to handle what we ship in our feeds. 

Good to know. ;-)

Fresh install of rss.chat with SQLite was successful. 👍

Technically we do store hierarchical data in the database — each reply knows the reply it's replying to and the root post — but we only display replies as a flat list. I had intended to have a mode where it switches to hierarchical when a conversation has gotten long and out of control, but never got around to that.

Thanks Manton!

Keep us in the loop on what you do, and if there are any nice-to-have or must-have features. 

Are your conversations hierarchic?

Just fixed compatibility with RSS.chat feeds in Micro.blog. Next up is to figure out if we can process comment feeds to view RSS.chat conversations within Micro.blog... A little tricky because of how Micro.blog assumes hostname usernames.

It would just be a command in a menu. We have lots of room to grow there.

I’m looking for things to put there, user interface improvements are the most visible.

We tried out a lot of different ways of doing this, the switch between timeline and structure. 

I had a product in the early 80s called LBBS that had a neat way of doing this, but it was a scrolling display, where things like that worked. We tried it here, but yuck. Didn’t work.

Also in the UserLand discussion group we had a flip switch like that but you could see only one level at a time.

I’m willing to put an experimental feature in for you. I think the idea of expand-all is easy enough, would have to have a limit because there could be a lot under any node.

Well, I can do that easily but it's another thing that users have to know to do that. Timeline is dead simple in concept. Having to explain how things work feels like adding a lot for little in return because they are visible stains in the timeline context.

Anyway, I'll try implementing this idea to see how it actually feels as I'm no stranger to surprises.

Working on it. As usual, I got too many ongoing projects like a forgetful gopher.

Don I think I have to try your product before I’ll understand.

Maybe what you want is a command to expand all the subs under the current post. We don’t have that now, but it wouldn’t be hard to add.you can already focus on one node by clicking on its permalink, by convention, clicking on the timestamp.

One idea I had on ways to integrate rss.chat into bside, a Chrome extension, is to map rss.chat rooms to URLs. Any link can be associated with URL currently and I'm going to be adding [popular] site-specific URL parameter awareness.

For example, I could associate a rss.chat link to a geolocation so anyone looking at the location on Google Map see the chat in the browser sidebar. It could be a town or some notable location anywhere.

For maps, geolocation + radius would be used instead of embeddings. Thoughts?

I’ve been thinking about how rss.chat handles replies. Right now, balancing a main timeline with inline threading can sometimes lead to UX confusion. A potential solution could be handling threads as separate, dedicated chat rooms—similar to Slack's thread model. Visual Exam...

Everything seems to have worked quite nicely. Soon it will be time to break for the day. 

But it's been quite a day here in daveverse, with my excellent programming buddy, Claude.

Now we're running the new server software on rss.chat.

Not yet on demo.rss.chat.

We're testing a big new feature in the next few minutes. 

Can't wait to tell you about it, esp if you're thinking about running your own instance. 

It's about to get easier. Fingers crossed.