trwnh.com/unified.test.hugo/content/monologues/social-web-storage-identity-protocols/index.md

1.6 KiB

+++ title = "the future of the social web is in storage and identity protocols" summary = "the current situation of everyone fighting over the ghost of activitypub is a convenient distraction to stop anyone from declaring themselves the canonical interpretation. it also presents an opportunity to regroup and refocus on the social web" date = 2024-10-19T11:10:03-05:00 source = "private" +++

actually the thing i worry about is that i distinctly see a future in which it stops being the Mastodon Protocol and instead becomes the Threads Protocol. all it would really take is for meta to launch a developer portal for federating with threads, and for them to formally define all this implicit undefined stuff. the current situation of everyone fighting over the ghost of activitypub is a convenient distraction to stop anyone from declaring themselves the canonical interpretation. it also presents an opportunity to regroup and refocus on the social web, if the necessary work is done to bridge the gaps and fill in the holes. whether that ends up being activitypub or something on top of activitypub or something else entirely is kinda irrelevant. i think the key going forward is actually gonna be the storage and identity protocols, not the transport protocol (we have more than enough of those). something like solid or atproto is needed to provide "personal data storage", and something like did service is needed to provide a stable base against which you can resolve relative references. this should mitigate the problems of link rot and services going down -- not completely solve them, but make them a lot less likely to happen.