A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)
I can understand defederating from Threads, but transitive defederation is bordering on insanity.
This will do nothing but exert peer pressure onto instances that wish to remain impartial. Transitive defederation will play right into Meta's hands by fragmenting the Fediverse further.
“You’re either with us or you’re against us”
— level-headed, fair-acting groups of people throughout history
Only a sith deals in absolutes.
Yeah, strong arming instances to do something or another based on a personal preference I thought was meta's job, not the fediverses.
The entire point is that each instance should decide for themselves. If they want to defederate with me because I haven't made up my mind yet, then so long I guess, to me that says more about them then it does Meta.
As long as Meta can't infect the rest of the fediverse, or track or monetize it...fine. I just never, ever want Meta shit on my timeline.
How would Meta “infect” anything? Do you really think Meta is producing self-replicating things that jump from person to person?
I understand the argument for servers blocking Threads/Meta. It doesn't strike me as the right choice for every server, but it's clearly a good choice for some servers. Threads doesn't moderate the way many fediverse servers would like their peers to, and Meta is generally an ill-behaved company. Blocking it is appropriate for servers emphasizing protection for vulnerable users, and inappropriate for servers trying to be big and open. The fediverse is great because people can choose what's right for them.
I do not, however understand the argument for blocking servers that do not block Threads and I think the article could be improved with a more thorough explanation. Maybe there's something I'm missing about the mechanics at work here, but isn't one's own server blocking Threads enough to keep Threads users from being able to interact?
I'll be honest, if this gets adopted I'm out.
Most of these ideas are ridiculous in how they desperately build up windmills to handle a surplus of lances among some fediverse users, but this genuinely applies the very thing you - completely out of nowhere - assume Meta would do to what you're doing: EEE.
You're trying to strong-arm users of AP into your modified version usage guidelines for it entirely to suffocate anyone disagreeing.
That's despicable, even as just an idea.
The good news is that none of the large instances are going for these insane policies. Small instances and solo instances can defederate themselves into irrelevance all they want, just like beehaw did.
exactly, they don't even have a definitive roadmap yet. most of the instances would block threads anyway if they ever make a decision that could EEE fediverse. blocking instances that federate with threads is kind of a bad move.
Splitting the fediverse in half just to get back at Meta is an awful idea.
Plus it wouldn't "get back at" Meta anyways. If their goal is to prevent or defend against some sort of EEE approach (nevermind how little indication their is that that is Meta's motivation for federating), then splitting the target into two smaller groups is perfect. They can easily do something about the one half, then claim that in addition to them, one of the two big camps of the fediverse already supports their new Meta-led protocol, in turn claiming the other half is silly for refusing to adhere to standards.
As in: Don't split the standard into two that are then easier to de-standardize if you are interested in standards.
For instances which choose to intentionally mirror or otherwise make available threads content on instances which defederated threats, instances which know about and are deliberately circumventing the fediblock on those other instances it does indeed make sense though. Keep in mind when I talk about it I'm specifically talking about instances who are intentionally trying to circumvent the fediblocks by a coordinated effort, not just that they federate with threads.
no thanks. no need to technology a kneejerk reaction to nonexistent problem.
I don’t know. Calling Meta a nonexistent problem sounds naive to me. Sure, something “hasn’t happened (yet)”. Except, it’s Meta … plenty has happened already. How many times are we going to allow selves to be fooled?
im not going to get into this, again, as im sick of asking the same thing and no one ever having a valid response so ill just state it.
theres no technical reason to think meta can overtake the ap protocol and substantially alter it in any appreciable way. that they have a federating server in threads is not some crazy threat unless your own shit becomes dependent on that federation. if it does, its on the instance owner not threads.
as it is, there is zero reason to not federate with threads other than substantial resource use (flooding) and righteous indignation.
i run a public instance, and as soon as threads interferes with it, i will nip that shit in the bud. until then, i plan on providing an offramp for those trapped in metas walled garden.
I don't federate with any instance that openly houses hate groups. Threads houses hate groups.
There's a reason for you.
It may not be enough of a reason for you, but that's a whole different thing to there being "zero reason not to federate"
you got the righteous indignation part down pat.
its work to block instances. im not going to operate like that. im treating AP like email. i dont block facebooks SMTP, i dont block Nestle email.. im not going to block their AP.
i am providing assistance to humans wanting to leave the walled garden. you are not capable of that, apparently.
but you do you. thats what its all about.
edit: btw none of this is technical in nature. its just political. i stand by the fact there is no technical reason to not federate.
The fact that you equate vulnerable communities blocking instances that house hate movements that target them with righteous indignation is genuinely scary...
I’m not sure I understand your issue with the term here. “Righteous indignation” word for word means “indignation that’s justified”, so I don’t want to jump to conclusions, and I’m thinking I may be having yet another of my English second language speaker moments.
Indignation implies that it's about being offended or upset.
The specific term you used usually carries an implication of pettiness, and of making a big deal out of nothing. The "righteous" part is normally meant in an ironic or sarcastic way.
I’m not the same person you were initially talking to. I’m not sure calling it indignation is necessarily dismissive - indignation can perfectly be justified. I’m really surprised it carries this subtext. I can’t seem to find any reference or definifion supporting neither this nor the expression itself though, but I may be looking in the wrong place…
I think it's another one of those things where words and phrases change meaning over time.
Righteous is equal to justifiable. Indignant is equal to showing anger.
Logically, it should mean justifiably angry. Often times, people will just ignore and skip over the first word and will only properly read "indignant".
I think it's similar to when people say words like "irregardless". They use it to mean "regardless". If you break the word down, the double negative makes it a positive. It looks like it should read as being the same as "regarding", but people had other ideas lol
Another fun one: "eggcorn" has been added to some dictionaries as a synonym for "acorn".
What can a hate group do when Meta’s federated to an instance with vulnerable people in it, that they can’t do when Meta’s not federated with that instance?
Yeah people never explain that. As if people get stopped by this. It just makes the tech behind the federation actually useless just for some imaginary hypothetical threat that it wouldn't stop anyways!
righteous indignation
This is minimising a problem you'd rather not think about or address "too much". For many it's a real problem, both morally or in the abstract, and practically.
Here's a good article outlining an "anti-threads" position (https://erinkissane.com/untangling-threads) that may answer both the "righteous indignation" point and some of your "technical" points too.
All of which gets to arguing that, yes, as my initial reply to you stated, there are "existent" problems and preemptively acting can make sense.
You want to be an off-ramp, and have your finger on the defed button ... that's cool (genuinely)! But dismissing urgency as illogical or something is, I think, out of line.
Your arguments strike me as either dismissive ("zero reason ... righteous indignation"), straw man ("resource use", "overtake the ap protocol") or excuses, frankly ("It's work to block instances" ... threads is like one instance).
eg, how sure are you that flow of users between the fedi and Threads will be net positive for the fedi ... how do you know Threads won't actually end up sucking up users from the fedi? How convinced are you that they won't bend the de facto standard usage of the protocol (where mastodon is already doing this) to their own ends and then reform what the "big mainstream" idea of the fediverse actually means to most people?
Sure, something “hasn’t happened (yet)”.
Pretty much the definition of a nonexistent problem.
I swear to god the conversation around Meta joining the fediverse has been one of the most annoying things I've had to read about in a while.
We should defederate with any server that has less than 7 degrees of separation with Meta. We can call it the Kevin Bacon rule.
I just went ahead and defederated with my own brain. This way I never have to worry about Meta sludge ruining my life by existing on my screen.
I mean if it is really transitive then we should defederate with any server that can be connected to Meta with a finite length path
Eh, nah, not as a preemptive thing. If threads users become a problem, then transitive defed is a good option. Otherwise it just makes the whole thing more annoying than it's worth.
Meta disgusts me but i cant lie and say the opportunity that my family may without me pushing much may join the fediverse on threads sounds much nicer then the status quo.
I am all for protecting the fediverse from metas ideas so i do support defediration.
With this transistive tool what happens if i am on my own instance, defederated from meta but i dont the transition and federate with a community that is federated with meta.
Could i see threads from my instance trough the federated one?
Is my own instance safe from meta?
Will transistive defederation mean others will automatically defederate with my instance because i federate with an instance that is federated with threads?
Man just gotta respond to one thing here. I’m not for protecting anyone from any ideas. Better to have an immune system than a sterile environment that requires isolation to maintain.
Lack of isolation online played a big part in my deconverting from Christianity.
These goobers on Mastodon content warning a fucking dog looking at you or, heaven forbid, a plate of food, cracks me up.
How do they function day to day? Grow up.
also blocking any instance that federates with an instance hosting harassers and hate groups – provides even stronger protection.
Even safer, unplug your router.
Y’all notice that things always talk about “user safety” and such but never detail just how the NAZIS at Threads will continue to interact with their users when the whole-ass domain is blocked.
This is just another purity test.
Nonsense
We really need better visualization tools for who is federated with what. Meta is just one large / recognizable company to pop into the fediverse. Others will move in over time, and if instances choose to do something like this (defed from any instance that didn't also defed), then it's going to be a complete mess trying to figure out who is federated with what. Those smaller defederated instances will need to be extra clear about who they are federated with and why, otherwise people will avoid them.
I personally think this is a bad choice to make, but instances are free to do as they please.
I honestly don’t know what my mastodon instance’s take on blocking threads is but I probably will be blocking them on the account level. Blocking servers transitively because they don’t defederate with meta seems like it is unnecessarily siloing servers into a second “free” fediverse. If a server is moderating their accounts in accordance to the written policy then if they choose to federate with meta, it doesn’t feel like it’s any of my business.
While my primary masto is a single user instance, basically anywhere else I exist on the fedi is a subset of infosec dot *.
Those instances are all run by someone who a) is cool with spinning up a whole bunch of instances, b) is willing to risk the costs, and c) is excellent at delineating policy. There’s a “no fucking threads full stop” instance, and a “no threads by default, but user can flip switch” instance, for example.
That’s a method of operation that works from my pov but doesn’t suit everyone’s needs. Personally, I want nothing to do with threads but am more able to express my anti corp tendencies than I was in my twenties, and I’m more willing to accept that “it’s just bandwidth, find the instance that meets your needs.”
My needs involve no threads at all, but I can accomplish that with a very small amount of effort given. My circles.