Timeline
Posts from the instances this one federates with
-
Something about the UI here is pleasingly tactile.
-
How does
relate to
- https://wordland.social/ & https://this.how/wordland/ & https://github.com/scripting/wordlandSupport
I see that the editor features are a little different. In wordland, there's a little paper-airplane icon that publishes/updates the wordland post on a wordpress blog:
the arrow icons move back and forth between wordland posts, and the + adds a new post.In demo.rss.chat, it's setup like a top-posting chat, where the '+' icon on the side bar add new top-level posts:
and the posts appear to make a tree with replies, and comments.
The header of the post has three clickable bits, The poster's name, (which leads to a list of their posts, e.g.
https://demo.rss.chat/?screenname=drf5n
), a direct link to the particular post (e.g. this one is
https://demo.rss.chat/?id=231 )
, and the poster's RSS feed, so you could keep up-to-date with an RSS reader.
-
Hello RSS.chat. I'm new here, but I know many of you and have learned from you on previous projects. 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.
-
This is a test of the emergency RSS system.
Uploading image…
-
Don't lose sight of what you're doing something in service of.
-
Another test.
If this works we will finally have caught up the Slack and GitHub in the pasting department. ;-)
-
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.
-
rss chat is now simper to set up so I gave it a wee go on local host. So far I've just run it from my downloads folder. The instructions worked but I am a node-no-nothing so I tripped a couple of times.
First I didn't npm install so nothing worked.
I tried to set up SMTP using SendGrid, but I lost the will to live half way through. Got an API key but
Message failed: 550 The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. Visit https://sendgrid.com/docs/for-developers/sending-email/sender-identity/ to see the Sender Identity requirements
So I just copied the magicString from the terminal and constructed my own url:
http://localhost:1420/userconfirms?emailConfirmCode=ysugstk4ycWhich did the trick.
Ofcouse a localhost oneperson social network is not much use ;-) but interesting none the less.
-
“the moral of the Internet’s story is that simple, open-source protocols that scale up tend to win over complex top-down approaches”
Really enjoyed this: The story of how RSS beat Microsoft
https://buttondown.com/blog/rss-vs-ice
“…there was simply no getting around how bloated ICE’s requirements were. Its North Star was automating complex, corporate publishing partnerships. It contained fields for catalog pricing and negotiation, content expiration tags, copyright enforcement functions, and the ability to apply the display website’s visual branding to feed content. While most of them could be ignored, that didn’t make its 58,000-word Getting-Started guide any more digestible”
“”I definitely want ICE-like stuff in RSS2, publish and subscribe is at the top of my list, but I am going to fight tooth and nail for simplicity.” Winer argued in one of the many combative and public RSS mailing lists.”
Uploading image…
-
RSS & emergency response
If "there's also a feed of everyone's posts together," I see that a small group of writers could collaborate on a topic of concern in a single instance of rss.chat, creating something they think of as a single-topic publication.
This could be a topic of pressing short-term interest, and that response would be nimble, wouldn't it? When a weather disaster threatens a region of the country, for example, the tools are already in place here and there's a low barrier to entry for new writers to contribute. The feed would send the posts to a WordPress blog built in minutes for the occasion, yes?
-
If I understand correctly, it's RSS-in, RSS-out, small pieces designed to be loosely joined, and all meant to be locked open . . . yes, please.
-
Fresh install of rss.chat with SQLite was successful. 👍
-
"early‑AI‑history maneuver"
I asked Perplexity to read through 258 posts in my “Snapshots & Fragments” category — the catch‑all bin I’ve used for photos and ephemera over the years — and tell me what it thought was going on. I had a hunch an outside lens might spot patterns I only sense in the gut.
-
I just watched Samsung's Galaxy Unpacked event for July 2026. The lineup includes new and updated Folds and Watches, Open UI 9, and improved Qualcomm chips. Samsung also revealed better tools for coexisting with or switching to iOS, expanded Google AI support, and provided more details on the eyewear collaboration with Gentle Monster and Warby Parker.
-
Photoshop Etiquette: A Guide to Discernible Web Design
https://photoshopetiquette.com/ -
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.
-
First post
Testing rss.chat, the most recent product from @dave
-
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?
-
Timeline vs. Threading
I’ve been thinking about how
[rss.chat](http://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 Example:
User A: Has anyone used this library?
└── 💬 Chat Room: "Discussing Threading" (4 replies • Active now)
User C: What's the news today?**
Implementation Idea:** The simplest approach might be spawning a new chatroom instance linked directly to the parent message, keeping the main timeline clean while preserving focused conversations.If a thread is created as its own feed/chat room with a unique URL:
-
The Main Feed stays simple: It only has to publish one post representing the creation of that chat room.
-
The RSS Readers don't choke: A basic RSS reader just sees a post with a link to a sub-chat. Advanced readers or native UI clients can render that link as an interactive, expandable thread widget right in place.
-
Protocol friendly: To join or listen to the conversation, clients just fetch or subscribe to the sub-chat's specific feed.
-
-
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.
-
testaaa
bold aaaa
-
ddadadadadad
-
Speaking of RSS feeds, you periodically go through all of the feeds in your aggregator and see if they are broken, right? And if they are, you update the URLs or just unsubscribe from them, I assume. And if you know what's wrong with an RSS feed (sudden absence, malformed, URL has changed), you contact the author or the publication. And if that doesn't work, you create an RSS feed out of the site using tools like Huginn or NewsBlur (one of its paid tiers has a feature to turn any website into an RSS feed). wouldn't say I've gone as far as Chris Hardie, but I've done a lot of those things.
-
RSS is still RSS, picking up where we left off
A lot of people are confused about wtf this is.
I don't blame them. I put out there a partially implemented vision.
But the vision isn't really new -- it's a turnback to 2002, and what UserLand would have done if we had continued pushing, which we did not.
At the time we had a product named Radio UserLand that was an integrated writing and reading platform, very user friendly, and it worked, all done with RSS. It also did podcasting if you can believe that.
So here we are 24 years later. RSS is still RSS. And we still have feed readers and blogging tools, so how does this become a social network?
http://scripting.com/2026/07/21/134309.html
That's where it's at right now. This is the writing environment. I have yet to show a new reading environment, but that's okay you can use NetNewsWire! It works. I didn't even tell Brent this was coming. Why is that? Because we use standards.
I don't have enough places to fit all the ideas these days. But we have been digging and the pieces seem to fit together just right
-
Well, well. This is exciting
-
Well this is interesting. Just trying to figure out how it works.
-
Crosspost from here to microblog
It's actually pretty easy to crosspost my notes from here to my blog on the Micro.blog service. Just add the feed to my account > Sources and I'm done. Easy.
- Updates on this weekend's activities: Notes from rss.chat land
-
Testing inboundRSS
Just saw the notice about the rss.chat example inboundRss for wordpress . I must say I hadn't thought about going that way. I had wondered about POSSE from WordPress to rss chat.
Currently micro.blog does a great job of posting items from my feed to mastodon and bluesky. I've also used FeedWordPress to pull rss feeds from one place to another.
Where inboundRSS differs is that it runs in a browser served from somewhere. The notes suggest it could site on a server or be served via node locally. I guess a simple php script could work too? inboundRss also updates edited items in real time (a few seconds).
I've run through the instructions, I had a bit of difficulty getting my site id, but got that from the WordPress.com API console using GET /me/sites/
I thimk the problem might be that my site is in a folder not at the top? I tried with a couple of other WordPress sites I run and the documented way worked for them.
Once I'd filled in the id and my demo.rss.chat feed I run the file with `php -S localhost:8081`
All I need today is do now is publish this post and it should also go onto my WordPress site. I'll check that and then test editing here by adding a link...
And it worked: Testing inboundRSS
I've now made several edits and they are reflected on my site. I put the php snippet for the terminal in backticks, they stayed as backticks on demo.rss.chat but were converted to code tags on my site.
I am now wondering what happens to edits on the WordPress side? If I added categories & tags? Enough for now though. Lots to think about!
-
test
test xpost to wp
-
xpost to wordpress test w/asciidoc
Asciidoc here…
The four-network test: written in AsciiDoc on su.perstitio.us, rendered with inline syntax highlighting, and mirrored to WordPress over the firehose.
(defn survives-the-trip? [colors] ;; perstitio -> firehose -> browser -> wordpress (every? #(= % :intact) colors)) (survives-the-trip? (repeat 4 :intact)) ;; => true, hopefullyAnd a little bash for contrast:
curl -s https://shjeflo.org/ | grep -c "color:#" && echo "phosphor confirmed" -
test xpost to wp
this should show up on wp
-
I still think there needs to be a setting to allow users to set a default view of threaded. The way that rss.chat does this is the same as micro.blog and twitter before it amd all are inconisted with message boards and bbs The challenge is working out notification of threads that have been updated. I would just bump the parent and responses up to the top. I think fundamentally threaded messages and rivers/timelines are incompatible but that may just be me.
in my mind chat is real time messaging, which is not this. To me this is more accurately described and a message board / forum that uses rss. RSS really doesn’t need to be in the name beyond making a point.
And chat / messages is not writing and I don’t know why Dave is so obsessed with merging blogs and chat. Besides what he claims to want Manton already did.
