shepherd, 10 months ago (edited 10 months ago)

Hmm interesting. I do think it's just as important that we double-defederate unfortunately. Meta/Threads has to be treated as if it's contagious.

If we stay federated with an instance that has accepted the Embrace, what do we do when the Extend happens? Is that when we defederate? Will we even recognize it?

EEE only works because it's difficult to see it happening to you. Instances that ally with Meta/Threads will actually present the same threat of EEE, or even a greater threat, because the Extend step may appear to come from non-Meta instances.

Imagine ActivityPub upgrades developed by a Meta/Threads-ally, let's say improved inter-instance moderator tools. That sounds good right?

It's basically all the exact same arguments again, but with a middle man.

• Meta/Threads have different foundational priorities (namely, profit) and real incentives to monopolize.
• Meta-ally instances have real and implied incentives to accommodate
  Meta/Threads.
• And we have incentives to accommodate the instances that we federate with, so of course kbin would use the well-developed new mod tools right?
• Seems crazy not to, even if it was developed by a Meta-ally. Right?
• Great! Repeat for thousands of tiny changes, that's called Extend.

That's how accepting EEE works, each little step looks great but big picture we're unknowingly in trouble. We'll have to treat any Meta/Threads-ally as if it is Meta/Threads. (Hell, some of them probably will be lol, the fediverse is just asking for astroturfing lol.)

We can trust instances that don't have economic incentives. But any instance that shows they can be swayed by money, or that shows they'll accommodate instances driven by profit, well they're showing that they'd consider eating us to become the next reddit.