Galomi04 (talk | contribs)
m Preliminary: added an explanation and referred to a reference
Galomi04 (talk | contribs)
m DMCA Takedown (2022-01-04): spelling and added a new reference
Line 53: Line 53:
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].
This is a list of all consumer-protection incidents this company is involved in. Any incidents not mentioned here can be found in the [[:Category:{{FULLPAGENAME}}|{{PAGENAME}} category]].
===DMCA Takedown (2022-01-04)===
===DMCA Takedown (2022-01-04)===
Readium filed a [[Digital Millennium Copyright Act |DMCA]] takedown notice with [[wikipedia:GitHub|GitHub]] in 2022. The notice stated that: <blockquote>"The user noDRM has published on GitHub software which specifically allows the decryption of ebooks protected by the LCP Profile 1.0 and allows saving them as non-protected ebooks. This infringement violates our legal business and affects authors and publishers’ IP. This codebase is presented as a plug-in of the well-known Calibre software, an open-source ebook manager."</blockquote>
Readium filed a [[Digital Millennium Copyright Act |DMCA]] takedown notice with [[wikipedia:GitHub|GitHub]] in 2022. The notice stated that: <blockquote>"The user "noDRM" has published on GitHub software which specifically allows the decryption of ebooks protected by the LCP Profile 1.0 and allows saving them as non-protected ebooks. This infringement violates our legal business and affects authors and publishers’ IP. This codebase is presented as a plug-in of the well-known Calibre software, an open-source ebook manager."</blockquote>
As well as that the explicit circumvention of Readium LCP was in a file called '''"lpcdedrm.py'''." And that: <blockquote>"The user noDRM is actively promoting the activity of cracking both library loans and one-off purchases"</blockquote>followed to a link to a GitHub Issue to substantiate the claim.<ref>{{Cite web |title=2022-01-04-readium |author=[private] |date=2022-01-04 |url=https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |url-status=live |archive-url=https://web.archive.org/web/20260604153156/https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |archive-date=4 Jun 2026 |access-date=23 Jun 2026}}</ref>
As well as that the explicit circumvention of Readium LCP was in a file called '''"lcpdedrm.py'''." And that: <blockquote>"The user noDRM is actively promoting the activity of cracking both library loans and one-off purchases"</blockquote>followed to a link to a GitHub Issue to substantiate the claim.<ref>{{Cite web |title=2022-01-04-readium |author=[private] |date=2022-01-04 |url=https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |url-status=live |archive-url=https://web.archive.org/web/20260604153156/https://github.com/github/dmca/blob/master/2022/01/2022-01-04-readium.md |archive-date=4 Jun 2026 |access-date=23 Jun 2026}}</ref>
As a result, the relevant files as well as relevant [[wikipedia:Git|Git]] history was removed from the repository.
As a result, the relevant files as well as relevant [[wikipedia:Git|Git]] history was removed from the repository.<ref>{{Cite web |author=captn3m0 |date=17 Mar 2025 |title=Extracting content from an LCP “protected” ePub |url=https://news.ycombinator.com/item?id=43378627 |url-status=live |website=news.ycombinator.com |archive-url=https://web.archive.org/web/20260616102133/https://news.ycombinator.com/item?id=43378627 |archive-date=16 Jun 2026 |access-date=24 Jun 2026}}</ref>


==Products==
==Products==