Found this post super informative as it relates to Mastodon, and thought Lemmy might also benefit from this perspective. I’m not sure I share his optimism, but his points seem sound to dampen some of the alarm bells over Meta joining the Fediverse.
You must log in or # to comment.
I think E/E/E is still a risk. If some “high follower” type people start joining Threads, and people on Mastodon start following them and making that content a big part of their feed, those people are not going to be happy if Threads accounts suddenly disappear because Meta make arbitrary, incompatible changes.
Hopefully it won’t actually extinguish Mastodon/the Fediverse, but it can still do damage.
Meta is a socially transmitted disease. There’s no reason to “wait and see” with Meta, we already know them. Meta is not new, it’s Facebook, with a new name and a fancy new logo to deflect attention away from all the terrible shit they do and have done, to individuals, groups, communities, and society as a whole.
So much terrible shit that unlike many Wikipedia articles that have a “controversy” section, Meta/Facebook has entire pages devoted to their terrible shit.
https://en.wikipedia.org/wiki/Criticism_of_Facebook
https://en.wikipedia.org/wiki/Facebook_content_management_controversies
https://en.wikipedia.org/wiki/Facebook_emotional_manipulation_experiment
https://en.wikipedia.org/wiki/Facebook–Cambridge_Analytica_data_scandal
There’s more. Meta is not some new and exciting player in the ActivityPub field. They’re a known quantity, and there’s nothing to gained by allowing them to flood the Fediverse with low-quality shitposts at best, massive social manipulation campaigns at worst, and everything in between. In my humble opinion.
I’m no fan of Meta or their practices, to be clear. Though I do think there are potential benefits in having the ability to communicate cross-platform, so long as some reasonable safeguards are put into place. I’m firmly in the camp that doesn’t believe that Google killed XMPP because XMPP was never a popular or widespread protocol prior to GTalk, and the users who came and went when Google did what they did were Google users, rather than XMPP users. So much like Eugen here says, it went back to how it was before they got involved.
That said, I do think that Meta in its current incarnation is an entirely different animal. I suspect that early on in a post-federated world, we’ll start seeing dark patterns intended to lure users to Threads. I’m envisioning registration gates similar to paywalls on news sites. “This content is available exclusively on Threads! Click here to register your account!” type stuff. More sinister, there’s nothing to stop Meta from appending advertisements in the body of posts created on Threads. Hell - they could go full evil genius and suppress that they’re doing it entirely on their own platform since they’ll have some other ad delivery mechanism there, which would mean the only people being served those ads would be federated users OFF of Threads who see or interact with content created on Threads.
So while I’m not a doomsayer about Threads and federation, I do think that we as a community are going to have to make some decisions about how to handle them. Having access to a community the scale that Meta will produce isn’t necessarily a bad thing. And because of how Lemmy / Mastodon / KBin / Fediverse apps work, we as users will always have the ability to control what we see in our feeds. At worst, it makes /All/ less usable, which is admittedly quite a big loss given how useful it has been to get subscribed to worthwhile content since joining Lemmy. And obviously, some instances will elect not to federate with Threads at all, which gives users choice on the type of community and content they want to interact with regularly.
With some care, likely some effort around defining usage rights for user generated content, and some new content control / filtering capabilities yet to be developed, I think that these networks can coexist in a way that is mutually beneficial to a degree, but if not - defederation is a click away.
EEE, Embrace, Extend, Extinguish. Meta may very well be embracing federation concepts to eventually return back to their former selves.
As has been mentioned before, Meta can scrape most data from the Fediverse already as it is publicly available.
One strategy could be to default to publish to followers only, and not public? It would be a great loss for the open web, but it might be a necessary one to make sure blocked instances do not get access to most of our data.
Another solution could be to publish all posts under a Non-Commercial Creative Commons 4.0 license, which I assume would legally block Meta from using our content in any context as they earn piles of cash on mixing user generated content with ads. Not sure if they would respect it, but it might give us an option for a class lawsuite in the EU?
Actually the copyright option might be the best one. Theoretically speaking the instance would need to state that all work is licensed only and that every comment and post has the copyright retained to creator/OP.
It’s just a simple tweak of the terms of service, but that would be enough to do it. Getting them to respect it is another ball game, because as we’ve seen with Midjourney and other photo apps, they have clearly scraped photos with watermarks that they didn’t have access to, and have used them to both train their models, and in the final output. This is why there was discussion of a class action lawsuit, although I didn’t hear where that ended up going.
I’m hoping that this happens irrespective of other steps that may need to be taken with respect to Meta or other corporate interests in the Fediverse. Since the data is all completely public, it would help clarify “ownership” of original content, allow for meme culture and virality to continue to occur, but still give some avenue for people to raise claims against these large entities.
Someone is eventually going to try to marry a blockchain to this tech so that there’s an infinite record of content with receipts to the beginning. Privacy concerns all over the place, but it seems like such a natural extension to the already completely public nature of the content being generated throughout the fediverse.
I feel like he’s out of touch. There are many concerns: our data; embrace, extend, extinguish; and lastly, our communities. Meta has already proven in the past few hours that threads are not different from anything else when corpos drop. Within a few hours, accounts like Libs of TikTok, Gay Against Groomers, and other LGBT harassment accounts joined and are still active. Is this what we really want federating with us?
I don’t know the others you mentioned, but how is libs of tik tok a ‘harassment’ account?
Are you fucking serious? Do you genuinely not know who Chaya Raichik is? Because if you’re acting in good faith and actually aren’t aware of the vile hatred and harassment orchestrated at her hands, you really need to drop her name in the old Google machine and do some reading.
How is the account harassment? How does the account harass people?
I don’t really care what kind of a person anyone is, the question is how the account harasses lgb people
The account is specifically for mocking people, thus the name. They take someone to direct their hate at and that translates to real harassment. It’s built to hurt people, especially LGBT people. Groups built on “destroying the woke mind virus” are a scourge to humanity.
Sounds like mastodon doesn’t mind lying with vipers and is trying to justify it
Lol are you serious? What, did you want a little bubble on the internet where corporations don’t exist? What does “open source” mean to you, open to only the entities you allow in? Like the article says, join an instance that defederates every corporate entity or make your own, but don’t blame developers of open source software for keeping it open.
I’d like to not embrace the assholes that helped centralize and control the narrative on their massive platforms of idiot users
It’s not embracing Meta. All it says is, once it is federated, they may be interoperable. That’s it. You could view stuff on Threads and Threads users could view stuff elsewhere (unless your instance defederates from Threads).
