Seeing as this conversation is going on everywhere right now, what’s the approach to Meta going to be here on UK? Personally I’m all for defederation as soon as possible, what does everyone else think?
Say no to Meta! They inevitably will want to Embrace, Enhance, Extinguish!
I’m struggling to see the benefits of defederation. If we defederate from too many places, then users will make accounts to see what’s on new platforms. If there is a better experience on the other side, then they will abandon these instances. If you can see content from the new platforms already then that is less of a reason to abandon ship.
I’m not buying the Embrace, Extend, Extinguish argument. It’s more likely that we end up making ourselves irrelevant, than Meta somehow makes an open source protocol closed.
Philosophically, wasnt the idea behind an open protocol so that access remains open and is free from broad bans like this? Trying to keep people out en masse is not much different from having a Reddit-style walled garden to keep them in.
If we end up defederating from everything new and scary then why did we even leave Reddit?
The Mastodon developers have posted their thoughts on Threads.
They seem quite welcoming about the whole thing, as they have been advocating greater adoption of federation by the big social media firms. However, they mention XMPP and we’ve been burnt by them before - once bitten twice shy?
Interesting stance. I hope they are right. Maybe it is a win for open protocols. I just feel like federating with Facebook is like getting into bed with your drunk uncle who has a history of molesting people.
Worth noting that it is also a pretty controversial stance in some quarters? I appreciate the utopian/optimistic stance and, if you feel all social media should federate and give their users the option to move, then this development should be welcomed.
However, Meta is an all-consuming amoeba and you play nice with them at your peril.
I personally don’t see them as any different than any other large instance and should be treated precisely as such: default federate until they give reason to defederate with them, which should be based on concerns of content/moderation and the like.
Meta is a privacy-hostile company and for that reason I’d certainly not wish to sign up with their service. With that said, the only data they’d be seeing from other instances is what people put out there in the public domain anyway and nothing is stopping them from obtaining that data if they truly wanted it without having to create their own instance to do so.
With that said, I love the fact that individual instance admins have the choice to federate or not and that’s the beauty of the fediverse. There’s going to be some instances that defederate instantly and that’s okay, much like there is going to be instances who take an approach similar to what I think should happen. As a user, I’ll have the choice to use whichever instance suits my philosophy and that’s awesome.
Additionally, to be honest I don’t really think Threads federating is even that relevant for platforms like Lemmy. Threads is a microblogging platform and Lemmy is a link aggregation system. To even post to Lemmy in the first place, federated Threads users will have to explicitly go out of their way to direct their status posts to a Lemmy community. How many people on Threads are realistically going to do that? It’s awkward and most people wouldn’t even know there’s a wider “fediverse” being more used to centralized services like Meta. People already don’t do this particularly often from Mastodon instances which are federated.
The whole thing is a storm in a teacup as far as Lemmy is concerned. It’s a more relevant discussion for Mastodon instances, tbh.
Given the success of Threads, and Reddit’s current problems, I think there is a good chance that Meta are already working on a Reddit killer, based on ActivityPub. Threads membership could easily be extended to this new app, and all of a sudden there is a lemmy instance with 100 of millions of users, spewing forth all their unmoderated content to anything that is federated. The rest of the fediverse would be absolutely swamped. Gone will be lemmy as we know and love it.
My fear is that they’re going to go at it Chrome/IE style: Get big enough that their interpretation of the standards becomes the standard.
I guess we’ll have to wait and see.
I’m against it.
First, I fear it’s an attempt to embrace, extend, extinguish the fediverse, but I dont know what blocking Threads is going to do to stop that…
Second, I want Meta to have as little data on me as possible, so if they are storing my comments and profile data, I’m not happy. Call me crazy, but I worry what big data algorithms they have behind the scenes can do to tie things together.
Third, I’m huge advocate for digital privacy, and against these large social media companies. What demand in exchange for what they provide is massively unbalanced in my opinion. I dont want to support them by giving them content I havent actually agreed to give them!
Honestly, I see no upside to them federating, other than content that I’m not desperate for.
embrace, extend, extinguish
Ayyy this again. A catchy sound bite goes a long way on the internet I suppose? Never mind that the examples are a good twenty years old and the recent MS Linux one isn’t even correct. But that’s cool. It sounds edgy I suppose.
I’m not arguing for Meta (they can go fuck themselves) but give people the choice and they will choose wisely for themselves. Block Meta if you want, or don’t if you don’t want.
I don’t think that having a realistic concern that Meta may be using a well documented business tactic that is used to snuff out competitors, to snuff out a competitor.
Embrace, extend, extinguish is associated with MS, but they’re not the only company to use.
I think many will see Meta entering the fediverse space as a threat to something nice that’s separate from corporate greed.
The problem with using that term is that people often have zero evidence of it and zero evidence ever materialises. Just because it might have been a business practice in the past doesn’t mean that it is now. You don’t go around saying oh you’re Belgian and they did shitty stuff in the past so you must be a rabid colonialist. The two just don’t follow.
I think many will see Meta entering the fediverse space as a threat to something nice that’s separate from corporate greed.
Many will. Many will not. Surely the beauty of federation is that you can choose? If it’s not possible now I would love to see a user option to block specific instances. Then users can block Meta if they wish and live happily in the gardens of their own making. Or if they don’t then they can still see federated content from Meta users.
Out of interest, does blocking go both ways? If I block Meta, I can’t see their content, but can they still see mine?
If they can, blocking does nothing to prevent them harvesting data on me does it?
As I understand it they can’t see anything from communities that don’t federate with them, but they can see your activity on communities that do. So if you don’t want them to have any data on you, you’d have to be careful to only interact with content on instances that block federation with Meta.
That said they could scrape content from instances that don’t federate with them but I think that would be legally sketchy since holding that data could violate GDPR and reposting it could be considered copyright infringement.
I’m not sure there’s much of a legal framework for feddiverse content since it’s relatively small and non-profit AFAIK. I think it would make sense for instances to have clear terms of use. They could state that you licence them to serve up your content and send it to federated instances, but not allow them to monetise it beyond raising reasonable hosting and development fees.
Thanks for the explanation, that’s really helpful.
Most of the conversations Ive seen around this are about giving the user more tools to curate their experience by being able to block at an instance level. But as you say, that doesn’t stop predatory instances scraping your data anyway, neither does defederating really.
The fact seems to be that if Meta (or chat GPT for that matter) want your data, you can’t really stop them. However, your point about the whole licensing angle is really interesting, I wonder if there’s a solution somewhere involving licensing your own content?
Feels kind of weird to think about but what would happen if your account had its own unique creative commons license? I guess the issue would be proving your data was stolen, but if literally everyone on the fediverse did it, any indication of fediverse related data being used by someone like meta could incur some kind of legal action?
Dunno, I don’t know anything about how licensing works.
Dunno, I don’t know anything about how licensing works.
Yeah, same.
This is the way Wikipedia works though. Everything contributed there is automatically CC-BY-SA and GFDL (bar some older stuff). https://en.m.wikipedia.org/wiki/Wikipedia:Copyrights
I think an instance could have that as part of its sign-up and community rules; that the content submitted is CC-NC licensed. Anyone using that data for a commercial purpose would be infringing our copyright since they are not complying with the license terms.
