Hi, File extension is a very handy concept which allows search and filter file list. The key is that one file extension is linked to one file in particular. Temp files (currently being downloading) with oDrive have random extension name, like .~de4dbaef-66fc-4888-a725-fd0957972c93 This is bad practice, IMHO. I understand why a unique identifier might be needed but why not in file name rather than extension ? For some reason I had to delete several Go of temp files (I dont know what sync error cause them), but I wasn’t able to make any relevant search based on fiile extension cause it was random. Why not use .cloudtemp for eg ? This would allow to quickly filter all temp files in a folder. Thx for listening !

Hi @extremraym , We released a version that uses a more predictable pattern for filenames: [image] Desktop and Web Releases (09-23-2019) Win v.6478 / Mac v.6535 Release Notes Hello odrive users, We’ve released some more improvements for the desktop clients and the web. Win v.6478 / Mac v.6535: Unsync performance improvements. Removes processing of filesystem events for blacklisted items (should reduce CPU and network activity). Tweaks to make bulk download operations more resistant to transient errors. Advanced setting to forget encryptor passphrase on odrive exit. Name pattern changed for temporary odrive files (.~_o-tmp_ …) Operational improvements and other bu… Temp files now start with .~_o-tmp_ which should allow you to search for them, if needed.

[SOLVED] FR: Temp files file extension shouldn't be random

Feature Requests

Tony October 1, 2019, 11:38pm 3

Hi @extremraym,
We released a version that uses a more predictable pattern for filenames:

Temp files now start with .~_o-tmp_ which should allow you to search for them, if needed.

1 Like