WhatsApp Begins Rolling Out End-to-End Encrypted Backups on iOS and Android

Facebook has announced that it has now begun rolling out End-to-End Encrypted Backups on iOS and Android devices.

Starting today, we are making available an extra, optional layer of security to protect backups stored on Google Drive or iCloud with end-to-end encryption. No other global messaging service at this scale provides this level of security for their users’ messages, media, voice messages, video calls and chat backups.

You can either set your own password, or let WhatsApp automatically generate a 64-digit encryption key on your device.

Whatsapp End-to-End Encrypted Backups

Facebook was under a lot of pressure in recent times to introduce this feature, so I’m glad to see it finally arrive now. Considering it has more than 2 billion users, this will be a slow rollout, starting with those who are running the latest version of WhatsApp on iPhones and Android devices. If you see this option, make sure to flip the switch right away.

The folks at Cloudflare have published a fascinating look into the recent ~6 hour long downtime that the Facebook network went through, taking down not just the Facebook product itself, but also WhatsApp, Instagram, FB’s internal looks, and a lot more. It’s a somewhat technical explanation, but Cloudflare’s Tom Strickx and Celso Martinho have made it very easy to understand.

Today at 1651 UTC, we opened an internal incident entitled “Facebook DNS lookup returning SERVFAIL” because we were worried that something was wrong with our DNS resolver 1.1.1.1. But as we were about to post on our public status page we realized something else more serious was going on.

Social media quickly burst into flames, reporting what our engineers rapidly confirmed too. Facebook and its affiliated services WhatsApp and Instagram were, in fact, all down. Their DNS names stopped resolving, and their infrastructure IPs were unreachable. It was as if someone had “pulled the cables” from their data centers all at once and disconnected them from the Internet.

How’s that even possible?

It’s really interesting to see how a (possibly) minor piece of code can take down large parts of the internet like this. Honestly, it would be a good thing for the internet overall of Facebook disappears from the internet, but I feel for everyone at Facebook behind this issue. Major hugs to the people involved in bringing the network back up.

Then again, imagine messing up so bad that your boss ends up losing $6 billion.

Mike Isaac, reporting for The New York Times:

The lawsuit, filed by WhatsApp in the Delhi High Court, seeks to block the enforceability of the rules that were handed down by the government this year. WhatsApp, a service owned by Facebook that sends encrypted messages, claimed in its suit that the rules, which were set to go into effect on Wednesday, were unconstitutional.

Yes, Facebook is evil, but the current Indian Govt. is riding the same boat. It’s good to see WhatsApp challenging these ridiculous new rules (may even be unconstitutional), and I hope other companies join the suit.

That said, this doesn’t absolve WhatsApp from their new Privacy Policy changes. Scumbags.

WhatsApp Processes 18B Messages on Dec 31st

WhatsApp, arguably the most popular cross-platform messaging service out there today processed a record 18 BILLION messages on a single day on December 31st, 2013. That’s 7 Billion inbound and 11 Billion outbound messages.

If you’re wondering why the number of inbound and outbound messages is not the same, WhatsApp explains:

[…] difference in inbound vs. outbound is due to group chat. sending one msg into group chat of 10 people is 1:10 inbound:outbound

That is an interesting logic they follow there. To me, when a group message is sent out, a single message goes out but is instead is being delivered, independently, to multiple different devices and users. So that’s 1 outbound message but multiple inbound ones.

That said, that’s an insane amount of messages for a single day. Hats off to their engineering and ops team for this.

[via @sathyabhat]