magika VS imgproxy

As someone that has worked in a space that has to deal with uploaded files for the last few years, and someone who maintains a WASM libmagic Node package ( https://github.com/moshen/wasmagic ) , I have to say I really love seeing new entries into the file type detection space.

Though I have to say when looking at the Node module, I don't understand why they released it.

Their docs say it's slow:

https://github.com/google/magika/blob/120205323e260dad4e5877...

It loads the model an runtime:

https://github.com/google/magika/blob/120205323e260dad4e5877...

They mark it as Experimental in the documentation, but it seems like it was just made for the web demo.

Also as others have mentioned. The model appears to only detect 116 file types:

https://github.com/google/magika/blob/120205323e260dad4e5877...

Where libmagic detects... a lot. Over 1600 last time I checked:

https://github.com/file/file/tree/4cbd5c8f0851201d203755b76c...

I guess I'm confused by this release. Sure it detected most of my list of sample files, but in a sample set of 4 zip files, it misidentified one.

We are very excited to announce the release of Magika our AI powered fast and efficient file type identification lib and tool - https://opensource.googleblog.com/2024/02/magika-ai-powered-fast-and-efficient-file-type-identification.html

Thanks to its optimized Keras model, large scale training dataset, and Onnx Magika massively outperform other file identification tools while be very fast even on CPU.

Magika python code and model is open sourced on Github: https://github.com/google/magika and we also provide an experimental TFJS based npm package https://www.npmjs.com/package/magika

With the team we hope you will find Magika useful for your own projects. Let us know what you think or if you have any question!

In my project[1], I convert all user-uploaded images to high-quality webp and store them like that. I discard the original files after the conversion. I use imgproxy[2] to further resize and convert them on the fly for actual display.

I don't do videos yet, but I'm kinda terrified of the idea of putting user-uploaded files through ffmpeg if/when I'll support them.

[1] https://github.com/grishka/Smithereen

[2] https://github.com/imgproxy/imgproxy

We use imgproxy which does 2->4 and all you need to do is change the URL on your site.

imgproxy interactive demo

You should also be using a variety of formats. Unless you need support for old browsers and transparency in the same image, don't use PNG. Stick with jpg, webp and avif. You can setup something like imgproxy to automatically resize and change format of images, or even fit into the space requirements you set.

If you look for something universal, you can try API for image optimization (e.g. imgproxy). However, the mechanism is different from build-time optimization.

Hey everyone, seeking some feedback about how to improve our project, imgproxy, an open source image processing tool.It’s designed to reduce costs and remove pricey requirements for all saved images to conform to specific formats. You can read the full list here if you’re curious: https://github.com/imgproxy/imgproxy In addition to crucial image processing stuff (like resizing, cropping, rotating), it can also sign urls, add watermarks, and a ton of other things.A ton of developers use it, and that’s great. We’re trying to improve it further, so wanted to put out the feelers and see if there is anyone using it (or a similar tool) who could suggest some additional features (or tell about the essential features of your current image processing tool).