it's not about the past (2017...), the authors are concerned about how the dataset could be or is likely to be used from now on.
many tech projects these days have or are thinking about integrating third-party A.I. providers in their services, either to harness the power of their large datasets or their large user-base. I think it's great if authors/users opt-in to this, but likewise I agree with those that want out (opt-out).
>> I called it "fear" because there was no strong argument on the authors' side as to why this tool is bad
their argument doesn't have to be a peer-reviewed journal, it suffices to say "i don't want my books in your dataset"
>> I called it "illogical" because I think that it's no coincidence that this controversy only came up now, in 2023. Back in 2017 and onward, the existence of this tool didn't appear to generate pushback ...
6 years have passed since 2017, life moves on, it's natural for things to change e.g: the project's code, updating servers, partnerships, emergence of third-party tools/libs/services etc etc.