Yup. Anticipatory obedience isn’t the way to go!

Okay but… have you ever tried to force your group to get together despite those two being unable to get along? e.g. Russia vs. Ukraine? China vs. Taiwan? Israel vs. Palestine? USA vs. a neighbor with oil?

Whether one side (e.g. Ukraine) can “get along with” the other side there (e.g. Russia) depends a LOT on whether they are able to agree to follow some shared rules (e.g. to not murder the other side). These are not mere political differences in the sense of left vs. right, but rather those who are proud to remain ungovernable (while seemingly not understanding what that phrase originally was intended to mean) vs. those who would rather nope out entirely than exist side-by-side with them.

Please also note that Lemmy’s block tools are so misleadingly misnamed as to be almost worthy of the moniker of calling it disinformation. What “blocking an instance” does is to:

• Mute communities on that instance from the user, preventing discoverability and blocking that content from showing in your personal feed, including when browsing All

What that so-called “blocking” does NOT do:

• Hide content from those users submitted to communities on remote instances
• Prevent those users from being able to reply to, famously including vote brigading on, your own content
• Prevent those users from sending you DMs, which at first were not allowed to trigger notifications, but the Lemmy devs reversed that decision and now these “blocked users” can trigger notifications - which bc of the “style” preferred by people on those instances, can continue for WEEKS and WEEKS after you so much as reply to a post that you encountered on All, without having read the sidebar and so not knowing that this style differs from what you are used to

Besides, even if insurance blocking actually worked, it would still do nothing to not showcase the content for an anonymous guest account or a newly created account, i.e. it does nothing to help others deal with “the situation”, only yourself. Which is especially notable when people access Lemmy’s content from apps like Voyager that by default does not show the instance name, thereby treating all content from all instances as being equal. However, I would argue that e.g. Poland does not fear attack from all nations equally - does Poland want to be on guard against Taiwan? Or North or South Korea? What about Russia?

Defederation is a blunt tool, but is virtually the only one offered by the Lemmy devs. When the software is made more robust to offer some other alternative… then this issue can be revisited at that time.

Also, you are free at any to self-host your own instance. But to tell Ukraine and Russia that they must get along… or else what? I am saying that I reject the underlying premise of your argument. “People getting along” should not be the ultimate goal of the Threadiverse. A better goal IMHO would be “People enjoying their experiences while here”. Which for many, means blocking Hexbear - and yes, for some it means NOT blocking it - and therefore since the answer is neither a clear yay or nay, we are forced into preaching the controversy for every new potential member, even though that very complexity itself is often what drives others away.

Though PieFed.zip offers an intriguing and innovative compromise: upon joining the instance a user block is placed upon the Hexbear and lemmygrad instances, and a message sent to the new user about how to remove or place such blocks. This makes federation with those highly controversial instances as opt-in, as opposed to opt-out or impossible to block or not block. That’s really neat! However, that delves into a whole other can of worms on how PieFed instance blocks have problems - namely that people on the receiving end can still reply to them, though only people on the same originating instance will see those replies (or perhaps it’s worse and everyone using Lemmy will see them while everyone using PieFed will not? or perhaps something else altogether?). Also this in turn opens up an entirely new rabbit hole on top of that, where Lemmy and PieFed (and Mbin, and nodeBB, etc.) would need to agree on a set of shared practices…

In short, the technology of the Threadiverse is still quite primitive in so very many ways, despite the upcoming release of Lemmy vs. 1.0. Yes defederation is a very blunt instrument, but it’s all that we have been given to wield for the most part. But the alternative IMHO would be far worse, being forced into allowing bullies to thrive. The Paradox of Intolerance is ironic, but very real: allowing the intolerant to exist in your space, worse yet platforming and even promoting them, means that you yourself are intolerant. Fences between neighbors is the only hope the Threadiverse even has of surviving. Yes you are allowed to be sad at that fact, but it remains true nonetheless. Move past your sadness, to get to what must be done to thrive and move forward in a positive direction?

e.g. learn Rust and contribute to the code development of Lemmy!? Unfortunately, merely donating money is unlikely to help, as much of those funds go into the moderation and instance maintenance costs of the “highly controversial” Lemmy.ml, and the devs have refused to open a way to provide funding for the former independently of the latter. Or learn Python and contribute to development of PieFed? It likely won’t help with interoperability between PieFed vs. Lemmy, and both require investments of several years, but if you want to help then there is no better way. So long as the technology remains as primitive as it is now, these kinds of blunt instruments are all that are available to us - someone would need to invest the effort to provide better.

TLDR: there are extremely good reasons why things are as they are now.

Yes; the percentage underneath an instance is its proportion of the overall Threadiverse userbase. The percentages on the large arrows are the sum of the userbases within the associated box, indicating the extent to which an instance is defederated (somewhat of an underestimation, given that 12% of users are unaccounted for).