I'm actually currently working on the ZIM toolchain for Kiwix on a contract basis, so I'd be interested to hear more about your pain points, they might be somet

I'm actually currently working on the ZIM toolchain for Kiwix on a contract basis, so I'd be interested to hear more about your pain points, they might be something I can help out with. In general, I'd say that ZIM and WARC are not really direct competitors or solutions to the same problems, they're really for distinct use-cases. ZIM is a highly-compressed format that's designed solely for static articles and flat content, it doesn't really store headers or anything else that WARC does in order to support full request/response replaying. ZIM is optimized for storing thousands to millions of pages of homogenous content, WARC is optimized for high-fidelity collections of smaller amounts of content. If you want to help out with our efforts, feel free to DM me on Twitter @theSquashSH or reply here and I can introduce you to the ZIM people (who get grants to improve this process on the regular, and are open to hiring contract workers).