- cross-posted to:
- technology@beehaw.org
- fediverse@lemmy.world
- cross-posted to:
- technology@beehaw.org
- fediverse@lemmy.world
Server indexes of places for newcomers to join can be instrumental for Fediverse adoption. However, sudden rule changes can leave some admins feeling pressure to change policies in order to remain listed.
I cannot see anything bad here. Blocking an actively malicious actor should be the norm.
deleted by creator
predicted? they’re facebook, they are not predicted to be bad, they ARE bad.
lets learn from history and not be deer in the headlights
It’s often advantageous to prevent catastrophe before it occurs rather than clean up the mess once it happens.
Did you already forget the shit Facebook keeps doing? Repeatedly.
Why cover your nuts when you can just let somebody kick you there repeatedly?
Facebook has and it’s doing plenty bad. At this point, assuming this time they will be good is too much of wishful thinking.
Still I would let the instances decide. Seems a bit counter spirit to try to force them. Even as a user your can block them (there are two that a lot of users are blocking already…)
Its probably good to federate so that Threads users can leanr about alternatives and migrate to a better instance on the fediverse
Just to be clear, threads can federate with an instance that is not defeated with them, and in this case threads users can see all the Lemmy content, but not the other way around.
So this means that we can just keep posting anti Facebook content all the time and they will serve it to their users or will have to be blocking it.
The more I think about it, the worse it seems for threats to federate.
What’s the number of Threads users compared to Lemmy? If the number of Threads users greatly outweigh the number of Lemmy users, then we’d simply be drowned out by all the Threads posts. That’s part one of Embrace, Extend, Extinguish.
Extend adds functionality to Threads that Lemmy either can’t support or won’t support for a while due to development time. People migrate to Threads because Lemmy is “missing” functionality. Plus, though I’m not clear on the exact legal specifications, proprietary code can be added to open-source code, and the proprietary code would be copyrighted. In other words, Lemmy devs would have to figure out a way to interact with and mimic Threads’ proprietary code using open-source code.
Extinguish is when Threads’ support of Lemmy is eventually dropped. The users left on Lemmy have suddenly lost a huge amount of content, and they’re left with fewer users than before Threads enabled federation.
Right, so that means when someone on Threads is complaining about Threads, Lemmy users can’t chime-in and say “uhh, just register on here and thats not an issue, guy”
Well, meta plans to federate with at least some instances… Right? Else their users won’t be able to speak either.
cough
Haven’t done anything to the Fedivese yet.
“the mass murderer have killed multiple people in Spain and Italy, but we can’t just assume he will do the same thing in France”
Sure, but this is Mastodon, not murders. Much lower stakes.
if the stakes are so low then blocking them is as low-stakes as not, so why make a fuss about it?
deleted by creator
Oh? I missed where Meta had done bad things to previous Fediverses.
Like XMPP?
Not Meta.
Facebook allowed connecting with XMPP clients for a while and then cut off that access. While they were not the main offender compared to Google, they still did nothing but leech off the XMPP ecosystem until they decided it wasn’t in their interest any longer.
Well sure MS-13 may be a brutal trafficking gang known for extreme violence, but they haven’t done anything to ME yet.
I think this comment chain is going in a circle while everyone actually agrees with the underlying point.
It might be true that they aren’t ACTIVELY being malicious currently. It’s also true that they have a horrible history, and they will likely be actively malicious in the future.
(I say ‘might’ because I seem to recall them being malicious towards the fediverse with secret meetings with admins, but I didn’t follow up on that)
like this?
Wasn’t the original post amended to state it wasn’t intentional but rather a bug?
“bug”
So wasn’t Google when they killed XMPP.
like this?
Thought of this immediately as well
if only Facebook had started in 2004 and not 2024 we might have some historical evidence about how the company handles moderation or community safety or protecting user data or…
if only threads wasn’t launching literally today and we knew if they’d enthusiastically welcome hate accounts like Libs of Tiktok https://www.mediamatters.org/libs-tiktok/timeline-impact-libs-tiktok-told-through-educators-health-care-providers-librarians
The thing is, Meta does not care about community safety, or moderation, or protecting user data. (Fun fact: they don’t have a data protection agreement, but a data usage agreement.) All they care about is how they can get the most money out of something. Killing off things left and right of their path.
The question is not IF Meta kills the Fediverse but only WHEN they do it.
Ounce of prevention > pound of cure; or in Meta’s case, imperial fucktonne of cure.
It’s Facebook dude. To put it in Lemmy friendly terms, they’re not different entities in the way that Linux and Windows are. They’re different entities in the same way that Windows and Xbox are. It’s not technically the same thing but it’s the same people calling the shots. Expecting something different is only going to leave you disappointed.
I’m voting for Trump because he hasn’t done anything bad as a second term president.
They have done a lot of bad, not with threads, but with any other app. A wait and see approach to Facebook at this point is insanity.