|
Welcome @noDRM. I think the tools have been tolerated by Adobe and Amazon for a number or reasons. The DMCA is an unbalanced and far over-reaching piece of legislation. Whilst its application is limited to US jurisdictions in practice its influence is far wider. The tools arguably offend the very wide "anti-circumvention" provisions, which, thanks to the US, are mirrored in the copyright legislation of other major western jurisdictions. Adobe has not so far taken any similar action against the tools. The readium takedown notice reads almost as though you have violated an unwritten truce in respect to library books etc. I suspect Adobe is simply realistic. They already had the bulk of the DRM market when the tools first appeared and seem to have realised that those removing DRM are very much a minority who cost them little or nothing. It is significant that even Readium specifically excluded Apprentice Harper's repository from their notice, and clearly do not want to attract publicity and risk alienating the community. I think their problem is that they are seeking to establish their business in opposition to Adobe, and are slowly expanding, mainly but not exclusively in Europe and amongst libraries. They obviously felt their business model was threatened and perhaps some marketing advantages lost. Personally I agree with most of your reasoning. However, DiapDealer's point that making it now only possible but trivial and accessible to remove DRM raises the stakes to the point where actions such as readium's are much more likely. So, for instance, whilst modifying the old code to make it decrypt library books seems to be very easy, reading and changing Python Code in a plugin is way beyond many, with many more simply not interested. When a product does this "out of the box" it is likely that many more will do it. Hopefully taking your excellent readium decryption code out of the plugin will address their concerns and enable the repo to be reinstated. It may also be worth reinstating the code relating to library books.
If the tools are to actually go in the direction you intended I don't see that they have a development future on Github or in US and similar jurisdictions. Probably development would need to be taken up by non-US developers and development move outside of the mainstream.
|