Hacker News Reader

None of the mentioned tests had anything to do with directly testing power drain or low-power performance. He just thinks they aren't giving enough weight to battery drain as an undesirable side effect of features that don't directly benefit the user. That's it. That's his whole gripe. They're testing how fast an image loads, that uses up the user's battery, and that's bad for the user.

TFA literally says the battery drain was the purpose, not a side-effect:

   If you believe former Facebook employee George Hayward, a data scientist, Facebook can secretly drain the battery on its users' cellphones on purpose.

Okay, but the "you" in this sentence doesn't transfer to other readers. It's you when you read it, but when I read it, it's me. And I don't believe him.

> That document would presumably be subject to discovery in a lawsuit, although in arbitration it's unlikely it would be in the public record unless someone with standing made a freedom of information request (which may or may not reveal it).

Facebook doesn't retain documents for any significant period of time to the point where they lobotomize their own memory to avoid stuff like this in lawsuits (and to reduce costs of discovery).

Plus 2) would require additional design, engineering and QA work to implement the code to drain users' batteries. And it would cause plenty of users to uninstall/complain if Messenger was draining huge amounts of battery. It really doesn't make sense considering Messenger has 1.3 billion users, and remaining battery percent would likely be a bell curve across all users regardless of sample size.

Exactly, why don't just wait, this would make no sense from a risk rewards perspective

You want to test your app in negative scenarios, and one of them is "when and how to fail gracefully when battery is extremely low".

My phone rarely goes below 10%, and maybe it has seen 5% one or two times. If Facebook waits for that, they will never run the tests. But if they detect my battery is at 10%, then drain it to 3%, launch the controlled failure testing, then drain the phone to complete shutdown, on the next boot they have their very valuable data.

Or...buy some phones and run the tests yourself.

You could buy 100 iphones... Or you could "borrow" a million for free, to get rock solid stats.

Also there are hundreds, if not thousands, of different phone models. The allegedly used way of negative testing is much better than buying phones, and is virtually free.

I think Facebook Can afford to buy thousands of different phone models (and presumably already does?)

Handling low battery states isn’t exactly rocket science anyway. Do less computation. The rest is up to the OS.

"Borrowing" a million phones and draining their battery down would make increase the perception of your app draining batteries. Seems pretty dubious if you would be willing to do that just to get a bit better low battery prices.

It's also unethical.

Coming from a business whom founder said: "I have over 4,000 emails, pictures, addresses, SMS... People just submitted it. I don't know why. They trust me. Dumb f**s", ethical considerations has zero weight here.

Running that on end-user phones sounds wrong on so many levels.