Twitter | Search | |
mulander
Very creepy , someone was apparently typing in an URL and WhatsApp was fetching it off my server char-by-char
Reply Retweet Like More
gonzalo Jun 12
Replying to @mulander @WhatsApp
FB is good.
Reply Retweet Like
Rim Jun 12
Once more for the stupids, please: what does this mean?
Reply Retweet Like
b9AcE (Nazis off twİtter, return 140+name lengths) Jun 12
Replying to @traincrush @mulander
That WhatsApp (Facebook) leaks info about what you're typing to server admins, which could actually be private stuff… Not good privacy.
Reply Retweet Like
Rim Jun 12
Replying to @b9AcE @mulander
I use that shit for everythinnng
Reply Retweet Like
b9AcE (Nazis off twİtter, return 140+name lengths) Jun 12
Replying to @traincrush @mulander
You're on iPhone, so you can use The most basic tech-privacy mantra: Use Signal. Use Tor.
Reply Retweet Like
bmercer Jun 12
Replying to @mulander @WhatsApp
that really bytes!
Reply Retweet Like
Silverwizard Jun 12
Replying to @mulander @WhatsApp
That... is very much the wrong way to do URL previews....
Reply Retweet Like
Arjan Zuidhof Jun 13
holy crap, I just reproduced it on my own website. If this is by design I don't get it ;-/
Reply Retweet Like
Pan Yatsaman Jun 13
Not only that, but it also means that they try to access (and maybe parse, record and store) ANY web link you're sending through it
Reply Retweet Like
mulander Jun 13
It also allows metadata analysis of who communicates with who. For unique URL's you can time when it was sent and from where visited.
Reply Retweet Like
Pan Yatsaman Jun 13
It's just effing crazy. Why do we use encryption anyway? Let's go back to sending plaintext data 🤐
Reply Retweet Like
Arjan Zuidhof Jun 13
Replying to @xmjEE @mulander and 2 others
my issue w this behaviour is that you expect to have a private conversation, but you haven't. Scr*w the previews ;-)
Reply Retweet Like
Loran Kloeze Jun 13
Replying to @azuidhof @xmjEE and 2 others
Yeah, and besides that: simply because it's some kind of (needed) functionality doesn't make it less of a privacy violation ;)
Reply Retweet Like
👉 mstdn.io/@jomo Jun 13
Replying to @mulander @WhatsApp
Even worse, it fetches any meta property="og:image" tag with a very disclosing User-Agent:
Reply Retweet Like
👉 mstdn.io/@jomo Jun 13
Replying to @yatsaman @b9AcE and 2 others
The fetching is done on the client side
Reply Retweet Like
Pan Yatsaman Jun 13
Replying to @0xjomo @b9AcE and 2 others
Yes, I know that. But anyway it's VERY disturbing
Reply Retweet Like
👉 mstdn.io/@jomo Jun 13
Replying to @yatsaman @b9AcE and 2 others
Agree. I think I misunderstood your comment as that you would suggest they'd proxy the requests.
Reply Retweet Like
V U L P I N E   S P A C E  M O M Jun 13
It's owned by Facebook. Do you really think it's gonna be secure?
Reply Retweet Like
Pan Yatsaman Jun 13
Reply Retweet Like