You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
I am an APL programmer. That's exotic, and that's the problem. We keep our code in files with the extensions:
* `.aplf` (functions)
* `.aplo` (operators)
* '.apln` (namespace scripts)
* `.aplc` (class scripts)
* `.apli` (interface scripts)
* `.apla` (arrays)
In all these cases they are simple UTF-8 files, so they could easily be put on preview. But they are not, and that's pretty annoying.
One way to address this is to add these extensions to the list of extensions that qualify for preview. But that list might become VERY large in case every small community asks for something like this. Worse, small and exotic communities might well use the same file type for different purposes.
It would be better to allow people to configure those file extensions so that users can decide what to do about this. This keeps the list short, avoids 99% of the possible conflicts and gives users the freedom to do whatever they like.
