![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0d5e3a0e-e79d-4062-a7bc-ccc1e7baacf1.png)
Get off of .world if you want to see a difference.
The size of that instance almost guarantees these kinds of dynamics will emerge, especially on a website run by volunteers and paid for by donations.
Stop complaining to other users; go be the change you wish to see.
The idea is neat, and there is a certain precedent for the approach in .htaccess files and webserver path permissions.
Still, I worry about the added burden to keeping track of filenames when they get used as stringed keys in such a manner. More plainly: if I rename a file, I now have to go change every access declaration that mentions it. Sure, a quick
grep
will probably do the trick. But I don’t see a way to have tooling automate any part of it, either.