… are quickly defederated from by the rest of the Threadiverse, but such requires effort on behalf of the instance admin. I thought, though perhaps I am wrong.

I have no source for this, but I think, now, first content/post/comment from a new instance has to be approved by an instance admin (could be wrong and misremembering though). If not, might be worth seeing if that is a option admins would want added. Thoughts?

… or to begin blocking people, one by one …

All of which is a lot of effort, especially since it must continue to happen with each fresh new alt made to subvert bans. Each new joiner must then be subjected this again and again, like a hazing ritual that we who have been through such already now offer little to no help to new joiners to avoid. Except for your codeberg request that will help to change that - hooray!

On that note, it seems Pylova has finished writing up the block subscription code (yesterday) and it’ll be in the next update (unknown date).

… if ML were to ever go down, that content would continue to remain, foreve, just like happened with Lemm.ee) …

It could remain forever, but I think most instances (or at least Piefed instance) are set up to delete old content after “x” amount of time. Alternatively, admins could just manually delete the old content, if they wanted.

… A place’s reputation should proceed it, not be entirely ignored and force each new joiner to discover it all over again on their own, as what happens with ML.

Agreed. I think .zip’s approach where it has the default blocks and explains them is a good approach. If the subscribable blocks also make it into the on-boarding, I think there will be a large swath of new .zip users who almost never encounter the triad issues (assuming Pylova subscribable block list spreads back to Piefed and beyond). If that on boarding spreads throughout the Threadiverse, the triad could be dealt with, without major confrontations, which I think most admins don’t want to deal with.