Hey hexbears just want to update everyone.
We took the weekend to properly consider and are removing: programming.dev , aussie.zone , and lemm.ee from our allow-list.
We will look at refederation with lemm.ee after local-only communities are developed. When that feature is available we would really like to consider changing every hexbear community to local-only except for chapotraphouse, askchapo, news, and the_dunk_tank. The final say on if a community is local only or not is 100% up to the mod team on that community.
The reason for this is that lemm.ee despite having twice our monthly active users has a 700k annual comment rate to hexbear's 1 million, in addition lemm.ee has very little active communities that do not exist on hexbear.
Resulting in lemm.ee benefit of federation being votes and views, with a secondary benefit of comments.
However, as expressed by users belonging to marginalized groups, comments from .ee users are often lib-shit and in some cases outright hostile. While many on hexbear love dunking on these lost libs the duty to protect marginalized users is much more important.
The end vote for programming.dev and aussie.zone was a tie, so we decided to break the tie in favor of defederation. The decision on lemm.ee was much harder as the average user did express desire to remain federated however the admin team decided that a temporary removal from our allow-list was the best option.
As an admin team we have never wanted to prioritize growth, and we wanted to give federation with liberal instances a try, however we consider providing a safer browsing experience for marginalized users more important than the opportunity to dunk.
While user side instance blocking and local sort are options, neither address the issue of federated instance users coming into posts in hexbear communities to make reactionary comments.
Thank you everyone who gave input and please provide any feedback, comments, concerns, etc in comments.
final vote count:
federation
all 32
aussie.zone 27
lemm.ee 41
programming.dev 27
lemmy.blahaj.zone 5
defederation
all 40
aussie.zone 19
lemm.ee 4
programming.dev 19
lemmy.blahaj.zone 43
That's 100% shitty, and I did miss counting that one because it was a site ban and didn't list transphobia in the reason, but one user showing up an being shitty like once a month, maybe twice, isn't very many... Like I said before we get more wreckers signing up for local hexbear accounts than that most months by far.
The slava ukraini types again also suck, and its not like I value their input, but I don't think they're particularly harmful in small amounts... The value is about how we respond to them, and what other users from their instance see when we do (their boneheaded thought-terminating cliches getting both mocked and dismantled.) I don't see them as very harmful primarily because they're coming into our space where we have all the power to bully or insta-ban them, but as I'll expand on below, I do also believe we should have comms that are safe spaces away from them too
I'm definitely in favor of local-only comms (though it really depends how it's implemented). I don't particularly want like, the majority of the site to be local-only. A middle-ground where outside instances can view the comm but not post without a hexbear acct would be great for certain comms, and obviously some should be local-only safe spaces.
But something like !traaaaaaannnnnnnnnns@hexbear.net presents a dilemma where, ostensibly it's just memes and comradery and stuff, and that (IMO) should be open to other instances because those instances have trans people (maybe once every week or two we see one from .ee alone, and the fediverse as a whole has many more) and they'll probably not be very interested in our community if all the trans content is hidden away behind a registration questionaire and login screen, but we can't let them in on that comm without, once in a while, having some shitlord like the one you mention... Maybe that would be a good case for a view-only local comm, but idk.
Given that this defed is temporary, and there is a bigger contingent that wants it than I ever expected, I'm fine with it, but I worry that safety concerns along similar lines (especially the slava ukraini types, I really don't think they are a safety issue in the same way, they're just doodoohead liberals) could end up killing the community here outright in the long run via user attrition and infighting and such, and I think that new people making accounts here and/or posting from other instances are more positive than they are negative. Yes, most of the ones we'd want to keep around will make an account here eventually, but 95% of them would just never be exposed to us if we were defedded.
Yeah, i see that !traaaaaaannnnnnnnnns@hexbear.net is reaching a lot of people and i fully agree that this presents a dilemma because i think it's a good and valuable thing both that trans people from other instances, especially eggs that need a cracking, get to see us and that we confront cis people with actual trans points of view. Making cis people listen in on us authentically talking about our own experience among ourselves instead of being talked about is an important part of normalizing queerness, i absolutely see the value in that. I think that under agitation and community building perspectives, it may be a good thing when that comm remains public-facing, but that's something trans comrades should decide on their own. Going local-only or not should be a decision the comms make for themselves. If that doesn't leave a public-facing trans comm, that means we should consider other options, whether it's a new comm for that purpose or crossposting to relevant fully open comms.
Once the feature actually exists and gets used it will be a lot easier to draw that distinction and have it be understood by the whole userbase too
https://hexbear.net/comment/4543245
fwiw, the traa mod team is talking about ways to square this circle - mainly by building automod-like tools to help us by automatically remove comments from instances not on an internal whitelist while flagging the comment for restoration after manual review. that way we can keep the comm open to the wider fediverse, allow the instance to federate more openly without threatening our userbase, while still allowing us to approve users once we're reasonably certain they're trans. it remains to be seen if this is possible but we're going to give it a shot and hopefully it's a happy compromise for everyone, if it works out. this approach also means we don't have to wait on the lemmy dev cycle / put more work on our own very thinly stretched dev team. this may also be valuable to the other comms for marginalized comrades.
generally, I think we can do a lot better than we currently are, if we develop better mod tooling.
That sounds like a highly useful feature.