View Single Post
Old 03-15-2024, 08:41 AM   #1857
noDRM
Junior Member
noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.noDRM ought to be getting tired of karma fortunes by now.
 
Posts: 2
Karma: 7042596
Join Date: Jan 2022
Device: None
Right now, I don't think there's any advantage in actually releasing a 10.1.0 build. I was assuming that Amazon would be updating their DRM shortly after a bunch of changes were added to be able to handle newer KFX versions, and I was also assuming that a full new release (which typically leads to a bunch of ebook-related news sites to post articles like "New DRM remover for Amazon books just released!!" clickbait articles) would just lead to Amazon updating their DRM again.

So I made 10.0.9 an RC version to get it out to people that need it (want to remove DRM from Amazon books) but hopefully don't give Amazon too big a reason to immediately deploy new DRMs. That didn't happen, though, as far as I know 10.0.9 can still handle quite a few Amazon books even half a year after its release.

Given how well 10.0.9 (or even the latest auto-releases) seem to work for people, there's no reason for people to not just install the newest version. There's a beta that can be downloaded from Github, and even an automated alpha release which I added to make it easier for people to download and test the most up-to-date code.

I don't see an advantage in making a full new release right now, I just see the risk of Amazon investing more time and money in breaking it again. At least right now, in the eyes of the public, people are still like "Amazon DRM is hard to remove, not worth the effort".

I'm still skimming through all the github issue reports from time to time, it's not like I lost interest in the tools. Latest fixes / changes to the tools (apart from the one fix I just committed) are from December, that hardly counts as "abandoned". Though I did stop commenting on every "Help, X doesn't work" issue report that was either caused by user error or outdated tools.

Of course, development has slowed down quite a bit now that most of the bugs and features I've wanted to fix/add with my fork are fixed/implemented and I lost interest in supporting entirely new DRMs because I don't want to deal with another false DMCA claim like last time.

Yes, installing the plugin isn't as easy as going to Calibre's plugin search and you do need to deal with the double-ZIP "issue" - but the easier and more popular this becomes, the higher are the chances that Amazon or Adobe or whoever will do more against it ...
noDRM is offline