29

I've encountered this on Anime and Manga SE over a year ago, but figured that we haven't had a follow-up on that in a while, and it applies to more sites than just that one.

Content on the network can be removed with a DMCA request. It is no longer the case that Stack Overflow uploads these to the Lumen Database, so we do not have as much insight into what the infringed content was (for those of us who cannot see deleted posts).

Additionally, there doesn't seem to be any clean recourse for us to report or contest seemingly bogus take-down requests. One such post identified in a DMCA request targeted at Anime and Manga SE was this post, and in spite of it not having any media, I recall that it was deleted for a short period of time. Obviously that's an abuse of the DMCA system at-large, but I don't believe that there is a good way to really contest that in spite of that being something we can do.

In effect, I'm looking for clarity on the policy here and what could be done to improve it. What is the policy today, and what transparency on this can we expect tomorrow?

3
  • Just for clarity: the Anime.SE question linked here has not been deleted & undeleted, despite being one of the targets of the DMCA request. Only a few have been deleted before the process for that DMCA request was paused indefinitely. Commented Aug 21, 2023 at 12:32
  • @MetaAndrewT.: I'm 100% confident that it was deleted at one point during the DMCA process, then perhaps it was undeleted. I wouldn't expect that to be in the history of the post since a DMCA process happens largely outside the scope of normal post deletion and would likely leave little to no trace of it happening (which is why disclosures through sites like Chilling Effect are/were vital).
    – Makoto
    Commented Aug 21, 2023 at 14:04
  • At that time, SE didn't have specialized DMCA tools. We (Anime.SE mods) can still see those 17 questions that were deleted normally, not even redacted (yet). There's also no deleted comment by JNat notifying the reason for the deletion on your post. Commented Aug 21, 2023 at 14:13

1 Answer 1

20

Last time our attorney attempted to explain this to me, it was along the lines of "the law does not allow us to question the DMCA" and that we have to take action, and it's the responsibility of the accused to file a counter-notice (all they need to do is send a properly formatted counter-notice to the same dmca@ email). If we play a role in determining validity, then we become liable and can be sued for damages just as much as the person who posted if we turn out to be wrong. We can't put the entire network at risk to try and do what we and our users would argue is right. That would be fairly irresponsible on our part.

That's not to say we don't still question really weird takedown requests. I've sent at least a couple back to legal seriously questioning what the link to the infringed content had anything to do with the content on our site, and some clarification with the sender revealed it was an error and invalid. But if they had insisted that it was correct and action should be taken, we likely would have still had to take that action.

The only part of this we can improve is the transparency, and it's something we're still working on. We've recently been cooperating with legal in our move to the new support system to make sure DMCA requests remain visible to us at all times, because we're eventually going to start pulling those out of the support system and into an internal archive for safekeeping.

One key feature we want to add is a new lock reason for the question which better highlights that it was deleted due to DMCA and who sent the request, rather than having an unnoticeable comment that's sometimes hidden. This also would prevent the question being subsequently undeleted if the staff member who deleted it ever left the company, or if moderator diamonds ever stop preventing undeletion by the community. It might also provide a way for us to directly link the post to a specific DMCA notice so we don't have to go searching for it later, if need be.

Once that lock reason is in place, we'd retroactively apply it for all the posts we've deleted by simply searching for all the comments/flags we've left describing the DMCA deletion. Having all these locks would allow us to just look for posts with the lock and easily run numbers to generate transparency reports for how many posts/accounts were affected without any additional effort on our part.

