Dave Winer again calls for “a twitter-like system built with feeds, with all their limits”. In May 2023, I created My Status Tool (Github repo) using Node.js that provides the basic posting and reading functionality within Twitter, but using RSS and rssCloud as the enabling technologies. Colin Walker also created a PHP implementation (Github repo), and our two versions were able to interop. Dave also called for this back in December 2023 (my response), but from what I heard, Dave had some other ideas besides working with MyStatusTool. I don’t think that FeedLand is the system he was talking about, and I don’t think that Blogroll Social is the system either. Anyone interested in working on this?
Blogging
There are 104 posts filed in Blogging (this is page 2 of 11).
Creating the future of journalism (post and podcast)
I just finished listening to the two podcasts by Dave Winer on what we need from Biden, and his conversation with Jeff Jarvis on how to work around the brokenness of the mainstream media in the 2024 election. This was an excellent conversation. I have several comments on the Jeff Jarvis podcast, and will cover them in this post, and there is a separate podcast at the end of this post.
Jeff Jarvis brought up two points based on prior writing/conversations with Dave Winer. One was “the power of the link”, and the other was that people should uses their own personal spaces to respond to someone else’s post or story. I agree that if you are going to talk about someone, or something that they wrote, you should link to it. However, recently Dave Winer wrote a post critical about the people and work of the Podcasting 2.0 effort (how they reimplemented rssCloud), but he did not link to the thing he was complaining about (I had to track it down). How does this square with what was discussed in this podcast? I think it is inconsistent at a minimum, and perhaps bordering on hypocrisy.
Another topic was people commenting on social media posts, and how a lot of these comments were “spam”, in that people were not responding to what was posted, but were posting to try to take advantage of the “flow” of the original poster (in this case, I am assuming it was Dave Winer – it could also happen to Jeff Jarvis, but it was Dave Winer who brought it up). This is a tricky topic. Both Dave Winer and Jeff Jarvis said they want to encourage conversation (well, maybe it was Jeff more than Dave). However, if you want to have conversation, you have to give people the chance to say something. If the response to comments is deleting comments, or blocking people because they disagree or are critical, this discourages people from commenting. If I write a post commenting on another post (either compliments or criticism), how should I inform the person or site I am are writing about? Both Dave Winer and Jeff Jarvis said people should be “respectful”. That sounds good, until the conversation gets blocked. I do not have any solutions to offer here, but if someone wants to have a conversation, it has to be two-way/bidirectional. In the case of social media apps, part of the design of the apps, in my opinion, is to encourage conversation. Blocking people and deleting comments in a thread do not give the impression that someone wants to have a conversation.
The next topic I would like to address is providing an alternative to the mainstream media. Dave Winer talked at some point about individuals creating stories (covering events (like reporters, I suppose)) and creating/editing a flow of stories (again I assume this is mainstream media stories, which is a lot of what get commented about on blogs). I will address the “flow of stories” idea first. During the 2020 George Floyd protests, I started a site to curate the mainstream media and social media coverage of the protests in Portland, Oregon. The site was called Portland Protest News, and I updated it daily for a month and a half before I had to stop due to an illness. I set up news flows from mainstream media (primarily using RSS feeds), reviewed those feeds on a daily basis, selected stories to post, created a post with links to those stories, and also created a newsletter with the same content. At best, I was able to do this in an hour. Most of the time, it was 1.5 hours, and sometimes two hours. It was difficult to do this and work a regular 8 hour day. To me, the curated flow that Dave Winer talked about in the podcast with Jeff Jarvis would take at least this much time. Someone would have to put in that time to create a dynamic site with daily posts.
Next, I would like to discuss the topic of people covering events. I thought the idea of protesting the New York Times was interesting, and the idea of others news organizations covering that protest might occur. However, in a recent post of mine commenting on an essay by Anne Applebaum on protests in Poland, Applebaum stated that protests, if not carefully targeted, achieve little. I do not think there would be a clear enough goal to make protesting the New York Times effective. I think that the idea of independent writers/bloggers attending events and publishing accounts of this events is worthwhile, but I think there are several issues as well. Finding out about events takes work, attending events takes time, and writing about the events takes time and effort. Who will do these things? Who will coordinate this work? How will the posts/stories be distributed so that others can find out about them? The story “The Little Red Hen” comes to my mind, where one animal does all the work to produce a loaf of bread. Where are the “little red hens” to do this work?
There are some independent news organizations covering state legislatures (States Newsroom) and voting issues (Votebeat). There are small news startups trying to cover local news (Salem Reporter in Salem, Oregon as an example). There is even a online newspaper in Washington state (the Sammamish Independent) that is produced by volunteers. These are all current examples of independent coverage. Some of them have some funding, but many are dependent on subscriptions or donations. Doc Searls, in his work at the Ostrom Workshop at Indiana University, has written a series of stories about “The News Commons“, and experiments in the Bloomington Indiana area. So, I point to these examples of “little red hens”, each with a focus, but providing inspiration and food for thought to others.
I welcomed this podcast, as it shared many ideas and food for thought. I hope my analysis has done the same, and I welcome any and all feedback. No one will be blocked or deleted, I assure you!
I recently posted a quote from Hannah Arendt: “We are free to change the world and start something new in it” . I would like to point to a recent post by Ken Smith about how to solve the problem of Donald Trump. He organized his post as a series of problems to be addressed. I think the structure of this post could be implemented as a website in a fairly straightforward manner. I will try to create something in the next week that could serve as a model. Maybe I can even get Ken Smith or someone to collaborate with me on this project. Any assistance would be welcomed!
On the topic of link blogs
There has been some discussion somewhere this month on the Web (although I cannot find it) of a new list or lists of link blogs. Brad Enslen noted earlier this month that he sees an increase of link blogs in his browsing. The discussion of linkblogging has been going on for a long time (see this Manton Reece post form 2016 as an example). I have a Links category on my website (with its own feed), so someone could follow just the links part of my website. It is a simple thing to do in WordPress, as well as most other weblog tools. I also have another blogging tool (MyStatusTool) which is well suited to use as a link blog and has its own feed. Of course, there are many ways to publish a link blog, but why not get started with the tools you have at hand? As I mentioned recently, we have great tools available – let’s create some great things! Start blogging those links!
Are we creating great things?
In 2017, I wrote a post with the title “We have great tools to create – are we creating great things?”. It was in reference to a Doc Searls liveblog post on a podcasting conference at Columbia University. My observation was that there are a lot of low-quality podcasts, but as time goes on, better ones will appear.
Since then, the availability and quality of tools has increased (blogging, podcasting, video, etc.). Ken Smith recently commented on the tools aspect by linking to a video by actor Jason Alexander on acting/screenwriting – that the tools needed for creating videos are available to everyone (Alexander finishes by saying “You can create a movie on your phone…”). Ken mentions that the same is true for active citizenship as well. I will follow up on this in a minute.
In a recent post, I listed the tools I needed to create a podcast in the car, and have other posts on how to add podcast cover art to a WordPress-hosted podcast, and simple instructions for using WordPress as a podcast hosting tool. The tools available for blogging are always increasing, as is the same for video production. So, since we have the tools part covered, are there some great things out there? Are there more great things that need to be created?
Two excellent instances of group efforts in a topic are the Election Law Blog and the Americans of Conscience Checklist. The first is a group blog following current events in election law and the politics of election law. The second is a group creating lists of bite-sized actions that people can take to promote progressive causes. Both sites use WordPress as their main platform.
Jeffrey Issac’s Democracy in Dark Times blog does an excellent job of addressing issues relating to Donald Trump. Recently, he has been covering the student protests at his university, Indiana University, and calling out bad behavior by the university administration and Indiana elected officials.
I have made efforts to document events such as the protests in Portland, Oregon in 2020, the Georgia Trump election interference trial, a podcast about the “tools for thought” space, a site documenting news on the “return to office” efforts in the American workforce, and a “link zettlekasten” capturing news on elections.
Dave Winer has called for “determination” in using tools and resources to pick up the slack for lack of coverage by the New York Times and other outlets. Ken Smith has called to start “the work of a generation” (I am assuming this is work to try to ensure that our democratic system continues). I recorded a podcast addressing these calls (punchline: take some action, do something, don’t just call for resistance/protest). I think that this quote from a more recent post of mine is a good way to wrap this up:
… I recently listened to a Radio Open Source podcast episode focusing on the life of Hannah Arendt, who lived under authoritarian and totalitarian regimes in the 20th century. One line of her writing stood out to me: “We are free to change the world and start something new in it.”. I think that every podcast is a chance to change the world, and anyone is free to create one and send it out into the world.
https://andysylvester.com/2024/04/19/the-joy-of-podcasting/
As Ken Smith quoted Pete Buttigieg:
“Don’t wait. Start now.“
http://oldschool.scripting.com/ksmith3123@gmail.com/2024/04/20/123857.html#a124210
Chris McLeod: Blogging is where it’s at, again – reviews blogging services (including Micro.blog) and OPML usage in the wild
Bix Frankonis: ActivityPub Is To The IndieWeb As A.I. Is To Silicon Valley? – Bix Frankonis shares his thoughts about the use of ActivityPub and how it may have unintended effects in propagation of comments on social media services to blogs.
James’s Coffee Blog: The Web Is Yours – An overview of tools and techniques for getting started with a personal website – it’s a good read!
Who should be working together on Textcasting?
In recent posts, Dave Winer has been bringing up the “working together” mantra in regards to the Textcasting concept. This has been a difficult concept for me to grasp – working together with who? Today, Dave sheds a little more light on this:
When I say textcasting is “applying the philosophy of podcasting to text” — what I mean in practical terms is that my flow of ideas is available “where ever you get your text.” Choice in subscribing has to be that fluid, commonsense, and choice is something people feel entitled to, as they do with podcasts. I’ve been told people would never understand the philosophy of podcasting, but they do, they understand they’re entitled to choice in how to listen and thus producers are free to choose where to publish. Somehow text, which is so much easier to transmit than audio, is far less flexible. That’s a mistake I want to undo, but I can’t do it alone. I need to work with other people who have writing and reading tools, and people who have something to say and want all the features of writing to be at their disposal, and for it to be easy, inexpensive but not free of charge, and not owned by the titans of tech. (bold/italics emphasis by Andy Sylvester)
from http://scripting.com/2023/12/30.html#a160414
I think the key part of the highlighted text is “other people who have writing and reading tools” – that is, people who are involved in developing writing and reading tools, or the primary developers of reading and writing tools. Dave Winer did press Bluesky to add RSS feeds as a native feature in the Bluesky client, and this occurred on December 22. He has also developed some software to be able to post to WordPress, Mastodon, and Bluesky via a REST call, so I guess these three platforms are not the ones Dave wants to work with?
Two other concepts in this paragraph also deserve some review:
- my flow of ideas is available “where ever you get your text.”
- Choice in subscribing has to be that fluid, commonsense, and choice is something people feel entitled to, as they do with podcasts.
To me, this moves beyond the “feature list” as defined at Textcasting.org. The first bullet implies that a writer should be able to publish their writing such that it can be seen in any tool. Apps that create RSS feeds of content could be read in any RSS reader, so if all writing apps created RSS feeds of the output of their apps, a user could use a RSS reader app to read that content. However, I don’t think that is the direction that the first bullet is heading. My feeling is that the real message of this bullet is “my flow of ideas should be able to be posted on any social media network without me having to re-enter my ideas into some other editor or tool”. THAT would definitely require app developers to work together to make that happen. And why would they do that? I have been thinking about the struggle to get Twitter/X/Facebook/Threads to create RSS feeds. My simplistic thought is that if users could get the content using RSS feeds without going through the platform app/interface, the users would not be exposed to the ads that that the platform has, which is the primary means of support for those applications. From that standpoint, it does not make business sense for those applications to give the content placed in their apps away in that manner.
This brings me to the second bullet mentioned above. To me, this could be a description of the “pain” experienced by Mastodon users when trying to follow another Mastodon user on a Mastodon instance different from the one that hosts their accounts. Similarly, it could also describe the pain of trying to subscribe to a RSS feed. As I mentioned earlier, THAT would definitely require app developers to work together to make that (cross-app subscription and forwarding of content) happen. And why would they do that? I don’t know. As an aside, for many podcasting apps, their feed search feature is good enough to find a podcast feed from search terms, so I don’t think that is the use case being highlighted by the second bullet.
To return to the title of this post, I think the people that need to work together on textcasting are primarily developers. As the developers have applications, they should then evangelize their work to potential users. To me, this seems to be the approach that the Textcasting “movement” needs to follow.
What is “interop” for social media apps?
I have been busy lately, but something Dave Winer wrote recently about interop bothers me, and now I have a little time to discuss it. Dave said this on December 13th:
Andrew Hickey is one of my favorite bloggers, and it’s somewhat weird because..
- He blogs on Bluesky but it works because..
- John Spurlock added RSS 2.0 feeds for Bluesky, built on their API, I am able to subscribe Hickey’s observations in FeedLand, because..
- Of course FeedLand understands RSS.
And it all happened without getting complicated. No federation needed. Just plain old RSS.
from https://feedland.blog/2023/12/13/the-power-of-open-formats/
So – let’s break this down. Someone (in this case, Andrew Hickey) is using the social media app/service, Bluesky. Another person (John Spurlock) has created a web service that uses the Bluesky API to allow a user of the web service firesky.tv to create on demand an RSS feed of posts for a Bluesky user. This RSS feed can then be read by any feed reader supporting RSS. In the post, Dave Winer links to the feed for Andrew Hickey’s account as presented by his feed management system/application, FeedLand. The display of the items in the feed are attractive and easy to read. However, since the feed is public, anyone could create a similar display (like this one). To me, this demonstrates the interoperability of RSS – anyone can take an RSS feed, consume it however they wish, and present the feed however they wish (either privately (like someone using Feedly or Inoreader) or publically (like the FeedLand representation or my representation)). I agree that no “federation” was needed, but that service from John Spurlock was needed, otherwise there would have been no RSS feed for FeedLand or my app to read.
Now, this example does not, in my opinion, demostrate any “interop” with the Bluesky application or service. John Spurlock’s application is using data from Bluesky using its API, but the interaction is one way – Bluesky to firesky.tv. That, in and of itself, is fine. There are many applications in the world that provide an API to allow other applications to get data from the application (and presumably to send data to the application). There is a list of such applications for Bluesky (https://atproto.com/community/projects), so no one is stopping innovation in this area. My impression is that Bluesky is not charging for use of its API (unlike X/Twitter), so this also should foster innovation in applications using data from Bluesky and client development for Bluesky.
Now, returning to the Dave Winer post linked at the top of this article, he is putting out the call to add feed support to social media systems (i.e., outbound feeds, publishing the posts that users make using Bluesky as feeds, separate from what someone would see using a Bluesky client, such that someone could keep up with posts on Bluesky without using the native app or any other app besides a feed reader):
I am lobbying everyone I know to add great feed support to social media systems, so we can get out of the mode of dominant platforms before Threads becomes the dominant platform.
from https://feedland.blog/2023/12/13/the-power-of-open-formats/
In pushing for this, if all social media services produced feeds, then this could be used to support moving content between services, and for other uses. Mastodon natively supports outbound RSS feeds, but Bluesky does not (John Spurlock’s Firesky.tv service appears to be the main way to read RSS feeds of Bluesky posts).
So, what about peering? Currently, there is no peering of data between Bluesky and Mastodon or any other social media service. It is, of course, possible to send content from Bluesky to Mastodon or the other way around, or any other service, as long is there is a protocol or API that supports that sharing of content. Again, those protocols do exist (AT Protocol, Activity Pub, and Mastodon API), so content could be moved around (if someone wanted to invest in doing that work).
So, what about federation? This is where different servers and/or services could communicate with each other. The Mastodon documentation has a summary:
“Unlike a traditional website, Mastodon websites can interoperate, letting their users communicate with each other; just like you can send an email from your Gmail account to someone from Outlook, Fastmail, Protonmail, or any other email provider, as long as you know their email address, you can mention or message anyone on any website using their address.”
from https://docs.joinmastodon.org/#federation
This is part of the nirvana promised by the concept of federation – you can post anywhere, mention a user, and have that user be notified. The mechanics of that, however, can be tricky, and depends on multiple servers/apps using the same protocol.
Even though there seems to be a lot of heat/activity in trying to make federation work, what if that was not the key feature that users want? Dave Winer comments here:
“Imho, what’s valued is the ability to publish something quickly, and without much fuss, and follow others, again easily without having to have a deep understanding of how these things are architected.”
from http://scripting.com/2023/12/13.html#a135218
In my opinion, this is the use case that could benefit from universal RSS support across social media applications. If that was in place, the ability to flow content via RSS between social media apps would be straightforward, and perhaps not require any effort on the part of the social media apps to federate. The world will have to wait and see….