The ability to remove media compression

It’s been a long time since I asked you to remove the compression. I am faced with a problem once again, the quota for the mail limit is 45 MB, and the video or audio that I send weighs less than 45 MB, and it still compresses it just into useless information, the bitrate drops in the video and nothing can be seen, but the quality of the voice messages will be recorded. Well, please add the uncompressed function already, just in the settings you will be able to select the uncompressed option, what’s wrong with that?

1 Like

Кстати, так же касается сжатия аватарок контактов и групп, если честно не понимаю зачем это сделали, похоже что картинку кодируют в base64 и отправляют текстом. Но в чём проблема просто отправить её файлом?

После смены аватара создаётся список адресов кому аватарка была отправлена. Если контакта нет в списке, значит ему нужно отправить файл с аватаркой. После смены аватара, список стирается и всё по новой. Не вижу ничего плохого, если передать картинку размером до 500КБ, ну если например применить сбалансированое сжатие из готового функционала. А то порой на аватарке пользователя сложно догадаться девушка это или парень.

Hello :wave:,

In this case, it is better to send the video/audio as a file instead. Then the files are displayed in the chat as a video or audio message, but without compression. As far as I know, DC no longer has a limit on file size. The possible size is now only limited by the servers.

DC used to send the avatar images as attachments. Unfortunately, I don’t know why this was changed. As far as I know, the size is limited to 20 KiB, which is often too small for photos.
Perhaps it would be better to send the images as attachments again or at least significantly increase the permitted size in the header.

Hello :wave:

Я соглашусь, что со стороны DC ограничения на размер вложений нет, всё зависит от сервера, я на своём это ограничение убрал. Но дело тут в сжатие на стороне клиента. Зачем DC сжимает, если ограничения действуют на стороне сервера, смысла я не вижу. Я понимаю, что не каждый может убрать ограничение или сжать файл, и знаю что через файл можно отправить без сжатия, но это слегка не комфортно. Что касается решения, оно очевидно, делать в настройках сжатия функцию «без сжатия медиа» причём голосовое сообщение должно входить в эту функцию. А что касается аватаров, то тут однозначно нужно либо поднять это ограничение, либо вовсе убрать.

please speak in English so more people can understand and comment, alternatively, there is a Russian category where your can speak Russian, thanks

1 Like

I support a statement that DC should take to introduce more customization for media compression. For example, I prefer to send photos without compression and almost any e-mail provider can pass such an attachment. So, it would be better to have a level of media compression customizable for user and their needs.

1 Like

This is another update, as always very good, but it would be great if there was an item without compressing media files, which many have been waiting for a very long time. Well, there are already 2 points, well, add 3, I don’t think it’s that difficult. Please dear developers, hear me out.

feat: Send Chat-Group-Avatar as inline base64 (#5253) was done at 2024-02-24 23:24:04, but it only changed behaviour for group avatars, for users’ avatars that was done years ago and even i don’t know for sure, but sending any special data in the headers looks more straightforward.

There’s a comment in the code:

// max_bytes is 20_000 bytes: Outlook servers don't allow headers larger than 32k.                                                                                                                           
// 32 / 4 * 3 = 24k if you account for base64 encoding. To be safe, we reduced this to 20k.

but it doesn’t look very relevant as nowadays Delta Chat always sends the avatar encrypted if the message is encrypted. So in fact the limit can (and i think, should) be increased to the same value as for attached images, i.e. 500 KB, for encrypted messages, even base64 encoding doesn’t matter because of the PGP compression (though i haven’t done any measurements).

1 Like

Sending as files should already send them without compression. If not that would be a bug.

I would also like to have an easier option in the ui to decide whether I want to send images compressed or not.
On iOS sending an image as a file is very cumbersome, because you first have to go to the gallery app to export it to the Files app and then you can select it as a file in delta chat.
On android it might be easier as (at least some variants/versions) also show a gallery in the file picker.

1 Like

I meant the attachments in the email. It’s just a condition, the variable is set as not to touch the attached files, and then the execution of the function. At the expense of sending avatars with files, they have long wanted to implement, I do not know what they are dragging their time. After all, the same avatar will be sent as a file in an email, with the transfer of the first encrypted email.

Made a PR for this: feat: Send avatars as large as usual images when possible by iequidoo · Pull Request #5863 · deltachat/deltachat-core-rust · GitHub.
EDIT: But larger avatars will be sent only in protected chats, in unprotected ones E2EE isn’t guarateed, so seems it isn’t worth refactoring the code to try to send larger avatars if a message is going to be sent encrypted.

2 Likes

Avatars are not sent as images anymore to avoid them being displayed as attachments in non-deltachat clients. Some users use Delta Chat to send messages to non-Delta Chat users or reply to emails and having an attachment with some random picture is not nice.

3 Likes

Communication between the interlocutors in encrypted form proves that both have a DC client, so why not send an avatar with a high-quality attachment along with the first sending of an encrypted message. And again after the change with the same condition

If the message is encrypted image may as well be sent in the header section regardless of its size. There is no reason to send it as an attachment in this case.

I don’t understand a bit, so is there a problem? Or has it already been solved? Is it worth coming up with an algorithm further, basically this topic concerns the compression of sent attachments in correspondence, and not about the avatar, I would like to know how things are in this direction.

1 Like

Basically you can send “as file” to send without compression.
But that’s not very accessible nor user friendly UI/UX, especially on iOS.