Cryptocurrency donations for bots, groups and channels
Show a button for sending quick donations to maintainers of bots, groups or channels using cryptocurrency. This could use either an established cryptocurrency like Bitcoin, Etherium, EOS, etc. – or some…
⑨ Auxiliary channels are supported. They are useful when thermal imagery is to be stored alongside the regular photo, or when a depth map is available, etc.
The suggestion here is to support JPEG XL images absolutely everywhere in Telegram (in albums or single pictures, in stickers, in avatars, in thumbnailed uncompressed files, on Instant View pages, in preview areas under messages hyperlinked to external JPEG XL files or to JXL-featuring web pages, in preview areas under messages hyperlinked to other messages that contain JPEG XL, in uploads on Telegraph pages, in the results of external-URL-to-embed transformations on Telegraph pages, etc.), and to refrain from any automatic JXL-to-JXL recompression (see https://xkcd.com/1683/ for the rationale), and to refrain from imposing stricter limits (5 MB PNG are allowed on Telegraph pages → 5 MB JPEG XL should be allowed).
The implementation of this suggestion is expected to be delayed until the web browsers start supporting JPEG XL for real (right now their implementations are hidden behind flags in options, see https://caniuse.com/jpegxl for details, also see https://i.redd.it/s3l1g2b40jt61.png and https://i.imgur.com/ezQPsaW.png for the examples).
WebP and AVIF aren't better than JPEG XL.
They cannot compress old JPEG files losslessly (and thus they don't offer lossless decompression back to JPEG).
WebP does not support deep colors (only TrueColor). Chroma subsampling 4:2:0 is mandatory in lossy WebP files.
AVIF does not offer good lossless compression at all. Lossless WebP files are smaller than lossless JPEG XL only when a screenshot of ClearType text is compressed (an example of such screenshot is attached below).
Lossy WebP files are worse (in terms of quality-to-filesize ratio) than either AVIF or JPEG XL. Lossy AVIF files can be better than lossy JPEG XL files when both are compressed below 1 bit per average pixel (especially below 0.5 bpp), worse otherwise.
WebP files cannot be displayed progressively (only top-to-bottom). AVIF files currently do not offer even top-to-bottom progression and thus they have to be entirely delivered before they are displayed. (Future AVIF encoders and decoders may offer several layers of progression.) Lossy JPEG XL files are always progressive.