This is terrific. Thank you for starting this discussion.

I don’t think we can or should wait for individual users to make these decisions. Server admins are the ones who understand the risks and so should make this call. Guidance for server admins based on past experience (cough XMPP!) should be quite welcome.

I might refine the bit about altered API versions to really focus on the real problem: proprietary extensions. We probably want to leave the door open to try out additions to the spec that come with detailed RFCs.

But we know from XMPP that proprietary extensions are a huge problem.

As part of the eternal September myself, we didn’t just use AOL disks as coasters, we used them for awesome pranks like filling eachother’s cars to the brim with them. It was truly astonishing how many of those disks were around.

I’m planning the same.

Let’s not defederate from every corporate player. Some of them can probably respect reasonable rules of civility.

But fuck Meta. We already know how this plays out.

We know there’s a huge wave of hatred and misinformation incoming. We’ve seen it on their other platforms.

Yeah. I’ll switch to an instance that is defederated from Threads, if mine doesn’t.

I left Meta’s other properties to avoid state sponsored hate speech. I won’t use a platform that gives hate speech a platform.

I don’t need to wait to know if Meta will do that. I already know.

I’m all for companies participating in open source communities… but this is the company that routinely blocks me from viewing my aunt’s reposts of Russian state sponsored racist propeganda just because I don’t install the incredibly invasive mobile app.

I can imagine a few ways that this could go wrong…