Quote:
Originally Posted by JSWolf
|
I have to unlink openssl and relaunch calibre before that works, the plugin throws exception otherwise. Then relink and relaunch after.
It is easy enough to do, but I do not know why it is necessary or cannot be fixed. Maybe it is not an issue if not using HomeBrew but that is a necessity for me.
I don't think it is an issue on Windows - I do have calibre instance set up there for processing some Amazon books, so I will try installing the plugin there to avoid the need for the unlink/link workaround, especially since I may be purchasing more ACSM protected books going forward.
I wonder about the timing of this, after all these years. They've made a sale, what do they care what happens after that?
Perhaps their lawyers wanted to reduce their exposure to lawsuits that claim their indifference to the fact that DRM is so easily removed makes them liable for lost sales because piracy etc. Amazon is a big fat target and that could hurt them, and then they'd still have to do DRM hardening if they lose the lawsuit, even if it has no merit. Even winning such a suit would be losing in some sense.
If that's the case (whatever the reasons are), then we can anticipate hardening update sooner or later at least for Kindles still getting them. And PC 2.4.0 will get unplugged.
After that (or even now) somebody should still sue them to restore D&T for what are supposed to be DRM free books (if polite and reasonable requests to do so do not work). And actually that is something we could all do with feedback.