Why does Dropbox insist on renaming my files?

Same as BoxyBeat, and I am upset for the same reason as he/she is/was and it has to do with things he/she mentioned already, like being able to "keep track easier for missing files, [interrupted] transfers, moved files and so on". The only difference is that I take mostly photos, and not so much videos, so to me, it's completely uninteresting if the Dropbox app uses the timestamp from when the file was created or when it was last modified (in case of video files, according to referenced discussion above). But sure, I will give you some examples.

This is the naming convention that my phone uses to store the files in memory and how I want to keep them.

Format: YYYYMMDD_HHMMSS.jpg

Example file: 20210102_183405.jpg

This is the naming convention that the Dropbox app on my phone uses when the files are uploaded to Dropbox using the camera upload option.

Format: YYYY-MM-DD HH.MM.SS.jpg

Example file:  2022-06-24 19.14.54.jpg

There is a bit more to it when it comes to photo files that are taken within the same second. So the phone will add a suffix like "_03.jpg" and if I recall correctly the Dropbox app will turn that into "-03.jpg". I don't have a real example of this at the moment, I would need to spend another fifteen minutes searching for it as it's not very common that more than one photo is taken within a second, and it usually does that when you take burst shots, which I don't normally do. There are some more situations like that, but the general rule is what you have above.

So in summary...

File is stored as:

20210102_183405.jpg

File is mangled by Dropbox into:

2021-01-02 18.34.05.jpg

I expect the file to have this name on my computer after it has been uploaded/synced from my phone using Dropbox camera upload:

20210102_183405.jpg

Instead, Dropbox downloads/syncs to my computer a file with a name like this:

2021-01-02 18.34.05.jpg

So my question is, why are you doing this? And why are you not allowing people to change this behavior for years now? For example, does your backend not have the capacity to store or process files whose name contain underscores? A technical reason like that, I would understand, even if it seems highly unlikely. As it stands right now, you don't have a reason to do this (none has been given thus far in the many discussions on the topic). I on the other hand, like many users like me, do have a reason to keep the original file names and we have presented our reason.