A number of people have posted recently on the subject of POSSE (Dave Winer, Tantek Celik, The Verge, and Bix Fronkonis). POSSE is an acronym for Publish On (your own) Site, Syndicate Elsewhere. Dave Winer has also been talking about Textcasting, where he proposes that blogging/social media tools support a common set of features. Dave Winer also talks about “Two-Way RSS”, which I think means that a tool can generate RSS feeds and can use RSS feeds as an input to posts within the tool. I would like to explore these ideas further in the next few paragraphs.
Recently, I got the impression that a Textcasting use case is to allow a user to write in their tool/platform, and have that output be accepted on other platforms as “first-class posts”. What I mean by that is the post appears on the other platform to have been written by the user using the platform’s own tools. Now, a number of platforms don’t support all the features in the Textcasting spec, so even if the other platform accepts input from the user’s platform, it may not represent the text as it appeared in the original platform. In this instance, I might call that a “second-class post”. It may have all the text from the original user platform, but not the styling, or links, or an enclosure.
So, it seems to me that the target of Textcasting is to get Threads/Bluesky/Mastodon/Twitter/Facebook to support the Textcasting feature set (which I assume they don’t, or at least not equally). In each of these cases, the user must have an account on those platforms, so they have an identity and the platform can recognize who is posting. Dave Winer mentions that other blogging tools that support peering for the Textcasting feature set is WordPress and micro.blog. Again, both of these tools require a user account, same as the social media tools listed above, for the same reasons.
What about people who just want to post on your own site? Go ahead – nothing stopping you! For people that want their message to go further, we shall have to wait and see if those platforms are open to change. For open source platforms (Mastodon), someone could make changes in a Mastodon version to support Textcasting. The other aspect of the social media platforms, to me, is that they are social. If you are a writer that wants to have interaction with your readers, and your readers are on those platforms, it makes sense to “get your message out there”.
@AndySylvester The number of people who insist, or strongly desire, to use their own editing tool is small. Dave beats the drum for something that he wants and thinks would make the world better, but not many people agree.
@frankm I think your analysis is spot-on, I was trying to figure how to say that without being too negative, your reply is great. On a more snarky note, I thought about suggesting that an API be added to the OldSchool blogging tool…what’s good for the goose is good for the gander, right?
@AndySylvester That said, I do use Drummer to write my microblog posts so I appreciate Dave’s perspective, but recognize I am in the minority. You also know that I also write/maintain single page sites using Drummer and serve via PagePark.
@AndySylvester Should add. that what I post to microblog cross posts to Mastodon, so I am definitely a user of POSSE.
@frankm I think that the ability to do POSSE is great, but to make the Textcasting dream happen, it takes people working together. Having said that, I saw Tim Carmody’s reply (https://kottke.org/23/11/the-future-of-rss-is-textcasting-1) to Dave Winer’s recent podcast, it will be interesting to see if Dave Winer can find someone to work with….
Composing on whatever editing tool a person finds most congenial and publishing from there instantly and accurately to whatever sites the person chooses to connect with — a worthy goal. I imagine most of us know very well the time-wasting alternative.