Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More granular administration tools for federating with other instances #3255

Closed
3 of 4 tasks
jordan1776 opened this issue Jun 22, 2023 · 1 comment
Closed
3 of 4 tasks
Labels
area: federation support federation via activitypub enhancement New feature or request

Comments

@jordan1776
Copy link

Requirements

  • Is this a feature request? For questions or discussions use https://lemmy.ml/c/lemmy_support
  • Did you check to see if this issue already exists?
  • Is this only a feature request? Do not put multiple feature requests in one issue.
  • Is this a UI / front end issue? Use the lemmy-ui repo.

Is your proposal related to a problem?

When I heard about beehaw defederating with sh.itjust.works and lemmy.world , it didn't quite sit right with me. Because of the state of the mod tools and open user registration on those instances, they are effectively forced to de-federate to protect there community.

But to me, as though the userbase between the instances are fairly similar, de-federation over reasons like this are somewhat overkill. If there was a middle ground between completely separated and fully open.

Describe the solution you'd like.

I propose a middle ground between blocked and linked instances. This group would be "Linked with restrictions". As the name implies, these instances would be federated, but with restrictions. The options would be:

  • Allow inbound user interactions (voting, commenting, post) (from that instance to yours)
  • Allow outbound user interactions (to that instance from your users)
  • All in 'All' feed

The granularity could go down to the community level (such as allow federation with this instance, but restrict access to these certain communities, or the opposite of block these forms of interaction with this instance, except for a selected list of there communities)

The big thing is de-federation should be a final option, where there should be no question of "maybe we can federate with that instance some other time" as in the meanwhile regular users who done no wrong are punished at no fault of there own.

Describe alternatives you've considered.

Improve mod tools?

Additional context

No response

@jordan1776 jordan1776 added the enhancement New feature or request label Jun 22, 2023
@jordan1776 jordan1776 changed the title More granular options for federating with other instances More granular administration tools for federating with other instances Jun 22, 2023
@lionirdeadman lionirdeadman added area: federation support federation via activitypub Administration labels Jul 19, 2023
@dessalines
Copy link
Member

This should mostly be handled by person-based instance blocking which should be in the next release.

@dessalines dessalines closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: federation support federation via activitypub enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants