Locking post as comments are getting off topic and are not following the rules of the community.
this post was submitted on 06 Jul 2023
617 points (98.1% liked)
Fediverse
28528 readers
667 users here now
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 [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 2 years ago
MODERATORS
They didn't even address what will happen when Facebook starts aggregating data from instances federated with Threads:
- Vote/Like data
- Follow relationships
- Text sentiment analysis
- Behavioral patterns
- Periods of activity
- etc
Heck, not only did this post not address it, it seems like they tried to downplay it.
Facebook is an analytics company. Even if it's not mission critical to the function of Threads, they will scoop up data sent to Threads, they will use it to create profiles on every single non-Threads user they can, and they will sell that data.
It doesn't even matter if it violates privacy laws; the laws are toothless to companies as large as Facebook. They'll just be made to pay a fine and carry on as they are.
Yes, interoperability would be a win, but not when it comes from a company that has routinely demonstrated they abuse every crumb of data they can get their hands on.
What should happen? That's all public information, they can (and probably do) scrape this already. As does all and any AI project and company.
But it's probably not legal for them to sell it. The fact that they've tricked us into thinking this is normal is part of the problem.
load more comments
(8 replies)
I've posted this elsewhere in the thread so hopefully it doesn't feel spammy, but this is from their privacy policy:
"Information From Third Party Services and Users: We collect information about the Third Party Services and Third Party Users who interact with Threads. If you interact with Threads through a Third Party Service (such as by following Threads users, interacting with Threads content, or by allowing Threads users to follow you or interact with your content), we collect information about your third-party account and profile (such as your username, profile picture, IP address, and the name of the Third Party Service on which you are registered), your content (such as when you allow Threads users to follow, like, reshare, or have mentions in your posts), and your interactions (such as when you follow, like, reshare, or have mentions in Threads posts).
We use the information we collect for Threads for the purposes described in the Meta Privacy Policy, including to provide, personalize, and improve Threads and other Meta Products (including seamless personalization of your experience across Threads and Instagram), to provide measurement, analytics and other business services (including ads), to promote safety, integrity and security, to communicate with you, and to research and innovate for social good."
https://help.instagram.com/515230437301944?helpref=faq_content
to research and innovate for social good.
Oh fucking please. What a total absolute load of rat shit, my dear fucking lord.
Simple enough, based on their TOS we just block their instance and they can no longer create a profile/scrape our data. Anyone know how to go about that? If so, lemmy know
load more comments
(1 replies)
load more comments
(4 replies)
Isn't all of that already available to Meta (and anyone else) via the web UI anyway? They don't need to be federated for that, they can just use a web crawler. And I assume they are.
Frankly, there are other instances out there that I'm more worried about than Threads.
Why use a crawler if you could spin up some camoflaged small instances and get the info right via the regular api?
Or create accounts and get the info from the client api like apps?
load more comments
(1 replies)
I'm not sure about Mastodon, but at least for Lemmy, not every piece of information is available from the API or web interface. Some of it is only sent through federation. Namely, who, specifically, voted for something, edit history, probably a few other things.
Does Mastodon just hand over a complete list of everyone who liked a post? Even if it has thousands of likes? That kind of data would be very valuable to a company like Facebook.
load more comments
(7 replies)
Stop giving big corpo any more chance at 3E saying "no this time it'd be different" no the outcome is the same every time.
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%E2%80%93Cambridge_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.
EEE, Embrace, Extend, Extinguish. Meta may very well be embracing federation concepts to eventually return back to their former selves.
load more comments
(1 replies)
Generally well reasoned and interesting, but, the only thing that defends against EEE is
ActivityPub enjoys the support and brand recognition of Mastodon.
Ima guess that Meta's support and brand recognition dwarfs Mastodon's, not re-assuring and rather self absorbed imo.
Ima guess that Meta’s support and brand recognition dwarfs Mastodon’s, not re-assuring and rather self absorbed imo.
Yeaaah, when I read this I was just like, "Have you been outside of Mastodon lately? The brand's not so great to those folks that have heard of it in context." Nearly every time I've seen Mastodon come up outside of Mastodon, it's to complain about it being confusing or only used by tech nerds and there's nobody worth following there.
And I personally like Mastodon, but there's no denying the brand's not reputable to many folks, and it's probably still relatively unfamiliar/unknown to a majority of folks that don't closely follow social media stuff.
load more comments
(1 replies)
Calling Eugene Mastodon's CEO is kind of a threat. Granted he is Mastodon GHmb's CEO, but by no means is that what most people think of as mastodon. Then again he's let the #twittermigration go to his head.
Thankfully I haven't seen this, yet, from the lemmy.ml guys, the fact that lemmy.world is already bigger probably helps that too. (Well that ant they, allegedly, anti-capitalists).
I’m admittedly unfamiliar with Eugene, so was using the title listed in the blog post.
He was talking to Meta before they announced Threads and he signed an NDA. I strongly agree with @[email protected]'s opinion that the recent popularity Mastodon has enjoyed has gone to his head.
Put plainly, I don't trust him at all.
You don't have to. He might have developed Mastodon but it's all open source, and he certainly doesn't "own" ActivityPub.
load more comments
(1 replies)
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.
load more comments
(1 replies)
load more comments
(3 replies)
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?
load more comments
(6 replies)
I'm preemptively defederating from Threads. But I'm not necessarily opposed to refederating in the future, if Meta proves benevolent. Some bigger Mastodon admins are going with a wait and see approach, but as the sole admin of a small instance, I'd rather not have to rush to defederate if shit hits the fan.
load more comments
(3 replies)
It’s very… basic. One timeline, can’t filter anything out… ton of garbage. No thanks. Holy shit it’s bad.
And half of the feed is people talking about how addicted they already are.
load more comments
(1 replies)
load more comments
(2 replies)
Our software is built on the reasonable assumption that third party servers cannot be trusted. For example, we cache and reprocess images and videos for you to view, so that the originating server cannot get your IP address, browser name, or time of access.
I hope Lemmy also implements the image/media caching in the not so distant future. Currently, Lemmy Web UI sends a lot of HTTP requests to external servers like imgur. (Github Issue)
Threads being federated fascinates me. In one hand, it ends up being a gateway to mastodon / Lemmy for some. People who grumble about how “evil” Twitter / Facebook is but use it anyhow because “that’s where everyone is” may at least have their toes dipped into those concept and some of that may now see leaving as a viable option to something that isn’t evil as long as they can still see that content. It’s still seems to early to tell.
load more comments
(2 replies)
I didn’t know you could move Mastodon servers and retain your followers. Very cool.
Nice to see a balanced opinion, this whole facebook/meta discussion has been pretty virulent at times
view more: next ›