Last thought on #EEE: We need to support our standards makers STAT. The best defense against "extend" is a clear line of what we are defending.

#ActivityPub has needed a robust "test suite" to test compliance for a while & good efforts were unfinished. They need to be picked up at warp speed. To see an example of his working for other tech see: https://webmention.rocks/

The creator of the Wordpress ActivtyPub plugin said that he *wished* he had this.
More on why in my last post next.

🧵 8 of N

What else can defend against the "Extend" of #EEE?

Having a broad set of OTHER allies inside the tent of stakeholders. Growing the base of those who "embrace" it to even out the power dynamics.

And btw, defederating developers PREMPTIVELY before they launch a single activtypub server, is the fastest way to make OTHER potential developers run for the hills. (Actually to run to Bluesky)

The last thought for the night on this is what I think is the most important. Up next.

🧵 7 of N

So, to avoid the "Extend" of #EEE, which is the real risk point, what can be done since mass defederation won't protect ActivityPub?

This isn't a new battle. Tons of efforts to #EEE open tech fail. As @emc2 has put well #OSS software has fought and won this battle many times. As @davew the godfather of RSS & Podcasting said: "Podcasting has withstood countless attacks like this, and has always been left standing as unsullied as ever."

We know how to win this. Some tactics next.

🧵 5 of N

To the argument that we should defederate to avoid #EEE: We cannot avoid Meta's embrace of the open ActivityPub standard.

Even if the entire existing Fedi pre-blocked them. IG has 1.6 BILLION users. in one day just on their own they will be the size of the current Fedi's MAU and grow from there.

Instantlly the biggest ActivityPub entity on the planet. With or without a mass block.

So if we can't stop the embrace, what can we do to combat the second E?
Will cover that next.

4 of N🧵