A few days ago, I wrote about discovering that the feed of the “Preserve This Podcast” podcast had a problem (episode 1 link was no longer good). To correct this, I thought I would reach out to people who were listed on the About page to see if they could help. None of them responded, so I next went to the Preserve This Podcast Github repo, which houses the source data for the podcast website, and figured out what file needed to be updated to correct the error when the feed was rebuilt (the site was created using Jekyll). I then created an Github issue and a pull request, and within two days, someone merged in my change and re-deployed the site! After two more days, the site cache was updated with the new feed, and I was able to load episode 1 successfully from two separate podcast apps. Victory!
Micro.Blog
There are 319 posts filed in Micro.Blog (this is page 4 of 32).
Does Dave Winer really want a RSS-based social web?
I am sorry to have to continue this thread, but there are more developments to assess. In a followup, Dave Winer shares he does not get much in the way of views of his content on Twitter. He then tells Ben Werdmuller (and the rest of us) that “we have to create our own social web”.
Well, there’s the rub, isn’t it! If someone wants to have a social web based on RSS, they are going to have to create it themselves, instead of trying to “boil the ocean” and get every other social network software platform to add features to use RSS as the transport mechanism for social network applications. Then, they are going to have to convince other people to use it instead of existing social network software.
From the Mastodon About page, Eugen Rochko created Mastodon in 2016 because he was “dissatisfied with the state and direction of Twitter”. That was 9 years ago! Mastodon as an application has taken a long time to reach the position it holds today. rssCloud has been supported in Dave Winer’s blogging tools since 2001, and rssCloud support was added to WordPress in 2009 (see reference here), but there has been almost no uptake of rssCloud as a basis for blogging or social network tools. Perhaps part of the reason why is how Dave Winer responds to negative feedback on his tools in a negative way (examples: Feedland and Drummer).
I have described what a social network should have, and that definition covers all current social networking applications. Dave Winer gave his own description of a RSS-based Twitter app in January 2025, and it matches up pretty well with the app I developed, My Status Tool (demo version, repo for code). I also created a portal site for RSS-based apps for social networking (The Feed Network), so there is a place for people to get started (but I do not see it as my mission to try to evangelize this area). Dave has talked about what his new vision would be using WordLand (September 2025), but this “new vision” is nowhere to be seen. Show us the beef!
Do users want a “Really Simple” social web?
I have refrained from commenting on updates from Dave Winer regarding Inbound RSS, two-way RSS, social web based on RSS…fill in the blank RSS…, since he did not do a “reveal” on any of the features he said he was going to demo at WordCamp Canada 2025. However, this weekend, he posted another mini-manifesto on RSS-based social web stuff, which deserves a review.
He references three posts by notable writers who have written posts on RSS in the past year. Of the posts, only one hints at more “social web” possibilities for RSS. The overwhelming majority of the content of the posts concerns the classic reasons for using RSS (control the content you read, control the way you read it, filter out shit). So – my first objection to this manifesto is that these prominent users are not sending out calls to action demanding “inbound RSS” or “using RSS as a social network”. The second objection I have is the demand that other people’s software should start supporting two-way RSS (Davespeak for “inbound RSS” and “outbound RSS”). This is nothing new from Dave Winer, but none of these three references say anything at all about this.
I have addressed this second objection before, stating “What is in it for the “other people’s software developers to add inbound and outbound RSS support”? My answer is – nothing – no users are demanding this – no users are clamoring for a RSS-based “social network” that can communicate as a peer with other social network software.
Now, can there be a RSS-based social network that does not peer directly with other social network software (Twitter/Mastodon/BlueSky)? Yes! I created a site to collect the tools that support this – The Feed Network. Many of the tools I list were created by Dave Winer – see a pattern here?
In my opinion, the only way that inbound RSS support will be added to other tools will be by developers other than the main developers. Dave Winer actually did this for WordPress (although I have not looked it, so I cannot confirm if it works or not). I think someone besides Mastodon developers will have to do that development, not sure about Bluesky…but, to re-iterate at the risk of being repetitious, the only person in the world that is making a stink about inbound RSS is…..Dave Winer. Not much user demand there, methinks.
Introducing a “hand-rolled” podcast – “The Songs of Mavis and Marvin Smiley and the Manhattan Valley Boys”
At the end of 2024, I wrote a post about creating a podcast feed manually (“by hand” or “hand-rolled”) as opposed to using the feed created by a blogging tool (such as WordPress). My example was a short feed of two audio essays by Ken Smith, a blogger friend of mine. Shortly after that, I wrote about Dave Winer’s idea of subscription lists for podcasts, and referenced my manual podcast feed. Dave’s idea was focused on being able to share a list of podcasts that could be imported in a podcast client, and that could be updated as the list was updated. For this idea to be implemented, someone would have to add a feature to a podcast client. I discussed creating standalone podcast feeds of episodes from other podcasts as a bridge. Users have the ability to subscribe to individual feeds, and a creator could update a feed with new episodes, publish the updated feed, and it would be available through existing podcast clients without waiting for some developer to “go first” with the subscription list idea.
Since then, I thought about curating audio from a public radio show (A Prairie Home Companion) within a podcast feed. There is a central site with an archive of many of the episodes, and there are a variety of interesting parts of the show that repeat across the episodes. One fun aspect of this show are the “commercials” from regular “sponsors” (like “Bertha’s Kitty Boutique” and “Powdermilk Biscuits”). I decided it would a good test of this idea to find all of the available instances of a particular commerical and create a podcast feed of those audio excerpts.
The one I chose was appearances on the show by Robin and Linda Williams, a husband/wife folk/bluegrass duo, and their band. They appeared as “Mavis and Marvin Smiley and the Manhattan Valley Boys”, recording for Do-Tell Records. One of my brothers helped with the research, and together we compiled a list of 17 excerpts. I created a website (MavisAndMarvinSongs.com) to provide a set of audio players for each excerpt, and created a podcast feed so that users could add it to their podcast client and hear the wonderful music for themselves. Enjoy!
“Preserve This Podcast” podcast lost an episode
Recently, I wanted to re-listen to the episodes from the Preserve This Podcast podcast (a podcast that discusses strategies for saving artifacts used in creating podcasts). I had written about this podcast when it came out in 2019, and poked at the creators for depending on the Internet Archive to publish the site instead of paying for hosting themselves. After all, they had a GRANT to cover the production costs! Surely they could have budgeted for 5-10 years of hosting. I went to the site, got the feed URL, added to my podcast app, then started listening. When I got to the second podcast (Episode 1), my podcast app displayed an error message that it could not download the file. However, the app was able to download the remaining episodes. I decided to open up the feed in a text editor to see if there was any problem. I found the URL for the episode and pasted it into a browser tab. To my surprise, the browser said there was nothing at that URL in the Internet Archive. I then checked the URLs for several other episodes, and they showed the expected files. After some searching at the Internet Archive, I found this collector page for Episode 1, which led to this URL for Episode 1, which did not match the URL in the feed. UGH!
It is quite ironic that a podcast about preserving podcasts has a problem with its own feed! I will try to contact the team from their About page, but if anyone knows how to get in touch with one of the producers, I would appreciate it!
The need for curation and the cost of curation
Over the years, I have performed many “acts of curation”. Most of this has been simple collection of links, but several instances (Portland Protest News, Kamala Campaign Timeline) resulted in creation of websites to document a particular topic. These two sites in particular were collecting of daily links to document protests in Portland, Oregon, and the campaign of Kamala Harris for US President.
For curation of news events, it is important to keep up with content collection on a daily basis, as almost all news sites provide little to no support for tracking of stories, and searching usually turns up items in the last 2-3 weeks. For more stable topics, adding content as it is discovered is sufficient (see my Links Zettelkasten as an example).
Beyond the collection of links/information, the other primary problem is the organization of links/information. Curation, as a practice, is an attempt to organize information. My zettelkasten used individual topics in alphabetical order as headers, with links underneath. Other examples of collections include Indieseek.xyz from Brad Enslen, a curated directory. Karl Voit has a series of posts/presentations on personal information management (PIM). Chris Aldrich (through the use of tags in WordPress) has been performing some significant research on zettelkasten and the zettelkasten practices of Niklas Luhmann. All collections of this kind require effort, and most of them are for the benefit of the creator. Still, once these collections are available, they can be discovered and used by others.
Update on the Portland Protest News site
I got behind on posting when I was on a long business trip, but kept collecting links, and now Portland Protest News is now current again. The media coverage of protests at the ICE building in Portland has slacked off (last protest on local news media was for Veterans Day, over two weeks ago). It is possible that protests are on-going, but not getting coverage, or that protests have slacked off (this occurred in 2020 when the weather change to the regular cold/rainy fall started). The current state of the court review is that a local district judge banned National Guard deployment in Portland, but this is now under review with the 9th Circuit Court of Appeals.
ICE has definitely increased its activity within the state of Oregon. The media focus has shifted to mass arrests by ICE, arrests of US citizens, cities passing “state of emergency” proclamations, and federal contractor moves indicating ICE interest in creating a detention center in Newport, Oregon. Portland Protest News will continue to cover the activities of ICE, and further court activity.
Portland Protest News has been updated with all news from this week – still no National Guard deployed in Portland! Check it out!
Portland Protest News has the latest from this weekend’s No Kings protests in Oregon and continued protests at the Portland ICE facility – check it out!
I am going to a No Kings protest tomorrow (see locations here), and printed one of the two signs from this Kieran Healy post – print one for yourself!