androidclient
androidclient copied to clipboard
Send any file type
From [email protected] on March 23, 2013 21:05:11
Implement some safe method to receive any type of file, with warnings to the user about potentially dangerous files.
Original issue: http://code.google.com/p/kontalk/issues/detail?id=36
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
From [email protected] on February 25, 2014 22:48:13
The only messanger which can do this already is Telegram, afaik. This would be another very unique feature. Btw. they do not warn anyone of anything.
Could sharing of files in the audio/3gpp format be done earlier? Currently, Kontalk won't accept such files, which means that audio recorded from inside Kontalk cannot be shared.
Yes, it could actually. I'll keep a note of that.
This issue is labeled with Milestone 4.0 But there is no open issue?!
No this is actually labeled as Future, it was the old 4.0 milestone which got renamed but github probably didn't get that.
Would it be a idea to compress file as zip or tar before send it and unzip after receive? This way, we need only one file transfer to implement.
Or is this too dangerus because I could mask bad files?
Besides security, the content is the one that needs to be handled, not the container. We could use zip or gzip for compression, but the content must be handled differently.
I'm still not really keen to support really any file type in a mobile device, since is a much more exposed platform than a desktop platform IMO. I suppose I could implement a "block unknown file types" preference enabled by default.
Well, I don't think that's necssary, anyone who want's to harm others would find an excuse for the victims to turn that oprion off and it's been shown that even images are quitr harmful for Android phones, though I'm not sure if the article I read about included HTML interpreters only.
On November 28, 2017 10:48:31 AM GMT+01:00, Daniele Ricci [email protected] wrote:
Besides security, the content is the one that needs to be handled, not the container. We could use zip or gzip for compression, but the content must be handled differently.
I'm still not really keen to support really any file type in a mobile device, since is a much more exposed platform than a desktop platform IMO. I suppose I could implement a "block unknown file types" preference enabled by default.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kontalk/androidclient/issues/26#issuecomment-347469256
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.