Earlier this week, Dave Winer (the inventor of RSS and lots of other notable software, and one of the earliest bloggers) made a podcast for me. He posted it publicly, so it wasn’t sealed like a letter, but it was addressed to me and responding to something I wrote on Threads. I don’t think I’ve ever been the personal addressee of a podcast before: like an @-reply, but in audio.
For some reason, it reminded me of the poet Frank O’Hara’s "Personism" manifesto:
[Personism] was founded by me after lunch with LeRoi Jones on August 27, 1959, a day in which I was in love with someone (not Roi, by the way, a blond). I went back to work and wrote a poem for this person. While I was writing it I was realizing that if I wanted to I could use the telephone instead of writing the poem, and so Personism was born. It’s a very exciting movement which will undoubtedly have lots of adherents. It puts the poem squarely between the poet and the person, Lucky Pierre style, and the poem is correspondingly gratified. The poem is at last between two persons instead of two pages. In all modesty, I confess that it may be the death of literature as we know it.
But this is a digression. The ideas Dave is talking about in this podcast are serious (even if he is laughing a lot), and he spells them out in text at a site called Textcasting.org. Here’s the philosophy:
- The goal is interop between social media apps and the features writers need.
- What we’re doing: Moving documents between networked apps. We need a set of common features in order for it to work.
- The features are motivated by the needs of writers. Not by programmers or social media company execs.
It’s a proposal to build, using technologies we already have and understand very well, a very simple social media protocol that is completely agnostic about what editor you use to write your posts and what viewer you choose to read it. Writer/authors would have more control over styling, links, media enclosures, etc., and readers would have more control over how and where they consume it. It’s decentralized social media, but without the need to peer through ActivityPub or anybody else’s API and squeeze our toothpaste through its tubes.
Dave asked me to respond to his podcast, and while I thought about making an audio response, a blog post is more my metier.
If this is going to work, I think there are at least four problems we’d have to solve:
- Everyday users need a default writer and reader, preferably in the same place. It would be wonderful to be able to bring your own tools to bear and plug into the endpoints and have it just work. But nobody should need to fish around for that stuff. The defaults should be just opinionated enough (for instance, I like the Mastodon client Ivory, built on the ashes of TweetBot) that people feel like they’re getting a slick, finished UI and UX experience. That’s why people are gravitating to Threads: Meta knows how to put one together. But that’s not rebuilding the electrical grid from scratch. We know how to do that too.
- We need user and content discovery. We have to be able to find each other. And that’s what a lot of the heavy lifting of these other platforms is devoted to: to find people and things you didn’t know you were looking for. Again, this feels like a solvable problem.
- We need metrics. Most writers work for publishers, and publishers want to know whether their content is reaching people. It’s tempting to load this up with a lot of cruft, but impressions, clicks, reposts, quote posts, etc. is doable without a ton of advertising nonsense. Social media companies figured this out, but bloggers did too, a lot earlier.
- We need moderation. A wide-open social network becomes a highly abusive social network fast in 2023. And nobody who isn’t a Nazi wants to hang out at a Nazi bar. So we need tools to block and flag and maybe even ban people who use the platform to spam each other, impersonate real people, and abuse other people on the platform. In the now-seminal "Welcome to Hell, Elon," Nilay Patel correctly identified content moderation as Twitter’s actual product: it’s what Twitter-the-company added to Twitter-the-protocol. We don’t necessarily need a Twitter-sized overhead, or a complex system of federated moderators, but it’s going to be a problem, so we’d need tools to address it.
But in terms of philosophy and vision, I’m all for it. RSS remains incredibly vital to what I do, and its potential as both a reading AND a writing platform remains untapped. You can write using your own tool and broadcast it everywhere. And Dave’s right: this worked for podcasts (the phrase "anywhere you get your podcasts!" is a great advertisement for interoperability breaking any single platform’s dominance), it worked for blogs, and it can work for this strange multimodal thing we’ve created called social media. It worked for the world wide web! And I will be ride or die for the open web until my life comes to an end.
Now we just need to work together to make it happen. And I confess: my tools are limited here. I can’t (really) code, I can’t (really) design, I can’t build a moderation feature. I can evangelize, I can strategize, and I can write. But I can do those things (in all modesty) very, very well.
So let’s do this thing. Why not? Twitter is dying, and Facebook is fading. None of the replacements have eaten their lunch yet. Why not make a swing for the open web? Why not try?
Title: The Future of RSS is Textcasting
Source URL: http://kottke.org
Date: November 3, 2023 at 07:07PM
Feedly Board(s): Englisch