Prevent older cloud presets from overwriting newer local files

[L0rdS474n]

• Guard preset downloads by combining local metadata timestamps with file modification times, rejecting cloud profiles that are not fresher.
• Improve logging to show the effective local freshness value used during sync decisions, aiding debugging of timestamp-related issues.

[XinZhangBambu]

Thanks for your help. Is there any problem here that requires the time zone to be modified?

[L0rdS474n]

I think so. No matter what I do, the old profiles reappear after a few hours if I have cloud sync enabled.
Regardless of when I create or update them, my profiles are treated as outdated until we pass the date that the server has stored. When you provide a synchronization service, it is crucial to use UTC for timestamps, because you cannot reliably know the user’s time zone before the files are synchronized. I, for example, travel with my laptop and cross multiple time zones – what happens if some of my profiles are synchronized during such a trip?

I have not yet had time to fully verify that this is exactly what happens, but using a fixed time zone in any synchronization logic feels fundamentally wrong.

[XinZhangBambu]

Understood. We will consider the correctness and feasibility of this change and need to conduct actual tests. This may take some time.

#8916 (comment)

[L0rdS474n]

Understood. We will consider the correctness and feasibility of this change and need to conduct actual tests. This may take some time.

#8916 (comment)

Thanks,

This might also refere to when you have to many profiles according to the server. If I read the Wiki I should be able to have 200 filament profiles and 100 process settings. I'm well under that limit but I get a warning that to many profiles are cached in cloud and I have to have cloud syncronization off for now.