partially. Telegram is currently inconvenient for exchanging images and videos, especially from mobile devices.
Describe the solution you'd like
Client-Server-Client side JXL. Client-1 encode, Server transfer to, Client-2 decode+encode to png or save in .jxl
By default send uncompressed or lossless compressed images in personal chats, add traffic saving mode for force compression.
Ideally complete replacement of jpg with jxl for lossless compression, or avif for force traffic saving.
Describe alternatives you've considered
don't see alternatives
Additional context
Regarding the first, since Telegram initially added the JXL decoder, and on the desktop it even works without additional settings, based on this you can add an encoder in lossless mode on the client side.
In addition to optimizing the traffic of TG servers, you can add a setting for saving in .jxl by a second client, which will give an impetus to support the format.
Remove image compression in personal chats/notes, this only spoils the images without much savings (most of the traffic comes from channels, or am I wrong?), at the same time, expand lossless images to full size (as is done with compressed ones), and add they have a postscript "lossless" or something like that in the upper corners. This is as funny as possible when a greedy discord with subscriptions for $10, and with file size restrictions, does not compress images/videos, but telegrams do.
Is your feature request related to a problem?
partially. Telegram is currently inconvenient for exchanging images and videos, especially from mobile devices.
Describe the solution you'd like
Client-Server-Client side JXL. Client-1 encode, Server transfer to, Client-2 decode+encode to png or save in .jxl By default send uncompressed or lossless compressed images in personal chats, add traffic saving mode for force compression. Ideally complete replacement of jpg with jxl for lossless compression, or avif for force traffic saving.
Describe alternatives you've considered
don't see alternatives
Additional context
Regarding the first, since Telegram initially added the JXL decoder, and on the desktop it even works without additional settings, based on this you can add an encoder in lossless mode on the client side. In addition to optimizing the traffic of TG servers, you can add a setting for saving in .jxl by a second client, which will give an impetus to support the format.
Remove image compression in personal chats/notes, this only spoils the images without much savings (most of the traffic comes from channels, or am I wrong?), at the same time, expand lossless images to full size (as is done with compressed ones), and add they have a postscript "lossless" or something like that in the upper corners. This is as funny as possible when a greedy discord with subscriptions for $10, and with file size restrictions, does not compress images/videos, but telegrams do.
Thanks.