this post was submitted on 12 Jun 2023
492 points (100.0% liked)
Technology
37739 readers
500 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
I believe from Instance A, you can only subscribe to a community on instance B if both A and B allow it. Otherwise you need to create a different account in instance B.
This way an instance can have some kind of governance over its users and the content they see.
I wonder if an SSO solution exists and is supported by many instances, so as a user you won't notice much of the different accounts you could have.
not OP, but thanks very much for this very straightforward explanation, I've been struggling with figuring out all the pieces to the puzzle.
You can define whitelists and blacklists separately. By default none of these are enabled, and any instance can federate with any other instance.