this post was submitted on 23 Mar 2024
70 points (100.0% liked)
Beehaw Support
2796 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I agree, but my point wasn't a perfect analogy. I merely intended to point out the considerable difference in the workload of the two 'extreme' approaches.
User-defined filtering is also very nice to have, but I feel like instance-level filtering is what gives an instance its unique look-and-feel. And from what I've read, Beehaw has also defederated from certain instances 'only' because moderating all the undesirable stuff coming from there put too much of a strain on the mod team. Hence my river analogy.
My personal opinion is that federation is a wonderful concept, but it sometimes comes at a cost that may outweigh its benefits.
Beehaw needed to:
...the only mod tool available, was defederation. This is a clear shortcoming of the tools, which right now only allow an "all or nothing" approach, not of the federation itself.
Not exactly; the rules and community of an instance, are what give that "unique look-and-feel".
In an alternative reality, with a slightly different approach to federation, an "instance" could be a curated preset the user imports into their client.
Actually, that could be done with the Fediverse, if someone decided to do it.