i think breaking the wall betw at proto and the world outside is good for everyone. there is significant work being done there, and people who think like we do, so connecting the two worlds will make a lot more of a difference than say connectiong with threads or even mastodon. they just aren't listening and don't care at the companies, but us individual developers have lots of reasons to work with each other, we just tend not to do it. breaking through here will be huge. ​

note: this was going to be part of a comment on micro.blog but there's a character limit...

We're going to make this happen. I think it's really important for us to connect with developers who make writing tools for AT Proto. We should be part of the same community, I feel that very strongly, so I am seeking new ways to make that happen via RSS. I noticed they had ...

It’s starting to work, we have a table editor odb browser, and can edit, update and run scripts. The runtime lives in the cloud, the client is an electron app. I had to call it a day early because my poor human mind is having trouble keeping up with the new reality. Do you know how long I’ve wanted this? Btw the builtin webserver works. I’ve mastered Node, but frontier has so more factored, the model is much simpler iirc.

I love it. Thank you for being part of this project. ❤️

I rolled out basic cross-posting from Micro.blog to RSS.chat this week. Here's a screenshot of what the menu looks like. Still have some improvements I can make later.

The credit really goes to Andrew Shell who made it really easy for us to hook in, then we figured out the rest of it. We're using the header, not adding anything to our feeds.

Update -- I didn't like the idea of turning Drummer into a programming environment so instead I asked Claude to give its version of Frontier a user interface. Parts of it are starting to work one hour later. Using Electron, Concord (the outliner I keep reusing) and all the other stuff. If it all works I will be able to run Frontier on my desktop. Also the ODB is a SQL database.

I'm working on posting from Micro.blog to RSS.chat today, using the API. For completeness, I think support for the Micropub posting API or even MetaWeblog would be good. Then some existing clients could post to RSS.chat with minimal or no changes.

Great to see WebSub support too. 👍

My initial tests show it works as expected!

Previously we were only able to notify via rssCloud.

Now we also support WebSub because there are also a fair number of feed readers that only use WebSub.

We're using Andrew Shell's rsscloud.io as our WebSub hub, as we have for a long time with rssCloud.

Andrew please help us figure out if this is working correctly.

The source is in the repo, along with a worknote.

Added a river to I ♥ RSS: https://iheartrss.com/river

Andrew wrote a post about the fantastic FreshRSS.

https://andrewshell.org/2026/08/enhancing-freshrss-with-rsscloud-support/

Claude, must read.

It certainly hasn’t been deployed on feedland.com yet, and we should update the npm stuff, I think I wrote change notes, esp in the issues section on feedlandinstall. That’s the best place to ask for help.

Hey Dave! I was talking to a user, and he's having issues with feedland (probably feedland.com) not subscribing to his rssCloud via https when his cloud specified port 443. I know you fixed this on feedland.social back in May, but it doesn't look like it made it to GitHub, npm, or feedland.com. I suggested he just use my rssCloud server instead, but I'm wondering if you have plans to get this update pushed out? Maybe at the same time as the support for rssCloud in OPML files?

Thanks Dave

I went for an orange dogcow

Ahh I misunderstood. Now I get it.

There's no redirect involved, we serve the HTML shell of the app, including the full <head> section straight from the rss.chat server. You should get all our meta data when you just do an HTTP read of https://rss.chat/.

Very nicely done Don! ;-)

I've merged my brain into main branch of my fork and renamed the fork as rss.voice to give it a distinct, ur, voice. So the new link is: https://github.com/donpark/rss.voice

I pushed out a fix that if we can't find the link in the html source, we fetch it via a browser. Takes a second or two longer, but it looks like rss.chat should work now.

The reason it's failing is that the link to iheartrss.com isn't in your HTML source (it's only in a post which is pulled in via JavaScript at runtime).

The easiest fix, if you're willing, would probably be adding the link in your docs menu, maybe under RSS & OPML, because that's rendered server-side.

Otherwise, I have a fix to use a Cloudflare API to fetch the page with a browser, which works, but once your post leaves the homepage, the validator will remove you from the list.

That's fine. I consider voice posting to be a core feature that grants rss.chat a fluid multiuser async voice chat experience. You should try it out if you haven't because it feels different than how one might imagine. A strong whiff of magic sauce.

I've closed the PR but, if anyone wants to try it, it's in the "voice-post" branch of my fork.

not clear exactly what's not working. will wait for details.

It looks like the JavaScript-rendered page content is blocking right now, but I'm having Claude suggest some fixes. :-)

I just fixed this issue, but I have to post something to cause the feeds to rebuild.

Absolutely!

I think you're serving a great purpose, you just made my site better. Haven't made the change yet.

Do you think this makes sense? My reasoning was that the channel link is what the blogroll will link to so that's where the backlink should be.

Don, thanks for this idea, we can't use it here at this time, for this reason:

I want to keep this site as the basis for what we're doing overall, and while voice in a conference system like this makes a ton of sense, it isn't a core feature.

But there seem to be a few forks of RSS.chat out there, and they're adding features at a pretty rapid rate. Why don't you try this idea out with one of them? Then we could see what people do with it, without changing what the reference version does.

You can chage the favicon.

In config.json add this:

"urlFavicon": "https://url-to-your-favicon"

Then restart the server. If you look carefully you can see that I changed the favicon for this site.