1) WebFinger IDs that tie accounts to domain names

These were part of OStatus, and Mastodon continued to support them when it implemented AP. With Mastodon servers as the majority of the AP network, other software was expected to keep using them too.

But BS style IDs are just as compatible with the AP spec. Also, as Takahē demonstrated, one AP server can support IDs using more than one domain name. Enabling the same BYOD (Bring Your Own Domain) that BS offers.

(2/?)

2) Admin Wars fragmenting the network. See the campaign against federating with Meta's Chains, or the recent drama around the political views of one Fosstodon mod.

This is a political problem more than a technical one. But there are forms of network management that could reduce the churn. I laid out a proposal here for a numbering scheme that could automate a lot of moderation work, allowing human mods to spend more time considering edge cases together;

https://codeberg.org/fediverse/fediverse-ideas/issues/88

(3/?)

3) Large Mastodon servers are expensive to host

The solution to this is a fediverse made up of many more, smaller servers. With more people actively involved in the governance and funding of the server they use. As well as using AP software other than Mastodon;

https://delightful.club/delightful_fediverse_apps/

Almost all of which makes much more efficient use of server resources than Mastodon's creaking Ruby-on-Rails backend.

(4/?)

I'm still on a billion block lists and everyone just auto-imports them and so I'm automatically blocked for new people who startup an instance and just think of a blocklist as some kind of standard anti-spam measure.

Proposal seems interesting, but it's not going to change all the existing blocklists and just kinda adds a shitty BluCry style moderation standard with extra steps.

Honestly, Nostr seems to have the best design when it comes to censorship and resiliency.