c/asklemmy is not for support. Please use !lemmy@lemmy.ml for support requests and feedback. I have crossposted it there for your convenience.
Asklemmy
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
Instances aren't really blocking others, they're defederating. That means not communicating with certain url's. That's something you can accomplish on a system level, even if the "feature" isn't in the application you are running. (lemmy/kbin)
The devs didn't "give" this ability to instance admins, it was always there.
As for users being able to block instances, I agree. It should be a feature. For now, you can still get there the long way round, by blocking every community on a given instance.
But the vitriol in your wording is entirely unwarranted.