I think we can give facebook/threads the bad end of the bargin IF we have a data protections.
You know how powerful copy-left was for open source? I think we can do the same for Lemmy servers. We can have users agree (formally) that the data on a particular server cannot be used for training llvm’s advertisements, marketing profiles, etc, and make it legally binding.
Even if we don’t federate with them, Meta can still harvest the data so we should add these protections regardless. Maybe there is already something like this and I’m just unaware of it.
If we do add these protections and we ensure that the largest instance (e.g. Lemmy.world) is community controlled, I think it could work well for bringing more content to Lemmy.
Yep, on a public forum like this we lose very little on privacy by federating with them. What we do stand to lose is comment and post quality, but that’s trivial to fix by simply blocking threads on a personal level.
It’s not fair game for for-profit bussinesses training LLM’s. That’s part of why Reddit made the move; so that companies would need to pay Reddit for access to the data for legally training models
They changed the terms and made the API pay to use for large volumes of use. People using it to train models have already pillaged what they need and you can get the data prior to APIgeddon elsewhere.
I think this is the wrong take. If we want Lemmy to be truly community-controlled, we need many small servers, as opposed to the current situation of one server controlling half the userbase. Also, which server is Facebook-controlled? Lemmy.world is in the minority by federating with Threads.
I think we can give facebook/threads the bad end of the bargin IF we have a data protections.
You know how powerful copy-left was for open source? I think we can do the same for Lemmy servers. We can have users agree (formally) that the data on a particular server cannot be used for training llvm’s advertisements, marketing profiles, etc, and make it legally binding.
Even if we don’t federate with them, Meta can still harvest the data so we should add these protections regardless. Maybe there is already something like this and I’m just unaware of it.
If we do add these protections and we ensure that the largest instance (e.g. Lemmy.world) is community controlled, I think it could work well for bringing more content to Lemmy.
Yep, on a public forum like this we lose very little on privacy by federating with them. What we do stand to lose is comment and post quality, but that’s trivial to fix by simply blocking threads on a personal level.
You can scrape Lemmy instances for training data without even running an instance.
Yeah, sorry if I’m not great at communicating. That’s exactly what I’m trying to point out when I said:
That’s the thing, anything public is fair game. This is why Reddit is ruining their API.
It’s not fair game for for-profit bussinesses training LLM’s. That’s part of why Reddit made the move; so that companies would need to pay Reddit for access to the data for legally training models
They changed the terms and made the API pay to use for large volumes of use. People using it to train models have already pillaged what they need and you can get the data prior to APIgeddon elsewhere.
What does lemmy.world being the biggest have to do with any of this?
As opposed to a facebook-controlled server being the top search result for Lemmy.
I see why that’s confusing so I edited my comment just now
I think this is the wrong take. If we want Lemmy to be truly community-controlled, we need many small servers, as opposed to the current situation of one server controlling half the userbase. Also, which server is Facebook-controlled? Lemmy.world is in the minority by federating with Threads.