Is anyone else going to WordCamp this week?
I’ll be flying in Monday morning. Highs of 113°F in Phoenix! Uff da! I'll have "I ♥ RSS" stickers to hand out.
My initial tests show it works as expected!
Added a river to I ♥ RSS: https://iheartrss.com/river
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?
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.
It looks like the JavaScript-rendered page content is blocking right now, but I'm having Claude suggest some fixes. :-)
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.
Claude, I added rssCloud support to https://iheartrss.com/subscriptions.opml so feedland can update it realtime as new feeds get added. Right now new feeds are empty for a while because they aren’t in feedland yet.
Number one on the homepage 😳
Looks like my post was shared on hacker news! https://news.ycombinator.com/item?id=49136063
So far, I've tested FreshRSS, Feedbin, Feedly, and Inoreader.
FreshRSS is fast and handles all variants. Inoreader also seems to handle all variants, although yesterday it seemed to be delayed, but today it came back fast.
Feedly didn't seem to respond to anything, but it might just be slow/backlogged.
Feedbin seems to be a naive parser because it only worked with the atom:link elements, not the websub:link variant.
I tried testing micro.blog but so far it still says "Posts for this user are still being downloaded." for all variants.
I'm now using Dave's blogroll, styled for https://iheartrss.com/
Sounds good. I'll get a feed published to handle this. Maybe one that still uses atom:link and one with websub:link so we can track that difference as well.
https://websub-debug.geekity.com/
I'm about done for the day, so I'll hopefully start testing it with readers tomorrow. :-)
If anyone here maintains a feed reader that supports WebSub can you please weigh in on the following thread?
https://gist.github.com/andrewshell/55429f537cfc2a114471cf4c9dec8b8f
You read my mind :-)
Just added rssCloud support to https://iheartrss.com/subscriptions.opml
It uses source:cloud (which FeedLand supports) so we can see if it works.
I was inspired by Dave's "I Love RSS" post Tuesday and built a directory for people that love RSS. It's called https://iheartrss.com/ and leverages many of the goodies we're promoting like an OPML subscription list and a blogroll powered by feedland. :-)
Let me know if you have any questions or issues with the site. I'll try to keep on eye on the thread.
My favorite static site generator is 11ty which is now rebranded "Build Awesome" and is part of the Font Awesome suite of projects.
Here is the thread to discuss on GitHub: https://github.com/scripting/rss.chat/issues/13
When we're talking about the rules for interop with rss.chat, is there a specific name we're using? Like, would it be an "rss.chat" WordPress plugin?
I read the interaction here: https://demo.rss.chat/?id=57 and the part where you said "treat comments as blog posts with their own permalinks" made me wonder, because this is not a rule from Textcasting.
For instance, I could in the main feed add `` and link to a comments feed (like https://test.geekity.com/2026/07/16/hoopla-world/feed/), but those comments don't have permalinks, just an anchor tag to the main post. So this wouldn't be compatible?
Right now, I'm figuring out what might be the best way to implement rss.chat standards in WordPress without reinventing everything that comes with WordPress. As I've been going through the elements, I've been thinking, "How would a consumer use this?" and this was one of my questions.
So if I were a feed reader and I pulled in the feed from demo.rss.chat and I had an item with `<source:account service="demo.rss.chat">dave</source:account>` I'm trying to think through what I'd do with that.
The first thing that comes to mind would be linking to the user's profile page, but we don't have an html profile as far as I can tell. We do have the user's RSS feed, and it's in the `` element. The feed, interestingly enough, uses the user's homepage as the channel `` and not a URL where you'd see the user's posts.
So right now I have more questions than answers, but this is where my line of thinking is going.
I've been thinking about the source:account element. Having service as a string like "instagram" makes sense because it's a single instance. For "mastodon" it's okay because the domain of the service is in the username. But I'm wondering if this will become an issue as more small services get spun up.
Should service be a URL to the service homepage? Maybe the service is on a specific port or running from a folder on the server. I know there isn't anything in the spec that says it can't be a URL, but would it be useful, since this is being parsed by a feed reader?
If we want to keep it just a label for the service, should there be an optional url or href element linking to the service homepage?
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.
That’s fine. It’s all 100% opt in. :-)
Services that support WebSub have specific requirements. The link elements or the HTML headers are what they require. I think the best solution might be to use inline namespaces like we talked about and just put them at the bottom of the channel contents (after the items).
We still need the URL namespace with Atom in it, but at least it's not at the top of the feed. We might lose some parsers that are just looking for atom:link elements and not doing proper namespace resolution, but I think it's the best middle ground. Maybe ask the braintrust?
<link xmlns="http://www.w3.org/2005/Atom" rel="hub" href="https://rpc.rsscloud.io/websub"/>
<link xmlns="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="https://feed.example/rss"/>
You say:
> There isn't very much I'd have to do beyond adding two Atom elements to my feed, and an Atom namespace declaration in the top line of the file. So it's not an easy thing to do.
Did you mean to say "it's not an easy thing to do" or was that a typo? I'm hoping the changes were easy. :-)
If you see anything wrong, please submit an issue here: https://github.com/rsscloud/rsscloud-server/issues
Yay! rssCloud Server 4.0 is now live and running on my new server. This is a major upgrade/rewrite of most of the server. I'll write a full blog post tomorrow, but the killer feature is that the server now fully supports WebSub. That means anyone using rssCloud with my server can add an extra line to their RSS feed and automatically support WebSub without any other changes. An rssCloud ping will send notifications to any rssCloud (post or XML-RPC) or WebSub subscribers. https://rpc.rsscloud.io/docs/quick-start
There is also a new debug app for testing all the different flows. It can also be used to test other rssCloud and WebSub servers/hubs (like WordPress sites), although I'll probably need to record a video demo for it. https://debug.rsscloud.io/
I'm moving rpc.rsscloud.io to a new server this weekend. Shouldn't have any downtime. I have the new server proxying to the old server right now while DNS propagates. Tomorrow, I'll get the new server running, copy over the data, and perform a real-time switchover. When the new version is live, I'll announce a new feature I've been working on. 😊