There is currently a rumor afoot that Zuckerberg is planning to expropriate the AT protocol for Threads. If true, the pattern is undeniable, suggesting that any remotely open social media protocol which finds its footing will be subjected to a Zuckerberg incursion. Accordingly, future protocol developments should insure Zuckerberg-resistant measures as early as possible in their life cycle.
🐸 Protocols should incorporate Zuckerberg-repellent technology into their foundational codebase
🐸 Protocol projects should exclude the participation of anyone who could later become a Zuckerberg collaborator (e.g. het cis white guys who want to "keep politics out of it")
🐸 Protocols should be oriented, both in developmental organization and in the emergent community topologies they engender, to horizontally distribute and diffuse power; power concentrations become throttle-points for corruption, primed for Zuckerberg exploitation (e.g. SWICG, SWF)
🐸 Protocols should be designed to encourage the kinds of communities in which Zuckerberg-hate is a prominent characteristic, and which will be quick to activate and organize a social opposition to Zuckerberg incursion (e.g. FediPact)
We can take our lessons from the current failures; ActivityPub was deficient in all of these requirements except the last, and if the rumors are true, there's no hope at all for AT. Put simply, the protocol that powers the decentralized social network of tomorrow will be the one with the most successful Zuckerberg-resistant adaptions
#DefederateMeta #FediPact #Meta #Zuckerberg #Threads #Facebook #Instagram #SocialWebFoundation #SWICG #Bluesky
