Lemmy Defederation Sync (LDS). Contribute to Fmstrat/lds development by creating an account on GitHub.
Hi all, I'm a Lemmy FOSS app contributor that's made a couple of tools for people starting small instances including Lemmy Community Seeder (LCS) for building content on new server's All Feeds and Lemmy Post Purger (LPP) for clearing old posts on smaller instances.
Today I'm releasing Lemmy Defederation Sync (LDS). When launching a new Lemmy instance, administrators may not understand the necessity of defederation with problem instances. Using LDS, you can sync your instance's "blocked instance" list with that of another server(s) whose admins you trust.
Shared Fediblocks are a plague. Get added to one by somebody that personally dislikes you and every instance that uses the block will unknowingly block you.
The issue is there's no oversight here, or at the very least, no oversight that we can trust to be impartial.
When parties form a federation, it's usually with a signed agreement, to maintain the integrity of the federation and keep it together. Shared standards, rules, ideals, regulations, etc. All I'm seeing here are parties trying to carve out a sub-federation, and with no neutral oversight, it's just going to become a "people like me" circle.
And I guarantee at some point people are going to start thinking "Hey, if this instance isn't subscribing to the shared blocklist, that must mean they want those other instances around, and therefore they deserve to be added to the list"
Then just like that, the fediverse has a defacto authority. Instead of one sepz, we have a council of them from the largest instances.
And I guarantee at some point people are going to start thinking “Hey, if this instance isn’t subscribing to the shared blocklist, that must mean they want those other instances around, and therefore they deserve to be added to the list”
Already is happening on the Mastodon/Pleroma side of the Fediverse. Instances getting de-federated because they dared allowed their users to see posts from "bad" instances
Lemmy is built as a single instance with federation capabilities as an after thought. The biggest clue to this and the reason why it will always re-centralize is that communities are server bound. There is no fediverse wide community and they is by design. Read this closed issue
Don't worry, highly popular instances won't get on the block list and small instances don't matter enough for it to be a problem. Power always favours the powerful.
But isn't that what this program does? It allows you to choose an instance with admins that you trust. And those who want to review every single one manually can still do that. I'd love this tool. The ones setting up these servers aren't stupid. They can use their judgement and use this tool if they want!
This sounds a bit like how to bring the shared blocklists from Twitter to Lemmy. Those were a disaster on Twitter, and I don't expect it'll end any better here either...
Please don't use tools like this. Manually curate instances you feel the need to defederate with. The Fediverse was built on a model not unlike that of email. You wouldn't just randomly block whole email providers willy-nilly, so you shouldn't do so here on the Fediverse either.
Shared email Blocklists are the norm, not the exception
As a professional IT admin I would absolutely blackhole any vile hives of scum and villainy rather than dealing with their BS. If someone is going to do that for me I'll use the tool.
Shared email Blocklists are the norm, not the exception
Shared blocklists in IT are managed by industry professionals for the purpose of safety from malicious activity and there are vetted processes for being removed from days lists. False positives happen, but you aren't hung out to dry if you get hit, you just go through the process and clear your name.
Most of this "Fediblock" nonsense is several orders of magnitude less reliable, and filled with toxic people pursing personal grudges. There's no process to clear your name, and I've personally watched multiple admins and their entire communities be publicly mocked and told they "don't owe you anything" for merely asking why they were blocked, let alone how to remedy the situation.
These are not remotely equivalent and anybody who trusts them is a fool. The Fediverse has a serious problem with vile, bitter people who would not be out of place running an HOA. If we are going to emulate the blocklists common in IT, we need professionals in charge of it, not nosy busybodies.
Read my other reply, I'm not talking about email blocklists, my reference is to email providers doing that, which is extremely rare and done with explicit intent and good reason.
Secondly, while I won't disagree there's some vile content out there on the Fediverse, do you trust someone else to make that decision for you? Why would you let someone else decide what is and isn't vile for you and those using your instance? Better yet, how would you feel if some popular instance decides you were the vile one, and because it was a common instance to use for blocking references, your instance is now cut off from a good chunk of the Fediverse?
This is exactly the sort of nonsense that swept Twitter with shared Blocklists, and the potential for negative impact on the Fediverse is even worse from it. Don't let others decide make decisions for you just because it's easy, as it doesn't absolve you of responsibility when something goes wrong.
Admins can and do use email server block lists, though, so maybe that's a great example.
I suppose you're right--for now. But at some point Lemmy etc will grow large enough to make manual blocking infeasible. Just how much effort does it take to start a new instance even today?
Wrong comparison. It's not like a server admin using an email block lists (which are also often implemented badly, as anyone with a protonmail account knows...). It's more like if Protonmail suddenly blocked Tutanota, or if Gmail blocked MS Exchange. The uproar and rage from that would be unceasing.
The Fediverse operates on a model like that of email, and in the email world blocking whole email servers from each other is very rare, and usually done with the most explicit of intent and for a very good reason. That's how the Fediverse should operate as well.
Obviously opinions are divided on shared blocklists, but we're at the beginning of the road and only time will tell how this impacts the fediverse. Email had to introduce blocklists as well, so it's not surprising this also exists.
I've never heard of an email operator refusing to send or deliver SMTP messages to/from a certain provider because too many of its users support the wrong political party.
I haven't heard of users or instances getting banned/blocked for supporting the wrong political party either unless racism, brigading, CP, and death threats are core tenets of said party, which leads me to believe you may be referring to the Republican party in the US?
There is a need for something like this. Lots of folks here are die-hard free speech defenders, which I completely understand, but some are starting to get into 'Freeze Peach' territory side of things. You can't expect every new Lemmy instance admin to manually research about this nazi instance or that pedo instance everytime, especially with self-hosted hobby projects. If there isn't anything like this, then admins might as well as start copypasting blocked instances lists from big servers like Lemmy.world or Beehaw.org, which again makes it even less coordinated.
There are plenty of potential for abuse as well. Eventually it has to have some kind of a public wiki where the reason for block can be consulted and have an appeal process with a 3rd party ruling to handle these things.
I disagree that defederation hurts Lemmy. It doesn’t hurt it anymore than normal moderation hurt Lemmy. Users on defederated instances are more than able to create an account on a non problematic instance and follow the rules there.
Defederation is essentially Lemmy’s version of quarantining subs on Reddit. And nobody except maybe extremists thought quarantine was a bad idea
You forgot people who selfhost single user instances. So they would have to destroy the old instance and create and new one with a new domain, which is a lot of work and resources.
Edit: Please also notice the problem here is not defederation itself, but shared lists of defederation. Because most likely the list is super long and nobody would check if all instances are legitimately blocked.
The problem is that Reddit has a massive user-base and profits from the FOMO on newcomers while Lemmy is a very small thing most people don't know about and there are multiple cases of instances defederating others just because they feel like it... like the BS that beehaw.org pulled. Now we've lemmy.world and beehaw.org two of the largest instances that don't talk to each other.
Defederation does hurt Lemmy when overdone, but sometimes it simply needs to happen to keep unmoderated instances from harassing your instance. Shared blocklists when properly managed simplify this process and improves Lemmy’s capability to protect it’s users from spam and brigading.
this process and improves Lemmy’s capability to protect it’s users from spam and brigading
That assumes defederation only happens in those cases. You have an account from lemmy.world, so I guess you trust that instance. You know, the same instance that preemptively defederated from hexbear.net for political reasons. You see the problem?
Seeing the number of down votes I may say that most people do not take smaller or single instance users that are too common. They are the ones that get most hurt with shared defederation lists. This only encourages people to gather to well known instance or accept being cut out from the biggest part of the fediverse.
Disagree, this tool is meant for use by small instance servers, not large ones. Large ones have to manually handle their list since they are on the hook more for maintaining some kind of policy and announcement structure.) The only way it hurts them as a little guy is if they break the policies of a major instance enough to get blocked by the instance admins, which would take some work for a small instance. (The same or greater amount of effort that would get you banned if you lived on the major instance so no benefit to making it your home there.) And then they only get blocked by that instance and the other small instances using this tool who chose to sync from that major instance. They remain fine on other large instances and small instance that sync from those other large instances instead.
If a large instance does start squashing little people excessively then hopefully that hits the feed and people can pick a different instance to sync from.