You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instances can include many very different communities. Some might be compatible with other instances and some may not. At the moment it is an all or nothing thing - either federate the whole instance or don't.
As an instance owner, you may decide against federating with an instance due to some specific communities - this hinders federation
or
As an instance owner, you may have communities on your instance that you think are going to be incompatible with another instance and you do not want to upset the environment other instance owner has created or create work for them banning users in these communities,
Describe the solution you'd like
When Federating with another instance, being able to choose:
All Communities
Whitelist - just federate these communities
Blacklist - federate all communities except these
Additional context
This was originally included as a comment here #1487
Creating a separate issue as requested.
"Do you have to federate all communities on an instance - maybe a setting like
All Communities
Whitelist - just federate these communities
Blacklist - federate all communities except these
I suggest this because 2 instances may have an overlap of interests where it makes sense to federate communities relating to those interests. But there maybe communities on the other instance that are not compatible with yours or worse communities on your instance that may not be compatible with the other instance and will upset the other instance owner.
Rather then federating all the communities and having users banned by the other instance as a result - it might be smarter and create more cohesion to be able to select the communities that you will allow federation with.
The text was updated successfully, but these errors were encountered:
FYI it is already possible to stop federation with specficic remote communities. You can do that as admin by removing the community, which means it wont be shown to local users, and incoming federated messages will be rejected. Nevertheless, this would be a nice feature.
Is your proposal related to a problem?
Instances can include many very different communities. Some might be compatible with other instances and some may not. At the moment it is an all or nothing thing - either federate the whole instance or don't.
As an instance owner, you may decide against federating with an instance due to some specific communities - this hinders federation
or
As an instance owner, you may have communities on your instance that you think are going to be incompatible with another instance and you do not want to upset the environment other instance owner has created or create work for them banning users in these communities,
Describe the solution you'd like
When Federating with another instance, being able to choose:
Additional context
This was originally included as a comment here #1487
Creating a separate issue as requested.
"Do you have to federate all communities on an instance - maybe a setting like
I suggest this because 2 instances may have an overlap of interests where it makes sense to federate communities relating to those interests. But there maybe communities on the other instance that are not compatible with yours or worse communities on your instance that may not be compatible with the other instance and will upset the other instance owner.
Rather then federating all the communities and having users banned by the other instance as a result - it might be smarter and create more cohesion to be able to select the communities that you will allow federation with.
The text was updated successfully, but these errors were encountered: