rssCloud

There are 26 posts filed in rssCloud (this is page 1 of 3).

Thoughts on the “Winer WordPress Tease”

Dave Winer has been promoting his editor for WordPress sites, called WordLand, leading up to his keynote speech at WordCamp Canada in October 2025, as well as hinting about other WordPress-related projects. Recently, he asked readers to “Think Different About WordPress“, where he talks about how WordPress supports editing features that Mastodon and Bluesky do not support (linking, no character limits, and other features). WordPress also has “excellent support” for RSS and rssCloud, and has a “deep and powerful API“.

Dave Winer goes on to say that he is providing three things to bootstrap a development community around WordPress: (1) Apps (I assume this refers to WordLand), (2) a storage service (I assume this refers to his wpIdentity NPM package, which he uses for identity for his FeedLand feed reader, and also to provide storage for user writing (although it appears to use the MySQL database associated with a WordPress install)), and (3) content (to me, this is RSS from other sites, implying some feed reader app or link to a feed reader app (like FeedLand)).

Now, how does a development community arise from this? Well, I guess that if people want to use an API to interact with WordPress (create posts, manipulate data in the WordPress database), they can do that, and maybe wpIdentity makes it easier to create Node.js apps that can interact with WordPress (like WordLand). As Dave Winer has mentioned before, though, the WordPress API has been around for a long time, but does not seem to have gotten much use. I am not sure if providing an easier “front end” to an API will increase use of that API. The WordLand app up to this point has been “the example app”, but has been provided as a service (no source code), so it is more of a “working example” for developers, not an app that some one can build on. Finally, Dave Winer has been hinting about an “RSS timeline viewer“, which is perhaps where FeedLand comes in. Again, without the full picture, it is hard to see how these three things are going to spark a growth in WordPress application development.

Finally, Dave Winer posted a podcast on “the last chance for the open web“, in which he talks about WordLand as “really easy way to write for the open web that does not otherwise exist today”, among other topics. I do not see this as the “last chance” for anything. I have written before on the economics of software development and on innovation in RSS and podcasting. The open web is still there, still providing a platform for innovative work. Nobody stopped me from creating MyStatusTool as a Twitter replacement based on rssCloud, and nobody stopped me from collecting rssCloud-based tools at The Feed Network. I know that Dave Winer would like his writing tools to be able to push their content to all social media platforms. Maybe that is the “promised land” that WordPress might provide via the ActivityPub plugin and an AT Protocol plugin (not yet developed). We will have to wait and see…

A question about rssCloud on WordPress.com

I have been trying to troubleshoot a problem with subscribing to RSS feeds from WordPress.com sites on my rssCloud blog tool MyStatusTool. I decided to use a rssCloud test app from Andrew Shell, and was able to set it up and run it successfully. I did a week-long test to see if I could detect posts from seven WP.Com sites, and it worked (see log file here). This weekend, I realized that the app did not re-subscribe to any of the feeds, but still remained active, receiving notifications from the subscribed blogs for over a week. This seems to be in conflict with the rssCloud walkthrough page, which states that a feed must be re-subscribed every 24 hr. Does anyone know anything about this?

Announcing – The Feed Network

In recent posts, I have been giving updates on my work to set up a feed-based social network using rssCloud as the notification protocol. The initial site to support this is now complete – The Feed Network at https://FeedNetwork.Social.

The site has a page on how to get started, a set of questions and answers, and a tool catalog listing the tools that support rssCloud. This is an effort to show that other technologies exist that can create the foundation of a social network.

For more info, go to The Feed Network, or check out our introductory video, or follow our blog feed for updates!

Updates on building a feed-based social network

In a previous post, I mentioned that I was able to use a reference app to test rssCloud support for WordPress.com sites and WordPress.org sites. Since then, I have migrated some of the features in the reference app into a demo instance of MyStatusTool, the app I developed in 2022-2023 to provide a Twitter-like experience using rssCloud for notification. Here is a screenshot of the demo instance:

Currently, the app is subscribed to 11 WordPress.com sites, 1 WordPress.org site, and 6 non-WordPress sites. I did perform tests to confirm that all of these three types of rssCloud sites appeared within seconds on my demo instance. Woohoo! I will let this demo instance run for several days to check the re-subscribe function, but I think this is a good enough start to plan for a rollout of the feed-based social network.

Taking steps to build a feed-based social network

In a previous post, I mentioned that my vision of a feed-based social network included the use of rssCloud as the notification system within RSS feeds. Back in 2022, I did some investigation regarding support of the rssCloud protocol in WordPress.com and WordPress.org sites, and using FeedLand as the most prominent feed reader supporting the rssCloud protocol. It turned out that although WordPress.com sites had included support for rssCloud since 2009, and WordPress.org sites through the use of the RSS Cloud WordPress plugin, there was some misunderstanding about what a client needed to do to register with the WordPress rssCloud support. This Github gist goes into the details, but to summarize, the client trying to register with WordPress needs to be running on port 80 or 443 to be recognized. Both Feedland and the River5 feed reader (the two prominent feed readers supporting rssCloud notification) did not necessarily run on those ports, and as a result the “real-time” notification of rssCloud did not occur. Those feed readers were able to read the WordPress RSS feed and display updates, but not in real-time.

