Why this matters: current single-file approach breaks common industry project workflows with repeated folder structures. The industry solved this problem years and years ago with .gitignore, now you decide to throw that out the window for a large one at the top.
As someone who works on lots of different unity projects, I use templates. When they get generated, imagine if I could throw a .dropboxignore file into this template and then never sync my library folders on any devices, never sync any temp folders, and never sync packages because they should all be handled by package revolvers.
The types of people who use this type of feature are the types of people who are use to gitignores, which is why it is so monumentally baffling that you have done things this way. I seriously can not fathom for the life of me why you did it this way.
Device: Custom Desktop (5070ti, 7800x3d, 32gb)
OS: Windows 11
Dropbox App Version: 243.4.6956
