this post was submitted on 23 Oct 2023
70 points (100.0% liked)
Technology
37727 readers
671 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
The DMCA is so fucking contradictory about these subjects too. For example, per the DMCA, a party that misrepresents themselves in a takedown claim:
This should mean you can sue the person for absolutely every bit of damage you suffered + whatever legal costs you encouraged in the process when you are delivered an illegitimate takedown. Reality is though, when regulatory duty is foisted onto private actors like this, that's just making it harder to get access to your rights.
The DMCA limits liability for platforms that host infringing content so long as the platform does not have knowledge the content infringes... but it provides NO guidance for how the platform should ascertain that an infringement claim is legitimate -- and waives their liability for making an erroneous determination.
It mandates a counter-notification process, but in this process the content will stay down for 10-14 days -- which in the world of social media can be an absolute death sentence. In no small part because the service provider's own algorithms will now bury that content when it is restored. And of course, DMCA has zilcho recourse for algorithmic burying (of course the writers weren't even aware of these potential effects).
And you cannot have an anonymous of pseudonymous counter-notification. Must be your full name, address, and phone number on it. Which will theoretically get handed off to the person that put in the fake claim against you as part of the process! Fucking madness! I don't know if this is enforced as written, but as written this is what it says.
There's probably a lot more to be said, but christ it is a poorly written law. And this is all from Section 512, which is often viewed as the only "good part" of the DMCA.
This isn't remotely true. You contest the claim by submitting information through the host and basically telling the complaintant to sue you or go away. There's no obligation for the host to do this, though; they're free to just take your content down because of course they are.
DMCA takedown notices protect server hosts from copyright lawsuits.
What are you claiming is untrue about what I said? The part where I directly quoted the statute, or something else? Fuck off with this "not remotely true" bullshit.
I mentioned the counter notification process. Extensively. It's a bad process.
There IS an obligation for the host to do something with the counter-notification, by the way. Their liability waiver for damages goes away if they do not participate in the process. But same as other parts, it puts the legal onus on the victim, meaning little guys get fucked.