this post was submitted on 17 Jun 2023
310 points (100.0% liked)
Technology
37738 readers
48 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
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
The thing that I think didn't sit right with a lot of people is that Beehaw's admins apparently said (I haven't seen it first hand) that they see a future in refederating with Beehaw's communities being kept private, only accessible to Beehaw users, while Beehaw users would get access to the wider Fediverse.
To be honest, I feel that it's Beehaw's prerogative to grant or revoke access to anyone on other instances, but also I wouldn't be surprised that in turn other instances would not federate with an instance that would not give access to other instances' users for its communities.
That’s sounds…not possible. At least at the current iteration of the software. It also seems like kinda the opposite of what the fediverse was meant to be.
I just looked at one of my communities and the only main setting is whether mods can post. You can’t set perms at the community level to exclude certain users or make them private
On the latter part of your reply. I agree. It is their prerogative but I do see obvious benefits of not going say…allowlist only federation. We are swiftly hitting a point where there will need to be instances just to manage user registrations and avoid bottlenecks and scaling issues.
Yep, not possible currently, hence defederation for now. The point is that there must be some change, better mod tools, less new users, or something to change the calculus for Beehaw to refederate. The point Beehaw is making that they can't create the community they want with the current software iteration, either with regards to perms or mod tools without defederating from other big instances.
BTW that's my point, it's not what the Fediverse is meant to be, that's why it's weird. Again, this is second hand info, so take it with a grain of salt.
IDK why is everyone making accounts on the 3-4 biggest instances.
Makes sense. It was the main reason I just built an instance, for speed and performance reasons, but also to have control on my account. I have the know how so f-it.
And I’m mulling over just opening it if there’s a huge surge come 7/1/23. Though I may stick to application based onboarding to make sure it’s not totally overwhelmed.
I do, personally, think it's reasonable for an instance to have "private" communities exclusive to their own users. This is likely a subject that comes down to personal belief, but after dealing with so many trolls and bad actors on other platforms, I absolutely do see a need to have those kinds of permissions.
This wasn’t the impression I got from the Beehaw admins. I believe they felt that blocking lemmy.world users from Beehaw but still being able to have Beehaw users interact with lemmy.world would have been better than full defederation, but I don’t think that was the ideal solution either. Something like an approval process for an external user to interact with Beehaw communities would be preferable.
Also, Beehaw could go fully private today if they wanted to, that definitely doesn’t seem to be their intention.