No specific feature is required by law. What's required by law is that providers
(C) upon notification of claimed infringement as described in paragraph (3), responds expeditiously to remove, or disable access to, the material that is claimed to be infringing or to be the subject of infringing activity.
There isn't any place in the DMCA that suggests any limit to the number of notices that can be provided. On a tactical level it seems like having limits was a mistake: they should have just queued them let the bottleneck express itself as a backlog and a delay.
On a strategic level, it doesn't matter. The argument that MegaUpload wasn't aware of its status as a piracy hub is totally implausible. It thus flunks 2 of the 3 conditions for establishing immunity under the DMCA.
There isn't any place in the DMCA that suggests any limit to the number of notices that can be provided.
There is no limit on notices. The limit is only on the direct-deletion of links, without review or notice, by parties like Time Warner. In other words, in addition to handling notices, Megaupload gave "Delete" buttons to certain parties that allowed them to directly control which links were available, but that button was limited in use.
(C) upon notification of claimed infringement as described in paragraph (3), responds expeditiously to remove, or disable access to, the material that is claimed to be infringing or to be the subject of infringing activity.
There isn't any place in the DMCA that suggests any limit to the number of notices that can be provided. On a tactical level it seems like having limits was a mistake: they should have just queued them let the bottleneck express itself as a backlog and a delay.
On a strategic level, it doesn't matter. The argument that MegaUpload wasn't aware of its status as a piracy hub is totally implausible. It thus flunks 2 of the 3 conditions for establishing immunity under the DMCA.