Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Extracting content from an LCP “protected” ePub

shkspr.mobi

Post reply on HN
Print view View original

11–20 of 72 posts

Re: Extracting content from an LCP “protected” ePub

#11

Post by nocoiner »

ferbivore wrote: post #2

> You can, for sure, publish information relative to your discoveries to the extent UK laws allow. After study, we'll do our best to make the technology more robust. If your discourse represents a circumvention of this technical protection measure, we'll command a take-down as a standard procedure. Disgusting behaviour, as expected from the publishing industry I suppose. This "EDRLab" outfit appears to be little more…

The author’s response was just perfect though in both tone and substance.

“As you have raised the possibility of legal action, I think it is best that we terminate this conversation.”

Once someone shoots off about getting the lawyers involved, there’s really nothing more than can productively be said (unless, of course, you are prepared to get your own lawyers involved).

Re: Extracting content from an LCP “protected” ePub

#12

Post by baruchel »

A more straightforward way to do it, IMHO, is to use Thorium in conjunction with a Python script called lcpdedrm. If I remember well, that script isn't available directly any longer, but it is easy to look around and find copies of it. Then use Thorium for locally saving the file and use the Python script for removing the DRM.

Re: Extracting content from an LCP “protected” ePub

#13

Post by npodbielski »

ferbivore wrote: post #5
spudlyo wrote: post #4

Granted, Readium LCP[0] may be one of the less odious DRM solutions out there for eBook contents, however it's still DRM. Handcuffs are still handcuffs regardless of how comfortably they fit. DRM is in my view is too often used as a cudgel to mandate hardware and software level restrictions that take away the control of our own computing devices and environments. I personally hold that intellectual property isn't pro…

Altman isn't on your side, or any side except his own. OpenAI insists both that they should be allowed to train models on any text they can gain access to, regardless of copyright or licensing ( https://openai.com/index/openai-and-journalism/ ) and that you should not be allowed to train models on any text produced by their models ( https://archive.is/20250130132153/https://www.nytimes.com/20... ).

Exactly. OpenAI and altman would be very happy to say that intelectual property does not apply to them but then enforce that law when they talk about their own intelectual property being used without their consent.

Re: Extracting content from an LCP “protected” ePub

#16

Post by damnitbuilds »

lxgr wrote: post #7
spudlyo wrote: post #4

Granted, Readium LCP[0] may be one of the less odious DRM solutions out there for eBook contents, however it's still DRM. Handcuffs are still handcuffs regardless of how comfortably they fit. DRM is in my view is too often used as a cudgel to mandate hardware and software level restrictions that take away the control of our own computing devices and environments. I personally hold that intellectual property isn't pro…

> I find myself uncomfortably on the side of AI bros like Sam Altman who argue for the expansion of the fair use doctrine Why? Are you training LLMs? I highly doubt they'll fight a pro-consumer fight completely incidental to their objectives (if not detracting: don't need to buy the source textbook if you can ask ChatGPT about its contents as soon as it's released).

In a courthouse in the near future:

"So, yeronner, I think you will agree that I was well within my rights to share a torrent of the new Batman movie, not for people to watch but so they could train their LLMS on it."

Re: Extracting content from an LCP “protected” ePub

#17

Post by damnitbuilds »

lxgr wrote: post #15
damnitbuilds wrote: post #14

One should also note that Thorium is a remarkably crappy app to read Epubs on.

I've never used it myself, but I'd be really surprised if it somehow managed to be worse than Adobe Digital Editions.

I lol'ed.

Indeed, the bar is low.

Re: Extracting content from an LCP “protected” ePub

#18

Post by Akronymus »

JadeNB wrote: post #3
ferbivore wrote: post #2

> You can, for sure, publish information relative to your discoveries to the extent UK laws allow. After study, we'll do our best to make the technology more robust. If your discourse represents a circumvention of this technical protection measure, we'll command a take-down as a standard procedure. Disgusting behaviour, as expected from the publishing industry I suppose. This "EDRLab" outfit appears to be little more…

> Disgusting behaviour, as expected from the publishing industry I suppose. This "EDRLab" outfit appears to be little more than a non-profit front for Hachette. The quoted block is indeed disgusting, but it gets even weirder in the context of the full discussion, where the correspondent seems to be trying some sort of intellectual blackmail on the author of this article, saying that, as long as nobody talks about its…

> we are already working on that

so they worked on making harder to crack DRM before being informed of the weak DRM...

Re: Extracting content from an LCP “protected” ePub

#19

Post by damnitbuilds »

captn3m0 wrote: post #9

Readium was also responsible for the takedown on the noDRM repo, a few years ago: https://news.ycombinator.com/item?id=29870151 The repo came back, but without the readium DRM code: https://github.com/noDRM/DeDRM_tools/blob/master/DeDRM_plugi...

To further Streisand this, I think the restored repo is here:

  https://repo.or.cz/DeDRM_tools-LCP.git
Post reply on HN