nei a. Collaborator | Level 8

5.5 years since removal, I still would like to have it back 

and the silence off dropbox continues

thanks for this, but somehow I cannot access the ticket. but nevertheless I do not really need this ticket, all information is in this thread. I need the question answered, which I asked above, i.e. has this bug been fixed? 2 years ago I lost data due to this, and this is something that should never happen, the first few…

anyone home?

@"dbox_", is now fixed or not? a simple yes or no would help .....

really? " account-specific information that may be necessary to troubleshoot" it seems to me that dropbox has not or is not willing to understand the problem there is nothing account specifc here, just install veracrypt, create a ****** container, set the flag not to update the file timestamp and observe that it does not…

@"John L.2" @"Julia20" @"Walter" @"Jane" @"Daphne" another month has passed, no communication from dropox. any news on not only tc/vc syncing, but any filename as encrypted container, anyone @dropbox?

as it is sitll not properly fixed, any timeline?

@Dropbox when will the workaround/restriction to .tc /.vc be removed? so it works again, as it was working up to about September 2019

it was like that before the "change" , all files got checked. and I still argue, having no communication from dropbox to the contrary, that they did this on purpose to reduce load on their infrastructure. as usually a file close event without date change of the file has no data changes.

no, I have not. I stopped installing any Dropbox beta builds about 2 years ago, when they stopped doing change logs. Also here, there is no change log or mentioning of this fix in the beta build thread referred, I cannot verify if the link points to a correct or other build. There are now 3 newer beta builds, do they all…

@"Julia" any reason why this no longer works? as Dropbox has a workaround, dropbox should now know what caused this

Dropbox is not interested in finding the cause of this or getting a solution. This is what I got for my request to pause/halt autoupdates temporarily for my account (they used to do this, so I know they can do it): "Regarding the update, I understand this can be frustrating to you, however, we are unable to disable the…

9912915 first I have been asked ot make a screenshot, I do no really know how do this for something that is not working. Then I got the answer: "The problem you’re experiencing appears to be caused by another app or service you’re using, not by Dropbox. We’re unable to provide support for third-party apps or services."…

as I write in my intial post, I believe 81 was last working good, not 82. when I install 81 it indeed starts syncing again the modified containers, however: for a minute only, until the *#*! autupdater strikes again while it is syncing, updates to 84, which then starts producing conflicting copies, grrrrrrrr

well, I can tell you it is more than 8 years, since it has been first requsted to get an option to exclude files/folders (this was in the old forum before this one, might have been even earlier, it was for sure before the votebox interlude) anyway, at that time Arash made a comment they have it internally, in it will soon…

now you confused me, this post was originally about vercrypt container no longer syncing properly, per file encryption (with or without filename) is a different technology (encfs or similar) anyway, I see two issues some thing changed on the way syncing is detected and executed, and dropbox not comunicating any changes.…

I do not think so, windows 10 with ntfs here, that should work or do I miss something? And it used to work until 2019-10-04 (last sync in my history), so something else must have changed. 

I have the same issue, but I think it started with version 82. The ugly "workaround" I use, is to copy the "file" daily to "file_yyyymmdd", this syncs, and the immediately delete the file. While the orginal file is not synced, doing this I have a daily history, I can get if needed. I think drobox either wants to save…

now I have the same issue, cannot move dropbox folder, geht the same error as in the screenshots above. Is there a timeline by dropbox for a solution or is it still an unknown issue?

I also would like to see this come back, however it will not happen, never has dropbox listened to users once they made a change. 

When you reach version 100, do we finally get change logs again?

changelogs

yes, or at least since they started the stupid habit of releasing as quickly as they are able to increase the version numbers in the code ....

yep, they just change the numbers, there is not much more they can do in the short time between 2 release ......

really? improvements?

really? improvements?

??? with many improvements and fixes.

now I know why they do not provide changelogs, as the changes and the version number seem to have no correlation at all. win 10, 43.4.50, I still have the start on system startup option while others for the same version do not ...., go figure ....

do you still think people are testing without changelogs? I don't