After the Major Service Outage, I have seen an unpleasant change in the behaviour of the Murenacloud.
Since I am using the free plan (1Gb storage), I sometimes have to delete old synchronized pictures/videos as to free up some space for new media files and this worked very fine (i.e. the deleted files would be excluded from any upcoming synchronization). But since the service has been reestablished, the system does not understand that those files should be excluded anymore and keeps reuploading them after I remove them. As such, the last files uploaded to my Murenacloud space dates back to the 18th of April…
Would there be an other way to proceed than to delete the files from my phone storage as well ?
I found that it’s a major drawback to users that don’t require a lot of storage space.
the 2.9 update did force a device-side purge of the database that keeps track of former uploads (to not reupload on remote-side deletion). With that database all brand new, reuploads happened (as intended by the code change).
If the reset doesn’t happen again, your remote-side deletions should be honored.
Nevertheless, even though I am deleting old files (remote-side), e.g. <2023, they just keep coming back constantly (did not notice any change up until today). It feels as though there is no “database that keeps track of former uploads” anymore.
if you want to debug, fetch the database. When there’s no ETag to the file, it thinks it never uploaded. In that model you’d need to delete twice remote-side to not get another upload when the eDrive internal database is reset/new. (But sure, bugs always very much possible, I’m not defending the software)
Great idea thanks, though in your April 16 you are referring to a README which contains the dump db command but where can I find it and how should I run that command ?