22
  • 5
    It's worth clarifying that if a user ever later loses their moderator privileges, posts that were deleted by them can now be undeleted by the community. Commented Nov 2, 2018 at 18:07
  • 3
    There's nuance in "the law does not allow us to question the DMCA" in that "Stack Overflow" could be liable if They defend the content. An FAQ entry from Legal's perspective on this matter would be valuable when a more transparent way to archive and identify these takedowns would be very valuable.
    – Makoto
    Commented Nov 2, 2018 at 19:29
  • 5
    I have a few questions: When a post is removed due to a DMCA claim, who is notified so that they can potentially file a counter notice? Is it just the author of the post? Is it the author of answers on the post? If someone wishes to file a DMCA counter notice with Stack Exchange, where should those be sent?
    – Andy
    Commented Nov 2, 2018 at 20:00
  • 7
    @Andy Only the author of the post is notified. Counter-notices can be sent to [email protected] same as the notices themselves.
    – animuson StaffMod
    Commented Nov 2, 2018 at 20:22
  • 7
    How is the author notified? Is it via mod message, email, both?
    – Andy
    Commented Nov 3, 2018 at 13:35
  • 2
    what would happen to a community wiki, who is notified then? I feel that even though the post is the responsibility of the original poster, it does sort of belong to the community.... Commented Nov 5, 2018 at 15:51
  • 3
    @Pureferret By default only the owner would be notified, but I'm also not gonna make up processes for what would happen to a CW because it's never happened and I kind of doubt it ever will. If it ever did we'd think about what to do at that time.
    – animuson StaffMod
    Commented Nov 5, 2018 at 15:53
  • 2
    "...and it's the responsibility of the accused to file a counter-notice (all they need to do is send a properly formatted counter-notice to the same dmca@ email)." Um...and then what? SE still can't "...play a role in determining validity..." can it? What's the point of the counter-notice? (And: Wow is the DMCA every bit as flawed as I remember it being, if that legal advice is correct.) Commented Nov 15, 2018 at 8:02
  • 1
    @T.J.Crowder the details outlined here don't seem flawed to me. The legal advice seems to be that Stack Exchange are allowed to unilaterally refuse to comply with a DMCA request, as long as they're willing to take on liability for any infringement. That seems right; what other system would be reasonable? The fact that, per this answer, the company's legal department have chosen a policy of never contesting DMCA requests - even if they are blatantly obviously meritless and the complainant has no chance to win in court - doesn't seem to me like it's a fair thing to blame the DMCA itself for.
    – Mark Amery
    Commented Nov 15, 2018 at 13:10
  • 5
    @T.J.Crowder When we receive a counter-notice, we are allowed to undelete and restore the post, because the user is claiming it does not violate copyright. We would then notify the party that sent the original notice. It is then up to the two parties involved (the one who filed the takedown notice and the one that filed the counter-notice) to basically battle it out in court.
    – animuson StaffMod
    Commented Nov 15, 2018 at 14:39
  • 1
    @animuson - Cool, thanks! Commented Nov 15, 2018 at 14:41
  • @MarkAmery I'm not sure, but I thought the law doesn't allow a content provider (e.g. SE) to choose how to handle each individual takedown request. They can either automatically honor all requests, in which case they get the benefit of the safe harbor provisions, or they can do something other than automatically honoring all takedown requests, in which case they are liable for infringement. In other words, the policy they chose is the only way they can legally avoid liability for copyright infringement on the network. But again, I'm not sure about that.
    – David Z
    Commented Nov 16, 2018 at 11:22
  • 1
    I rememberd that once SE filed all the incoming DMCA notices into something like the webarchive. But that SE stopped doing that. Perhaps SE can have its own page of DMCA notices, so that we can see who is <strike>bullying</strike> filing complaints and what effect they resorted.
    – Luuklag
    Commented Nov 16, 2018 at 11:27
  • 1
    Where the changes shipped into the system? Also, are 10kers supposed to be able to see DMCA'ed content?
    – Braiam
    Commented Jan 12, 2021 at 11:44
  • 1
    @Mast That was Shog's plan. I haven't been involved in DMCA in quite some time (it's owned by Trust & Safety now) and don't know if they even continued using the same comments to make them identifiable. At one point, we were redacting the posts to remove the content altogether. If how we handled them changed too much, it would no longer be easy to apply it retroactively. At least not in an automatic way.
    – animuson StaffMod
    Commented Nov 2, 2022 at 22:03

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .