I was able to confirm this morning that rssCloud support in FeedLand worked for my WordPress.com test site – hurray! Many thanks to Andrew Shell and Dave Winer for working things out, along with support from Joseph Scott at Automattic. Joseph Scott released a new version of the RSS Cloud plugin today for WordPress.org sites, I did an initial test, but FeedLand did not get a rssCloud update from my test site. I got some debug ideas from Joseph Scott, working on those now.

Update: I figured out that Gary Teter’s post I referenced on December 10 was not deleted from the FeedLand user view, so looks like it was my post that brought in the comment guidelines. I apologize for the error.

An unfortunate exercise of editorial discretion by Dave Winer?

Update: I figured out that Gary Teter’s post I referenced on December 10 was not deleted from the FeedLand user view, so looks like it was my post that brought in the comment guidelines. I apologize for the error.

I have been following the development of FeedLand, a new feed reader application from Dave Winer. I have used many of the tools that Dave has developed over the years. One cost of using his tools is figuring out how to navigate a web of sometimes unclear expectations on support forums/repos. For the Drummer application, it was made clear that problems related to Drummer were acceptable, but that was about all that was allowed.

Recently, Dave Winer added two new features to FeedLand – a way for a user to make short posts and create a RSS feed, and a collected view/river of user posts. I took a look at the feature yesterday, and decided to make a short post comparing this experience in FeedLand to an app I use for reading posts by Drummer users who blog using the Old School blogging tool. Here is the text of the post:

In response to Ken Smith’s comment on the Read user feeds feature in FeedLand, this is the sense of community that the Old School Drummers river has as well. However, with the ability to post new items as you read them, thee feedback loop tightens…which is a good thing…which is like Twitter/Mastodon…hmmmm…

Post on FeedLand feed

A little later, I decided to check to see if anyone had responded. What I found was my post in the user post view was deleted (the post was still present in my RSS feed), and this post was now at the top of the view:

I should’ve done this from the start, but I didn’t want to start off on a negative note. I’ve been hosting discussion groups on the net since the beginning and these days spam and abuse start pretty soon, and there’s no negotiating with it, you need clear rules and no tolerance.

So you have to have a policy ready, and I do — they’re called the Comment Guidelines, and they apply here. They’re easy to follow for most people, and we need them to protect against spam and abuse.

I’ll include a customized version in the Docs menu, soon. 😉

Wow (I thought to myself)! What was wrong with this? I decided to sleep on it and approach it fresh in the morning. I read through the “Comment Guidelines”, I think my item fell in the “No Spam” category (It’s not a place for you to promote your products, services, blog, initiatives, political causes. Don’t post spam. ) and the “No blog posts” category (2 sentences could be a blog post, I guess). Later this morning, I saw a post by Gary Teter that it appeared he had also fallen prey to deletion:

Apparently FeedLand’s “my feed” isn’t actually my feed, and is intended just for making comments about FeedLand. So I guess I will have to come up with some other way to make quick posts to the blog part from my phone. Disappointed.

As a proud union member who does not cross picket lines, turning off the New York Times feeds at the root level of FeedLand feels like the Musk approach. Unsubscribing from them on your own feed seems better to me. If there’s a social aspect to using FeedLand, it is users following each other’s curation judgments. Not the owner of the platform using the platform itself to express personal judgments.

It appears that the second paragraph of this quote was the offending post.

So – where was the guidance of what to post and what not to post? I looked at the FeedLand Change Notes blog, and found the post on creating a user RSS feed and the first post on the User Feed View feature. There was where I found the key phrase:

The rules of decorum apply here. There will be ways to block people, that’s inevitable. Feel free to discuss the product. Do not get personal, do not give anyone orders. Remember we’re here to have fun and make something new!

from FeedLand Change notes blog

So – read between the lines – this “user feed view” is a Dave Winer site, and is governed by the comment guidelines for his regular blog. I think Gary Teter said it best:

Apparently FeedLand’s “my feed” isn’t actually my feed, and is intended just for making comments about FeedLand. …Disappointed.

Well, here we go again – Dave Winer deleted a post I made on FeedLand comparing the User feed view and the Old School Drummers river, then posted comment guidelines. Really? Was that necessary? I will have more to say on this later today.

Lazyweb request – does anyone know of other feed readers besides FeedLand and River5 that support the rssCloud protocol? I am trying to collect data regarding the WordPress rssCloud implementation. Thanks.

Demo of rssCloud protocol and reallySimple NPM module 

In this era of moving away from Twitter, I have been reviewing the rssCloud protocol and think about its potential. I had not done anything about it, but saw this Twitter thread and really liked this comment by Preslav Rachev regarding building on RSS: “And best of all, everyone is free to build their own apps and tooling on top of it without restrictions, or stepping onto each other’s toes.”. I then decided to start playing around….

I read through the walkthrough document on the rssCloud site and decided that the simplest test would be to create some RSS feeds that have rssCloud elements, register them with a rssCloud server, then get the server to contact a server when the feeds updated, then display some information from the feeds. I started with this script from Dave Winer, updated it to provide web output, then ran the script twice to register two different feeds. I then made a video of running the script, posting to feeds using Drummer and FeedLand, then displaying the title or description of the most recent item in the feed, along with the feed name. The video is shown below. Source code and more instructions are available on Github. Let me know what you think!