FeedLand was updated and now supports WordPress rssCloud registration. As part of that effort, Dave Winer created a rssCloud server demo project to use to check rssCloud server implementations. I decided to check this out with a WordPress.com site and a WordPress.org site using the RSS Cloud plugin. On my server, I am using the Caddy web server, and had some subdomains being hosted through Caddy. I updated the rssCloud demo code to use the port I am running on, and to use one of those subdomains with Caddy doing a reverse proxy so that the app would appear to be running on port 80. My test was successful! I was able to see the app register with both the WordPress.com and WordPress.org sites, and to see the app respond when the sites notified the app of a new post. Here is my copy of the main app and the stats file created by the app.

This is an important step in creating the feed-based social network I have in mind. WordPress is the largest generator of RSS feeds supporting rssCloud, so it is important to understand how the WordPress rssCloud implementation works to make sure that apps interacting in this social network can get real-time updates from WordPress sites.

What should a social network have?

I am cross-posting this from my WordLand blog.

The mention of a social network built around RSS has come up again. I added my off-the-cuff thoughts on this topic in this post, but I also wanted to review Dave Winer’s description on the rssCloud website:

There are three sides to the cloud:#

  • The authoring tool. I edit and update a feed. It contains a element that says how a subscriber should request to notification of updates.#
  • The cloud. It is notified of an update, and then in turn notifies all subscribers.#
  • The subscriber. A feed reader, aggregator, whatever — that subscribes to feeds that may or may not be part of a cloud. #

I think that these three elements are the minimum features for a social network to exist. By breaking this down into three parts, it is easier to see that multiple applications cane be created or assembled to create a social network. It does not have to be an “all-in-one” application (like Twitter, Mastodon, Bluesky, etc.). Users can use whatever tool they want to create their content, and they can use whatever tool they want to consume the content. Finally, both of those tools can interact with a “cloud server” which performs notification. 

So why has this idea/concept not gained traction? I think there are several reasons. Many authoring tools create feeds, but do not support notification. Many subscriber apps read feeds, but on more of a “polling” basis, and not because the app has been notified that a feed has updated. To me, these are places where innovation could start.

I have been waiting for “someone else” to do this work, but “no one” has stepped in to start, so I am going to try adding some “notification” features to some other blogging tools. I would be remiss if I did not point out that there is a RSS Cloud plugin for WordPress blogs, and WordPress.com supports rssCloud. In my experience, though, my self-hosted WordPress blog has not experienced “real-time” performance due to caching of the RSS feed by my host, Bluehost. I have tried many ways to turn this off, with no success.  Anyway, there is nothing “stopping” me from innovating here, so here goes!

Open letter to Dave Winer’s call to develop feed-based social media apps

On December 3, Dave Winer published a “call to develop” for a feed-based social media app (he mentioned Mastodon in his post, but could be any social media app out there in my opinion). Sounds great to me! I have a feed-based app using rssCloud for notification called MyStatusTool (link to Github repo and my install). It is implemented using Node.js, Express, and Embedded Javascript for templating. It inspired Colin Walker to develop a PHP implementation of the tool (Github repo, his install). We were able to use our tools to interop with each other (have a real-time conversation), and to follow other feeds using rssCloud for notification. I have tested my implementation with the rssCloud user feeds from FeedLand and WordPress.com in addition to Colin Walker’s MyStatusTool implementation, and verified the real-time performance (new posts showed up almost immediately).

Now, is MyStatusTool a fully-developed thing? Nope! It’s a bootstrap. It does use a number of Node packages developed by Dave Winer for feed generation and feed reading, and uses Andrew Shell’s rssCloud server for notification, so I think it falls into the “working together” category that Dave Winer wrote about in 2015: “When you have a choice, instead of re-inventing someone else’s work, use it.”

I am ready to work for interop with whatever Dave develops. I don’t have any illusion that MyStatusTool is the epiphany of feed-based social media tools, but I developed it to see if one could be developed, and it spawned another implementation, so I think that is pretty cool. Let’s get busy and see what happens!

Solved my problem with WordPress caching

For a long time, I have had problems with apparent caching of WordPress RSS feeds. In my recent work on WordPress support for rssCloud, I eventually was able to get a notification about a WordPress update from the RSS Cloud plugin, but the content of the feed did not update. I spent some time on this again this week, and decided to search for “wordpress caching issues bluehost” (since Bluehost is my hosting service). I found this post on ThemeSkills which described a feature within the Bluehost interface that controls caching on a site-by-site basis. After reading through the post, I was able to turn off caching on my test site for RSS Cloud. I then made a post on that site and saw the update within seconds on FeedLand and MyStatusTool, and saw the latest post display – at last!

Here are the steps:

  • Log into Bluehost account
  • Click on the My Sites link on the left navigation bar
  • Scroll to the site to review and click the Manage button
  • Click on the Performance tab
  • In the Cache Settings area of the page, slide the slider all the way to the left. If it is already there, move it to the right to the Blog area, then back all the way to the left
  • A pop-up will appear, click on the Disable Caching button

PS – Here is a Bluehost page on this topic as well