Yep, this list is automatically updated and the page exists on every lemmy instance – the software installs it by default. Now that I blocked this instance you will see the page updated automatically with it in the blocklist.
Defederating, or the blocklist, is unilateral. We only block instances that do nothing against spam or are fascist. Don’t have any other reason to block tbh.
Since beehaw blocks us, we and they won’t see each other’s content, but we can still meet in “neutral ground”, i.e. third-party instances that we both federate with. I’m not entirely sure if it works different, I think if one instance puts you in the blocklist it’s enough that you will never see each other.
The reason they block us is because they are anticommunist 🤐 They thought, when they set up beehaw, that we took up too much space on their server and that was one reason given for not federating. Then they found out it was a bug with log files (lemmygrad doesn’t take 80 gigs of space lol).
Now I’m also seeing a lot of overlap between beehaw, sopuli and perthchat (possibly other instances as well, such as midwest.social and mander.xyz) – they share mods and users. If I didn’t know any better I’d say they’re concerting with each other to form a bloc of sorts. But that’s also just the nature of federation.
Did lemmy.ca also defederate from us or are they just inactive? I sort of thought I’d start seeing more klanada-centric stuff when they first announced they made that instance.
According to their instances list: https://lemmy.ca/instances, we are one of three instances they block 🤣 (one is wolfballs, the other is a Breton-language instance of all things to block).
One more question if you don’t mind, do you guys get notified when an instance in our link list blocks us, or is it just…they’re there one day and gone the next and you’re just as surprised?
I think it’s the latter. I’ve never got a message or anything.
Documentation is lacking on lemmy so most of the stuff I learn through trial and error x) for example, I have no idea why I’m discovering instances that we should federate with (federation is enabled by a checkbox) but don’t.
Not true, federation blocklists are essentially one-way. Beehaw has you blocked, so they wont see any content from lemmygrad. But lemmygrad doesnt have beehaw blocked, so its content is shown here. Admins should consider blocking these instances to hide the content.
You were right to not think of it. What happens is that if two instances can federate, they do not begin federating on their own. Searching the URL or a user on the other instance (eg. @someusername@someinstance.com) the federation process and the backend starts pulling all the info it needs to be able to display content from that instance.
I think one instance’s linked list does not have to match with another’s blocked list
So we can allow beehaw, and they can ban us, and that means there’s no federation
deleted by creator
Yep, this list is automatically updated and the page exists on every lemmy instance – the software installs it by default. Now that I blocked this instance you will see the page updated automatically with it in the blocklist.
Defederating, or the blocklist, is unilateral. We only block instances that do nothing against spam or are fascist. Don’t have any other reason to block tbh.
Since beehaw blocks us, we and they won’t see each other’s content, but we can still meet in “neutral ground”, i.e. third-party instances that we both federate with. I’m not entirely sure if it works different, I think if one instance puts you in the blocklist it’s enough that you will never see each other.
The reason they block us is because they are anticommunist 🤐 They thought, when they set up beehaw, that we took up too much space on their server and that was one reason given for not federating. Then they found out it was a bug with log files (lemmygrad doesn’t take 80 gigs of space lol).
Now I’m also seeing a lot of overlap between beehaw, sopuli and perthchat (possibly other instances as well, such as midwest.social and mander.xyz) – they share mods and users. If I didn’t know any better I’d say they’re concerting with each other to form a bloc of sorts. But that’s also just the nature of federation.
Oh, the log files got them. I’ve had many stories of multi-gigabyte-large log files breaking stuff on my servers.
deleted by creator
According to their instances list: https://lemmy.ca/instances, we are one of three instances they block 🤣 (one is wolfballs, the other is a Breton-language instance of all things to block).
I think it’s the latter. I’ve never got a message or anything.
Documentation is lacking on lemmy so most of the stuff I learn through trial and error x) for example, I have no idea why I’m discovering instances that we should federate with (federation is enabled by a checkbox) but don’t.
deleted by creator
Yeah, szmer.info anarkids are on the list but lemmygrad.ml is on their blocklist. Also, coincidentally, they also federate with sopuli and beehaw
Not true, federation blocklists are essentially one-way. Beehaw has you blocked, so they wont see any content from lemmygrad. But lemmygrad doesnt have beehaw blocked, so its content is shown here. Admins should consider blocking these instances to hide the content.
deleted by creator
Oooh okay I get it now.
If you type one of beehaw’s post URL on the lemmygrad search bar, you will be able to access it. Example:
https://lemmygrad.ml/post/383684?scrollToComments=true
And you can see I was able to post a comment there.
But if you look at the post on beehaw : https://beehaw.org/post/131299?scrollToComments=true
My comment doesn’t show up there, it hasn’t been federated.
We can’t see scores or their comments either, it’s essentially just a list of posts
lmao they deleted the post as well 🤔
deleted by creator
You were right to not think of it. What happens is that if two instances can federate, they do not begin federating on their own. Searching the URL or a user on the other instance (eg. @someusername@someinstance.com) the federation process and the backend starts pulling all the info it needs to be able to display content from that instance.