For file types that are not able to be thumbnailed or indexed, there should still be basic support for querying the file's title, extension, size, and modified time.
I can't think of any reason not to provide this functionality. It would be easy to provide "fallback" icons for types that lodestone cannot handle but recognizes, such as json and zip.
I don't think there should be an exclude list at all -- just 2 tiers of "full support" and "minimal support".
Edit: depending on the response to this proposal, I also thing there should be fallback text indexing for any files not able to be parsed by tika. Basically any text files that can be unicode-decoded should be searchable, like csv and json documents. Need to do more research on tika and your implementation to understand how difficult this is.
For file types that are not able to be thumbnailed or indexed, there should still be basic support for querying the file's title, extension, size, and modified time.
I can't think of any reason not to provide this functionality. It would be easy to provide "fallback" icons for types that lodestone cannot handle but recognizes, such as
jsonandzip.I don't think there should be an exclude list at all -- just 2 tiers of "full support" and "minimal support".
Edit: depending on the response to this proposal, I also thing there should be fallback text indexing for any files not able to be parsed by tika. Basically any text files that can be unicode-decoded should be searchable, like csv and json documents. Need to do more research on tika and your implementation to understand how difficult this is.