search

hardcore-sushi / DroidFS

Encrypted overlay filesystems implementation for Android. Also available on gitea: https://forge.chapril.org/hardcoresushi/DroidFS
GNU Affero General Public License v3.0
612 stars 41 forks source link

Cannot share directly to secret chats in Telegram X #238

Open TippyLion28 opened 12 months ago

TippyLion28 commented 12 months ago

This is a really specific one and so far I've seen no actual proof myself that this is an issue. However when I share an image from DroidFS directly to a secret chat in Telegram X, the other person reports that the image does not display correctly (even though it appears fine in the chat history on my screen)

I have verified that sharing from other apps to Telegram X works fine, only DroidFS presents with this problem.

hardcore-sushi commented 12 months ago

What exactly do you mean by "does not display correctly"?

What version of DroidFS are you using? Did it work before version 2.1?

Does it happen with all images in different formats?

TippyLion28 commented 12 months ago

I can't easily show or describe it because I can't see it and the other person can't take a screenshot. Apparently it's blurry or showing as a solid colour. I am on version 2.0.2 and I can't speak for other versions since I only tried it on this version. The image format I tried to send was JPEG

hardcore-sushi commented 12 months ago

OK. Does it also happen with other image formats ?

It would be useful if both of you could download the file from the telegram chat to compare it to the original image stored in DroidFS (check file size, or better, compare the hash).

TippyLion28 commented 12 months ago

I just tested, it happens with PNG too. According to the other person, the image doesn't appear at all it's just an empty (large) chat bubble. When they tap to open the image it is just a blurry version of the sent image.

hardcore-sushi commented 12 months ago

OK, try to download the image files and compare hashes with something like this.

TippyLion28 commented 12 months ago

Surely they are guaranteed to be different regardless as telegram does its own compression when sending images?

hardcore-sushi commented 12 months ago

If it does, you should at least have the same hash as the other person. If they match, and the image appears correctly on your side then the issue comes either from Telegram or from the other person's device.

If you have a different hash than the other person, try to compare the hash from telegram on your side with the hash of the file contained in the DroidFS volume. If they don't match, the problem may come from DroidFS.