Earlier quoted context omitted.
>they may store on servers behind the scene at least for speed and performance. Yes, that's why I think so. They easily loads all the messages and images in just few seconds even when my phone's internet is too slow. They won't let you use the web app when you're phone is disconnected, so there's no way to confirm it.
In order to use Whatsapp Web you need to be on the same wifi network as your phone. Your phone has the data on it. Intranet speeds on most wifi networks these days is faster than 50Mbps. That's more than fast enough to transfer all your messages and photos with little to no lag. It doesn't matter how fast your connection to the WWW is because you're not using the WWW to transfer the data, you're using the wifi intran…
Introducing WhatsApp's Desktop App
211–220 of 228 posts
Re: Introducing WhatsApp's Desktop App
#212Earlier quoted context omitted.
WhatsApp was bought for $19 billion. You could probably pay $1 billion and get a couple of different systems that worked well enough to replace WhatsApp.
Having read the engineering posts about their core systems I think you're being wildly optimistic in the same way as people who think "writing a general CMS can't be that hard, I'll just write my own" are.
Re: Introducing WhatsApp's Desktop App
#2131/ phone tethering is the price to pay for end-to-end encryption: the support of multiple devices is not compatible with perfect forward secrecy, as the former require the asynchronous push of messages to all devices while PFS requires synchronicity (at least some kind of, as explained in their white paper here: https://lobste.rs/s/sx2f0r/whatsapp_encryption_overview_tech... 2/ if you don't like the Desktop App (or a…
What did they use to make the desktop app, I wonder. Maybe _electron 1.0_?!?
Re: Introducing WhatsApp's Desktop App
#214Re: Introducing WhatsApp's Desktop App
#215Re: Introducing WhatsApp's Desktop App
#216Earlier quoted context omitted.
I think you misunderstood me. I was talking about MY case. Not "hundreds of millions of people"
" If the Whatsapp team actually tracked the rate of user engagement with these Desktop/Web editions & compared this to the Smartphone/Tablet apps. They would agree with you. " Surely you are talking about them tracking the rate of user engagement across their userbase, not just the data of you alone?
Re: Introducing WhatsApp's Desktop App
#217Earlier quoted context omitted.
That doesn't explain them actively blocking google voice numbers. Or home phone numbers (landlines) for that matter. Let people use a landline number on a tablet.
I've had it working perfectly well with my google voice number for years now. When did they start blocking it? The only problem I recall is that the initial text verification doesn't work - I had to do the phone call option - but this is a problem with gvoice, not WhatsApp: google blocks pretty much all server-triggered texts.
I don't have the slightest idea on how to fix it. The only reason it worries me a bit is that I might miss texts from other people.
Switched to an iPhone so I could use "Find Friends" with spouse and kids.
Re: Introducing WhatsApp's Desktop App
#218I was excited when I saw the headline but the phone teathering is a deal breaker. I removed whatsapp from my phone precisely because it took up too much space, with all the photos and videos being shared daily. It's a shame really.. a desktop app would've been a great alternative
An app without tethering would be great, I agree. But to save space on your phone, it's easy to turn off automatic storage of media, on iOS this is under Settings > Chats > Save Incoming Media. I've had it turned off for a long time to stop my camera roll filling with meme pics.
Re: Introducing WhatsApp's Desktop App
#219Earlier quoted context omitted.
Neither does iMessage store messages on servers, and yet I receive iMessages on every device I signed on.
But you can't retrieve historical iMessages on a new device.
Re: Introducing WhatsApp's Desktop App
#220Why is the app closing completely if I press 'x'? wouldn't be much better to stay in background mode like Slack does (well and many other chat clients)? It's annoying... I'll keep using my custom wrapper with NW.js (apparently this uses electron) until this behaviour is implemented...