On-ears this morning, on the road:
What does that mean, exactly, and why does it matter? Bluesky founder and CEO Jay Graber says social media is stagnating because “we're in this trap where users are locked in and developers are locked out.” It’s time to open things up again, she states, like in the innovative early days of the internet.
https://dot-social.simplecast.com/episodes/jay-graber
The transcript is okay'ish, but it's still worth a listen. Generally, repeatedly, what I really, fully, totally admire about the atproto / Bluesky approach is their take on user data and identity even as a mere mortal. Like: Even without being required to "run infrastructure" of your own, be able to tie all you have to your own domain name, your own online identity and be able to take, handle, move that as you see fit. Too, in example, the option to use a custom domain name even on infrastructure operated by others has been around for ages in Tumblr and for quite a while in micro.blog, and whyever this hasn't been a first-class baked-in feature with every other federated network and most specifically "newer" implementations and standards such as ActivityPub or Mastodon is something I have a hard time wrapping my head around.
Morning audio, longform edition:
In February, everyone who went to a concert in the old medieval town of Halberstadt, Germany, showed up 23 years late. This is also concert from which everyone walks out early. The performance is of a piece called ORGAN2/ASLSP. ASLSP stands for “as slow as possible,” which is how the composer meant for it to be played, and this particular day would involve a chord change. The last time ORGAN2/ASLSP had a chord change was in 2022, and this new chord will play until the next change, in August, 2026. There is a change the year after that, and the following year, and so on, until the year 2640. The full performance is meant to last 639 years.
https://99percentinvisible.org/episode/as-slow-as-possible/
Have to admit I've just briefly been to Halberstadt ages ago and quite before that project started. Yet, I've always had a thing for experimental music and drone stuff, and this seems to be as droney as it might get. And all along with the sounds, it brings up some quite interesting considerations regarding melodies and chords and the sounds in between and duration and time itself. (Even though I was a bit stunned the concept of a pipe organ apparently needs a deeper explanation.)
Listening recommendation for the morning:
There are a lot of companies and ideas competing for space on the post-Twitter internet, and Jay makes a convincing argument that decentralization — the idea that you should be able to take your username and following to different servers as you wish — is the future. It’s a powerful concept that’s been kicking around for a long time, but now it feels closer to reality than ever before. You’ve heard us talk about it a lot on Decoder: the core idea is that no single company — or individual billionaire — can amass too much power and control over our social networks and the conversations that happen on them.
https://www.theverge.com/2024/3/25/24108872/bluesky-ceo-graber-federation-social-media-decoder-interview
There are quite some reasons that leave me very cautious about Bluesky, one being for sure the fact there's one commercial entity currently backing this service / protocol, especially one that has risen from the same ecosystem that caused a lot of the trouble we do experience with current social media platforms. But, I've then and now been at odds with ActivityPub as a protocol, which gets worse the more I dig into it, and from that perspective, it seems the AT crowd gets a lot of things right, considered a lot of things that don't just seem obvious at least in the 2010s but actually surprising to see them missing from ActivityPub, a spec that has been established at roughly the same time: Full account portability (the idea of comparing personal data, conversations, comments, posts, ... to a github repository which "of course" you want to easily be able to take, backup, move around, ... seems both stunning and painfully trivial), support of custom domains for users (which Tumblr has already been supporting for years now), distributed curation and moderation (because most obviously community structures will be different to server or domain structures and not necessarily live on one instance exclusively) - in a way I really do hope they "show don't tell" by submitting that protocol to some standardization body anytime soon. Maybe this, too, could provide a good option for the "open" fediverse to counter the problems that might arise the very moment platforms like Meta / Threads fully embrace ActivityPub. (I also found it rather interesting to listen to what she had to say about why Meta might be more into ActivityPub than AT - being "server-centric" rather than "user-centric" - but that might just be a loose end of things.)
Been in my playlist this morning, and, though obvious in some ways, still added some points and leaves me pondering that particular issue more than usual:
At the outset, including for the IBM System three sixty, the computer with a single CPU was not actually multitasking. It was doing the same thing that our brains do. It was jumping back and forth between tasks really fast to make sure it was doing them both adequately. So when we kind of figured out that there was a problem with processing, that there were limits to it. We established very quickly something called a processing bottleneck. That, yeah, there is. It's documented humans do not multitask to begin with, and when we try to multitask, the results are terrible.
via SYSK: Multitasking: Working slower with worse results