I mean.. isn't the point of decentralization that you can build your own service with the same protocol and still communicate with the other services?
There are ongoing initiatives for alternative stacks speaking the AT protocol, like Northsky, or Indiesky.
There's also community-run labelers and blocklists for moderation. You can make the moderation stronger, what you might not be able to do is make it weaker if the PDS takes an account down fully, or the indexer/relay refuses to use it.
Does the DCO really offer a real guarantee? it looks like it just adds a
Signed-off-by John
line at the end of the commit, with no actual signature checking that enforces any particular version of a particular document is being acknowledged. IANAL but it doesn't look like something proven to work in court to give legal protection.Sure, it's easier to simply add a sign-off-by line than actually accepting a legal agreement, so it reduces the barrier of entry, but if this were really enough to establish the conditions to shift liability then I don't see why companies wouldn't start using their own DCOs and extending them, essentially just being a more convenient CLA (which is a license agreement, not a copyright transfer, even if some might add terms that allow relicensing.. which anyway is already possible given the project is already MIT licensed).