I hope this is the right place to discuss a potential feature for lemmy.

I’ve been reading a lot of the defederation calls from instances and their users. More often than not, this was due to very specific elements of those instances; trolls, extremists, etc… But in my opinion, defederating a whole instance because of that is a sad pity.

I was thinking a way to solve this would be to have a federated blacklist. Instance Admins would ban user accounts from their instance and that would be added to a list that could be consulted/automatically used by other instance owners. They would ideally be able to set parameters, like banning users from a list accepted by a number of other instances, a specific reason for the ban, or banned by specific instances.

This would lessen the administrative load, protect instances, allow different instances with shared concerns to help each other while allowing their own users to interact with the ‘compatible’ users and communities from other instances.

Just an idea and wanted to bring it up and hear some thoughts.

  • CleoTheWizard@beehaw.orgEnglish
    3·
    1 year ago

    I feel like users should be able to block and unblock instances at will. So let’s say that instance A defederates from instance B. So instance B users cannot comment on instance A. But instance A users should be allowed to comment and interact with instance B if they choose to unblock instance B for their own personal reasons.

    Is there a problem with this that I’m missing? I just feel like I should be able to choose to interact with a community if I choose, but my instance should be able to keep the other instances away if they want to.

    • PotjiePig@lemmy.worldEnglish
      1·
      1 year ago

      When a server A federates with server B, it allows itself to scrape information off it and synchronise with it so that its users may comment, receive updates etc. Because these are individually run, and decentralised, each server will need to comply with its own local laws.

      If server B decides to host a community with kiddie porn, Server A now will synchronise and share that information with its users, storing elements of the information on it’s own servers. This would put the owner of Server A at massive risk and would be a responsibility of the admin to keep themself protected and in line with the Law. Since you can’t control anything that happens on Server B.

      If server B gets taken over by Russian spam bots, and they are able to comment wherever they wish, you wouldn’t have any control at moderating those accounts as they are not on your server. It’s easier to just block that server entirely.

      Defederating but allowing commenting means that you aren’t actually disconnecting, and keeping a tunnel open and swapping data and updating fresh comments.

      It’s a gray area as the line can become blurred with things like The Donald, which might be largely unpopular and racist but it doesn’t break any laws. so deferedating willy nilly can easily become a tightrope walk between protecting users from bad actors and quelling free speech. That’s why we can block those communities ourselves.

      True that it’s not the perfect system and as servers connect and disconnect from one another, communities may fracture and users may need to create new accounts or have multiple which can be inconvenient, but it’s the most logical system for now.

      There may come a time where a middle step is needed, once instances become so large that defederating can be a massive issue, it may be nice for an instance to block off communities from other instances while not actually fully defederating.