On the one hand it provides a greater user-experience if Whatsapp can figure out the URL and preview information about the posted URL (like any social network does today, even we do it at STOMT when you attach an URL to your feedback). On the other hand i do not get why they send it after every character. Makes it even faster but creates a bunch of unnecessary requests. Not very user friendly. They could do it after…
“Someone was typing in a URL and WhatsApp was fetching it off my server”
11–20 of 69 posts
Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#12Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#13Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#14Seems like they need debounce? Most JS utility libraries (lodash, etc) have a debounce function...
Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#15Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#16Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#17Why is no one saying anything about end to end crypto?
Whatsapp shouldn't be able to see my messages, isn't that what they say themselves?
Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#18E: Disregard. Whatsapp is doing exactly what they should be doing. Telegram seems to proxy the requests. Why is no one saying anything about end to end crypto? Whatsapp shouldn't be able to see my messages, isn't that what they say themselves?
doing a GET request over the internet is already violating e2e
Re: “Someone was typing in a URL and WhatsApp was fetching it off my server”
#19E: Disregard. Whatsapp is doing exactly what they should be doing. Telegram seems to proxy the requests. Why is no one saying anything about end to end crypto? Whatsapp shouldn't be able to see my messages, isn't that what they say themselves?