this post was submitted on 11 May 2024
167 points (100.0% liked)
Technology
37717 readers
382 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What about users' copyright? Would Bright Data have to obtain permission from every user to scrap data while following copyright law?
I guess this wasn't a question raised during this lawsuit.
This is a guess since I'm not a lawyer, but since users license their content to Twitter when posting it, Bright Data might have to prove fair use. I don't think that question has been answered yet in relation to AI model training, but search engines have been doing this for decades for what it's worth, so I don't know.
This seems to have been addressed by the judge:
Users already relinquished their copyright rights when they signed the ToS.
Do they give up the copyright, or license it to the website? They still created the content, and I don't have a Twitter account, but after briefly reading the ToS, it says they license it to Twitter (which is pretty standard from the other services I use that I've read the ToS for).
Yep, you're right. I oversimplified it.
The same ToS which the judge says X cannot enforce because it conflicts with copyright law.
The copyright law says that Musk cannot claim copyright while also claiming not to be accountable. That has nothing to do with users waiving their copyright, which has been the standard practice for all forum software since practically forever. It's why prior to GDPR, their was nothing to motivate websites from deleting your posts and even that isn't about copyright, it's about privacy.
Copyright can only be waived in the US by dedicating the work to the Public Domain. In most other countries, it can only be assigned or licensed to someone.
The "standard practice in all forum software since practically forever", has been to include a very broad use license on the work, without switching the copyright holder, in order to protect the forum owner from liability.
The GDPR is about a very broad take on "privacy", where the rights of "access, modification, and removal" get extended to any "personal information", no matter whether it's "personally identifiable" or not.
Kind of a two birds with one stone situation.
MVP!