WordPress has published its latest transparency report which shows that it only takes action for a small fraction of the piracy takedown notices it receives. A whopping 86% don’t result in any removals. This high rejection rate is mostly the result of “careless” incomplete notices sent by takedown companies, the report notes.
Automattic, the company behind the popular blogging platform WordPress, receives thousands of takedown requests from copyright holders.
For several years the volume of notices continued to increase, with a peak in 2018, after which the trend slowly went in the other direction.
This week, the company published its latest WordPress.com transparency report, revealing that it processed 2,412 takedown notices during the first six months of the year. That is a significant drop compared to a year earlier when over 3,321 notices were handled.
These data only apply to the number of DMCA notices that are directed at WordPress.com services. Each of these notices can contain multiple URLs, in some cases even dozens. In future, Automattic plans to release more granular data. Abusive and Incomplete Takedown Requests
Aside from the continued drop in takedown volume, the high rejection rate clearly stands out. Of all notices received, only 14% result in any content removals; the vast majority are rejected for a variety of reasons.
In the reported period, 77% of all notices were rejected because they were incomplete. An additional 9% was labeled as ‘abusive’ and dismissed for that reason. The remaining 14% was processed as usual.
The number of rejections is significantly higher than in the same period last year. According to Automattic, this is mostly due to more incomplete notices, which are often sent by specialized ‘removal companies’.
“Most of these incomplete notices were submitted through seemingly automated processes that are provided by content removal companies which often charge content creators to exercise their rights,” Automattic notes.
These ‘faulty’ notices also include requests to take down content that’s cached for other hosting providers, through WordPress’ Jetpack service, for example. Since WordPress is not the original host it doesn’t take action in response to these.
The high percentage of ‘faulty’ notices is a source of frustration for Automattic, which indirectly criticizes the companies that largely rely on takedown bots and automated processes.
Tumblr
Automattic also owns the blogging platform Tumblr, which it purchased in 2019. For this service, it releases a separate transparency report.
The Tumblr report shows a similar decline in DMCA takedown notices. In the first half of 2023, 2,278 takedown notices were sent to the platform, a significant drop from the 3,362 requests it received a year earlier.
A detailed breakdown shows that these DMCA notices targeted 2,369 posts and 11,146 pieces of other content. The majority of these notices, 78%, were valid and processed accordingly.
“This type of careless use of the DMCA makes it harder for platforms to efficiently process valid takedown notifications. In the past, we have highlighted similar problematic trends such as the negative impact of automated takedown notices submitted by bots,” the company writes.
All in all, the transparency reports show that the major DMCA takedown surge of a few years ago has subsided. However, Automattic stresses that it’s important to remain vigilant to ensure that content isn’t needlessly removed.
“For our part, we meticulously review each takedown notice we receive so that we can identify the validity, push back on abuse, and help our users understand their rights such as Fair Use,” Automattic writes.
You must log in or register to comment.
Going to bet a bunch of these saw the site used WordPress, the software… and sent a bunch of requests to WordPress.com.
That’s like calling Google support because you saw a bad image on the Internet.
I wonder if they can sue against these time-wasting takedown companies. At least bill them by the man-hour or something.
Technically, misrepresenting a copyright claim in a takedown notice is purgery. Within the notice itself you have to indicate that you are a representative of the copyright holder (or hold the copyright yourself), that you have a good faith belief under penalty of purgery that the use of the copyrighted material is not authorized by the copyright holder, its agents, or the law.
However, good luck finding someone who wants to spend the money to prosecute a legal document that can be easily contested or often simply ignored.
The other issue here is that many of these probably aren’t actually in bad faith, but have been submitted to both the actual file host and the site it’s linked on, or have otherwise misidentified the correct recipient, or have misidentified usage that would actually fall within fair use.
It’s often the reality that it makes more sense and gets better results to submit your DMCA notice to both those technically hosting the file and those who may be swayed into removing a post linking to it. Sometimes it’s more about rapport building with site owners in countries that don’t care about DMCA, or finding relevant local laws to wave at them. Often if they don’t follow through it’s literally just left at that, because chasing foreign legal entities is hard.
On the other end, it’s pretty easy to contest a false DMCA as long as the host doesn’t default to removal with no appeal, at which point they basically have to either spend the money on a court case in the US or drop it. That, of course, assumes that the host’s country cares about DMCA at all.
But essentially, people reporting infringement and it never going anywhere the majority of the time is DMCA working as intended. As a process it’s really more of a legal shield for hosts than it is an extremely effective method of enforcement. Often it’s tact and rapport that’s more important.
This article is about WordPress.com which is completely different from the open-source software available on WordPress.org.
WordPress.com uses a proprietary form of the WordPress software that requires an overpriced subscription just to be able to install plugins. Not to mention that they intentionally make it confusing that there is a difference between WordPress and WordPress.com.
They don’t give a definition of ‘incomplete’ or ‘faulty’? Is that on purpose?
Probably the law says they have to put in X, Y and Z and something of the required information is missing. Or maybe they need to provide some documentation that they’re acting on behalf of the original copyright owner, which is missing/implausible or it targets content that’s not even hosted by WordPress (e.g. a blog embedding a tweet and said tweet is violating copyright),…
I guess they neither want to educate those companies nor want to provide a lengthy list of errors.
(areBallsOnInternet) == true
