While it's probably just an extension of Jack's obsession over blockchain, it's a bit interesting that you'd have to use Twitter to apply: there are a few truly-decentralized/or federated solutions that have been proposed and have an active userbase, and the authors of the good stuff don't tend to be on Twitter.
For example, one of the people working on one of the most prominent pieces of software implementing the ActivityPub specification has proposed/is ~close to releasing a reference-implementation of one [a non-AP distributed protocol], which seems to solve most of the issues that Twitter would need to solve for privately-scoped posts (a major problem with most federated and decentralized social media), with plans to ~eventually get around to solving publicly-scoped things:
(Pleroma doesn't really do per-user threading, so the responses to the original post are mixed in with the author continuing the original thread. Reader beware, etc.)
OCAP is such a needed feature. One of my concerns with Twitter is that it's essentially unsafe -- while safety is a tricky thing to guarantee in decentralized networks, OCAP makes serious steps towards addressing the problem.
I'm glad they're planning on using ocaps. Not so optimistic that twitter understands ocaps though. They should hire Mark S. Miller to consult for them or something.
For example, one of the people working on one of the most prominent pieces of software implementing the ActivityPub specification has proposed/is ~close to releasing a reference-implementation of one [a non-AP distributed protocol], which seems to solve most of the issues that Twitter would need to solve for privately-scoped posts (a major problem with most federated and decentralized social media), with plans to ~eventually get around to solving publicly-scoped things:
https://socially.whimsic.al/notice/9p6cjMLaIZxtCKyNto
(Pleroma doesn't really do per-user threading, so the responses to the original post are mixed in with the author continuing the original thread. Reader beware, etc.)