File Naming Standards

Would it be possible to discuss and create file naming ‘standards’ via the upload (publishing) process to help with the maintenance and upkeep of the thousands of files available to end-users? Could this maybe be done as a survey across the community to see how widely it might be accepted? IMHO there are three major categories: airports, aircraft liveries, and scenery files that sorely need a file naming ‘standard’ to help eliminate confusion with files, especially with the current Flightsim.to UI. For instance, maybe all airport filenames could be standardized something like this…KDFW_20_JoeBuilt_v1.2.3_202512301200.zip. The author/developer at the time of upload would input the airport ICAO, the MSFS version (in this example 2020), author/developer name (JoeBuilt), and file version (developers’ version). Flightsim.to might provide fields for the author/developer to input these values during publication (uploading) to format and create the filename. Flightsim.to might also automatically attach a date/timestamp to the file name during upload (in this example YYYYMMDDTIME). Such a filename would never be duplicated. Searching for specific airports would be made super-efficient even amongst different developers. Also, if authors/developers could be encouraged to voluntarily include a text file description of the contents with specific install instructions as required and/or any other pertinent information such as an aircraft picture for livery files in the zip file root folder (instead of having to plunder into the file and find the thumbnail picture) the end-user could pick up the file a year later and know what it is and how to use it without any question. It also makes finding and updating files on the PC more efficient by the end-user. Even in the FSX days most files included at least a FileID.txt in the zip to explain the file contents. How many could wish their hundreds/thousands of downloaded files were all like this now. In a similar way maybe a file naming ‘standard’ could be developed for aircraft liveries and scenery files. Would this not be advantageous in many ways? All this is just food-for-thought but imagine how it would help the maintenance of files and save time for the end-user. Personally, I spend many hours to manage and update the thousands of files I have present on my hard drives to date. Maybe such an improvement would even help Flightsim.to better manage thousands and thousands of files?