Sorry for the lack of clarity, let me reformulate my compression question.
Let’s take the example of email backup (which is ultimately what is of interest for me): emails are .emlx files, mostly plain text with the attachments uuencoded inside the files.
When I use EagleFiler to archive, these files are essentially moved from Apple Mail library to EagleFiler database (which is a folder and metadata files). The good side: I get to keep the original emlx file and it’s spotlight searchable.
However, lots of emails (still) contain BMP images (despite my complains) and a lot of text. Both (especially the BMP payload) are easy to compress and to save on disk space. I’d like to keep the emlx files as: .emlx.zip inside the archive database (it’s an archive so it can be somewhat slower of access). Obviously I don’t want to compress each file individually and decompress each file to access the DB. I’d like avoiding having to decompress a potentially large DB to be able to access it also.
Given that you already have encryption built in, it means that you must have a mechanism to transform the emlx files (decrypt) that are stored in the database. Also, usually to save on encryption time and to strengten the encryption, most program actually compress files before encrypting them. Hence my request for on-the-fly compression of databases :). Do you have something like that on your roadmap? How does your encryption actually work? When the database is encrypted, what about spotlight and your search function?