For that use case we have Tiff with float and lossless compression.

https://gdal.org/en/stable/drivers/raster/gtiff.html

That is true but you can determine a baseline from Tiff.

In the GIS world we have a Cloud Optimized Geo Tiff. It is almost a standard now. This better than go to another format like Jpeg2k or ECW.

Tiff is an extendable format. Bit I am not saying that it can be better than JpegXL. Just a curiosity.

I just found this video on YouTube now:

https://youtu.be/A8fDr7Rr7yM?is=cHwOQVrli9oXLdqY

That doesn't show this project.

Open to see what it was about, stayed for the banger soundtrack

Rainfall

And at least the forest soil has the same amount of carbon stored.

I usually like to write elegant code using Python and frameworks like Django.

The pleasure comes from the "the only right lines of code" instead of "the most lines of code".

Nice advice

More info here:

https://x.com/ayubio/status/2068195735279923267?s=20

Everyone in Brazil capital cities are receiving extreme alert messages with just the text: "misanthropi"

I would use a hash of the body content (the query) as a URL parameter

/?hash=123456789

Why? That's pushing more work to do both on yourself and the cache.

Actually this is a use-case supported by this RFC [1]. You accept an arbitrary QUERY /search/ and you cache it on your side (or in a middle box somewhere such as a CDN edge) you can return in your response:

    Location: /search/?queryHash=SOMECDNHASH

The browser can then cache that Location and the next time convert that same QUERY /search/ into GET /search/?queryHash=SOMECDNHASH.

Sure, it is more work for your webserver to compute that and potentially the browser to cache it's knowledge of that QUERY, but it potentially gives you an advantage in keeping things like CDN edge caches generally aware of client/browser caches in a way that can be performance optimized.

[1] https://www.rfc-editor.org/info/rfc10008/#section-2.4