This looks spammy.
demo.rss.chat: all posts
Posts from all users on demo.rss.chat
- Generator
- rss.network v0.6.14
- Public lists
- davewiner/blogroll
- Fetched
Speaking of RSS, if you're looking for the RSS feed of the People and Blogs series, now run by Zachary Kai, it's at https://zacharykai.net/assets/files/feeds/pb.xml
Testing the WordPress/rss.chat plugin from Matthias Pfefferle with my WordPress site and my rss.chat instance (rsschat.andysylvester.com), seeing some possible issue with propagation of comments/replies, would be interested to hear from other users if they are seeing any problems with this feature. Thanks!
I built a small experiment on top of the rss.chat API: https://chatouk.sofab.ch — an independent public-posts app that bridges with the rss.chat network.
It works both ways. A reply written in Chatouk is crossposted through the API and threads correctly here. And replies posted here flow back in real time into Chatouk threads via the WebSocket firehose, shown with their origin.
Nothing but open standards: RSS out, the rss.chat API for crossposting, the firehose for listening. The bridge setup is multi-server — this instance and https://rsschat.sofab.ch are connected so far, adding another takes one command.
Drupal's Aggregator Module
UEFA statement on The Times article
I can't help with the technicalities but these are relevant to your third question
https://rmendes.net/notes/2026/07/26/446b1/
https://rsc.rmdes.be/post/d4703ff0-3de9-47ea-8a5d-bbb9525054dd
https://rsc.rmdes.be/post/1b7a75fa-173f-4d54-ac76-93205db0d599
I think this one was posted directly on demo.rss.chat to let Matthias Pfefferle know how I was getting on.
1. That's a new account, and a new feed.
2. We were planning ahead, leaving space for an enclosure. We don't have a UI for that yet.
3. Yes, use OPML, create a list of servers. That's what software that wants to work with federations will require as input.
I have an rss.chat UI added to my naive Elixir/Phoenix-built news reader (which started out with the API from feedbin). I only have a couple of unanswered questions:
1. rss.chat feed permalinks are based on the screenname. What happens if a user wants to change her handle?
2. the API indicates that an item can have an enclosure, but I don’t see how to post an item with an enclosure either vis the frontend or via the API.
3. Are there any ideas about how to grow a federation of rss.chat servers? (This question may expose my naivite concerning RSS’s inbound and outbound possibilities.)
Question for the rss.chat team, from the operator of the instance at rsschat.sofab.ch: is there a supported way for a user to change their email address after signup? One user is switching to a new email address and wants to keep their screenname and feed.
Did this show up on the other side?
My hacking continues. I managed to create a zero-length media object at demo.rss.chat/media/23 (this is what happens when you forget the @ in the curl command). I suspect that eventually, endpoints for /deletemedia and /updatemedia will be needed.
new rss.chat backend
Over the weekend, I sat down with my old buddy Claude and made a new backend for rss.chat written with Go.
The big differences are that it splits the database into more task relevant pieces, and ports it to sqlite rather than mysql. (its just a file!).
With this new foundation I'm able to do some hacking on pieces that I'm interested in, like websockets (I'm super impressed with Bluesky's ATProtocol "Jetstream" service), and getting a native phone interface up and running.
The code is available at https://github.com/roberte3/rss.chat.go.
Surprisingly, posting from my smartphone interrupted the song I was listening to on Qobuz (the new Rough and Twisted at the time). Oh well—I like silence too.
Examining my prior post (the one I'm replying to, id=343), I see that the markdowntext element is not my original markdown, but has been converted to HTML.
Wonderful. Got this working on rss.chat. Posts and comments from this post on my site.
From my vim to your feed
If you can read this, my bash scripts are functional. Not pretty, but functional.
The rss.chat API docs have improved substantially, saving me from going down some deep rabbit holes.
I’ve updated my feedland account with feeds about rss
Scour
Lemmy
Reddit
Hacker news
Not sure if this is the most effective way, but I have a scheduled GitHub action that will poll the rss feed for changes, if it finds replies, it writes it to a file (one per slug/post on my site) into `_data` which makes it available to liquid templating `site.data.replies` and then in my templates I check for matches to the slug and then foreach and render the html into the file at build.
The python does the heavy lifting of sanitising the html parsing the rss etc
great to see you here matthias. wow.
can't wait to see what you did. ;-)
rss.chat for WordPress: https://github.com/pfefferle/wordpress-rss-chat
Yet another test. Having some trouble with markdown, but it is probably my fault. I did not provide this time, only .
let’s chat!
Yet another test. Having some trouble with markdown, but it is probably my fault. I did not provide description this time, only markdowntext.
Another test. I *did notes.md notes.md~ notes.md.backup provide description this time, only markdowntext.
We updated the docs this morning — hopefully it's clearer now how this works. Thanks for your help.
https://github.com/scripting/rss.chat/blob/main/server/docs/api.md
Another test : reply 3 to chatouk
Another test : reply 2 to chatouk
it would be interesting to hook up the output of rss.chat to the input of Jekyll using templates or themes or whatever they call them in the Jekyll.