Hello @noDRM! Thank you for popping in and sharing your thoughts, and thank you for your contributions to the tools. I look forward to seeing you on GitHub again or following you elsewhere should that become necessary.
Quote:
Originally Posted by darryl
... The readium takedown notice reads almost as though you have violated an unwritten truce in respect to library books etc.
|
The way I'm reading the
takedown notice, this has nothing to do with library books specifically and everything to do with Readium LCP as a whole.
Readium describes LCP as a DRM solution for "Ebook distributors, e.g.,
public libraries and online booksellers", and their grievance is that noDRM's plugin is being used to "circumvent the LCP protection ... [for]
both library loans and one-off purchases". [
emphasis added]
There doesn't seem to be anything in the notice that indicates circumventing LCP library loans is more egregious than circumventing LCP purchases. The issue appears to be LCP under any circumstance.
Quote:
|
... It is significant that even Readium specifically excluded Apprentice Harper's repository from their notice ...
|
From the
takedown notice: "[Apprentice Harper] does not provide circumvention material for the LCP solution, therefore it is not part of our request for takedown."
The way I'm reading it, Readium cannot initiate a takedown request for Apprentice Harper's repository because they have no standing there.
Per step 1 of the takedown process, only the copyright holder can initiate a takedown request, and Readium doesn't hold copyright for any DRM being circumvented by the Apprentices's tools — i.e., only Amazon, Adobe, and Kobo can request a takedown of Apprentice Harper's repository.
I suppose Readium's takedown might inspire Amazon, Adobe, or Kobo to do the same — but I think Amazon's response is KFX, and Adobe's response is their "hardened DRM".
In any case, removing the LCP material should be enough to make Readium's grievance moot, and hopefully that will be enough for GitHub to reinstate noDRM's repository.