Yea, it's disregarding previous downloads and trying to start everything over. It is like it isn't even
Literally anyone who is mid-download for anything is going to need to roll back.
opening the download_history.sqlite file, it looks like running pip install cyberdrop-dl==4.2.231 in the bat successfully rolls it back and results in it picking back up where it left off
No, if the app needs to be changed to continue to work with supported websites, it needs to be updated. That's a no brainer.
The issue is that the app was reset, and for all intents and purposes, reset everyone's user configurations (which includes where the URLs are stored, and where the files are downloaded to).
If the changes to the app would not be able to accommodate keeping the user settings, the it should be made very clear that the new version is not backwards compatible with previous configs and pending/partial downloads.
That's like, when Firefox updates to a newer version (we're currently on 120.0.1), through means of the automatic update process which 99% of end users just click OK on, it decides 'well, we are going to change where your bookmarks and customization are stored, so when the update is done, they aren't going to work anymore. gg
. . . . . they damn well had done this before with the UI customization a few dozen versions ago and each time it's annoying. But using the userchrome.css to mod firefox isn't really something a layman would use, but if they did something similar with bookmarks, people would be livid.
