I also get substantial benefit from it, so I can't say it is. I think it's more akin to nuclear energy: bit potential, big risks.

Real backups must to be automatically maintained as multiple encrypted, integrity-checked, tested, monitored, and documented historical copies, on different media, offsite, and offline or immutable.

RAID, snapshots, Apple Time Machine, Windows Volume Shadow, cloud storage, availability zone mirroring, database replication, Git/GitHub, DRBD. These are all useful, but NOT true backups.

The proposed changes are well reasoned and documented. More thought could have been given to asking for shorter proposals. A good proposal takes months to write, which is time not devoted to research.

Google Scholar's lack of an API hinders automation and scientometric studies. In common with all proprietary academic databases, searches are opaque and non-replicable. With the Alexandria3k Python package you can run sophisticated queries on your laptop. dspinellis.github.io/alexandria3k/