2O2OEH8eoCRo0·Dec 28, 2022
In Barnes and Noble's surprising turnaroundnoDRM
DeDRM_tools
Python2022–2026
noDRM / DeDRM_tools
DeDRM_tools
DeDRM tools for ebooks
15Distinct people
17Mentions
0Explicit recommenders
10.5KGitHub stars
What to know before exploring
What it is
DeDRM tools for ebooks
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year17 dated mentions
Observed mentions: 2022-01-10 04:01:33 UTC to 2026-03-16 15:17:22 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesThe important change is that LCP DRM is no longer supported [0] (git history was rewritten):
> Support for LCP DRM removal was included in the past, but Readium (the company who developed that particular DRM) has decided to [open a DMCA takedown request](https://github.com/github/dmca/blob/master/2022/01/2022-01-0...) in January 2022. This means that for legal reasons, this GitHub repository no longer contains the code needed to remove DRM from LCP-encrypted books.
(Quote from the FAQ)
[0]: https://github.com/noDRM/DeDRM_tools/blob/master/FAQs.md#why...
This is the file that was removed: https://cloudflare-ipfs.com/ipfs/QmVoHkQ7AYMprL9eMtDQUa7zgGz...
In NoDRM's GitHub repo DeDRM_tools is backNoDRM's GitHub repo DeDRM_tools is back
3 points · Open discussionProbably these bits:
> The user noDRM is actively promoting the activity of cracking both library loans and one-off purchases:
> https://github.com/noDRM/DeDRM_tools/issues/2#issuecomment-9...
> This departs from the policy of the user [private], from which noDRM has forked the repository DeDRM_tools. The user [private] does not provide circumvention material for the LCP solution, therefore it is not part of our request for takedown.
In noDRM's GitHub repo DeDRM_tools is disabled due to Readium's DMCA noticeHow does quoting a passage where they assert copyright ownership over one thing imply that they did not also assert copyright ownership over something else?
> What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL. ... https://github.com/noDRM/DeDRM_tools
> the content of the repo was illegally obtained. The repo and its forks must be shut down entirely.
> I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.
> I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.
In addition, the larger co
Read the rest
ntext of a DMCA Takedown Request is to assert expedient takedown of a copy of work that you have copyright ownership over. Adding a bunch of backpedaling filler to a DMCA Takedown Request does not alter its basic purpose.
edit: Sheesh it looks like Microsoft is actually encouraging claimants to write these fraudulent DMCA notices regarding circumvention technology [0]. So this is basically another extralegal "Content ID" process, and Microsoft being overzealous with takedowns makes them a terrible option for hosting your stuff. I'd love to see the law produce some justice here for once, but the real answer to these corporate-bought one-sided laws is IPFS and the like.
[0] https://docs.github.com/en/github/site-policy/guide-to-submi...