News for hackers. Stuff that matters.
Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @09:11AM (#12209648)
This was a terrible idea from the start. In the best case scenario, what is supposed to happen? The sites I visit suddenly start being served as shells of their former selves in order to save the compute cost of rendering them? Web designers are supposed to figure out an entirely new design mode for the whole site to cater to visitors with low batteries?

Now back to the real world, where many sites I visit peg my desktop CPU trying to serve so many ads and so much tracking to squeeze every possible cent of profitability from my visit. If there's a war against ad-blockers, did we think these sites would relent and say, oh, OK, I see you might be low on battery, I'll serve just the content you want this time?!

No, this is a purely client-side concern, with plenty of purely client-side mitigation which can be put into place. That the protocol actually specified 14m degrees of granularity -- from what at the very least ought to have been a binary setting -- makes me wonder if the point wasn't user tracking all along.

Missing from the article: Do all user agents actually provide this information in request headers? Is there a way to shut it off?

Re:Your battery status may be used to track you online by DougWebb on Tuesday August 02, 2016 @09:32AM (#12209779)
As a web application developer, one idea that comes to mind is that, if I were writing an app that supports offline usage, I'd probably want to be aware of a low battery situation so that I can save my state and warn the user that the app needs to shut down to avoid data loss. I might also switch from online mode to offline mode, again letting the user know (and letting them override the choice, maybe.)

I can't see any reason to make use of the battery status server-side. But, there's also no way to prevent the information from being sent, once you make it available to javascript code on the device. If the standard api didn't send it, then you'd just see ad-hoc apis gathering the data locally and sending it.

Re:Your battery status may be used to track you online by DashRattlesnake on Tuesday August 02, 2016 @10:34AM (#12210233)
However, I don't think the battery state needs to be as granular as it is to support those use-cases. A simple boolean hasLowBattery or a much coarser 0%-25%-50%-75%-100% enumeration seems like it would have been sufficient.
Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @11:01AM (#12210432)
If anything, I would propose the mode should be a user-controlled bit called simply: "LOW"

Maybe I request low mode because...

  I hope you serve me less crappy ads
  I haven't bought a new phone in 3 years
  I am running other apps which need more CPU
  I find too much interactivity distracting or confusing
  I just want to read black text on a white background
  I hate your website, but need to visit it for some reason anyway
  ...
  I have full battery, but I need to conserve it
  I have low battery
EDIT: Fuck, I just realized, this already exists, and it's called NOSCRIPT. Wait, we could call this LOWSCRIPT!
Re:Your battery status may be used to track you online by vmateixeira on Tuesday August 02, 2016 @11:28AM (#12210640)
So much truth in here... this proposal would be very welcome!
Re:Your battery status may be used to track you online by bentruyman on Tuesday August 02, 2016 @11:29AM (#12210646)
Good luck defining "low". Also, coarse percentages of charge provide no indication of the amount of time left of a battery based on current activity. Which is something you would need in the above offline/save example.
Re:Your battery status may be used to track you online by DougWebb on Tuesday August 02, 2016 @03:35PM (#12212663)
Maybe a boolean would work. I don't think 0%-25% would work for the scenario I described; 0% is too late to do anything about the low battery situation, and 25% is too soon to worry about it.
Re:Your battery status may be used to track you online by vmateixeira on Tuesday August 02, 2016 @10:59AM (#12210418)
...warn the user that the app needs to shut down to avoid data loss..

Doesn't the client (laptop, phone, etc) does this already?

Re:Your battery status may be used to track you online by DougWebb on Tuesday August 02, 2016 @03:42PM (#12212721)
I've seen my devices give notifications about the battery level to me, but I don't think they notify the apps I'm running, and if I ignore the notifications until the battery dies the device just shuts down. The apps have no chance to save their state.

Often, that's probably just fine. But if I'm developing an app and I have a requirement to save state before my app gets shut down due to power failure, this api will allow me to do that. It's the equivalent to a drive flushing any writes before shutting down; normally they'd get flushed sooner or later, but if you have to shut down NOW, you'd better flush now too while you can.

Re:Your battery status may be used to track you online by vmateixeira on Wednesday August 03, 2016 @04:05AM (#12216398)
I mean, but if the device notifies you that it's running low on battery... maybe you should close the app? Shouldn't this be enough?

You would avoid loosing data, and regarding user experience, also avoid a slower performance of your app (and perhaps complaining about it?), and also seeing your device shutting down itself with your app screen running in background (which is pretty lame).

Re:Your battery status may be used to track you online by DougWebb on Wednesday August 03, 2016 @12:31PM (#12219199)
As a user, maybe that should be enough. Maybe not. It depends on the app and how critical the data/state is, I guess.

As a developer, trying to implement requirements set by a product designer/owner who thinks saving the data is critical even if the user doesn't cooperate, the api is useful to have.

Re:Your battery status may be used to track you online by vmateixeira on Thursday August 04, 2016 @06:07AM (#12224509)
Maybe a critical app shouldn't be web based?

If you're really worried about your battery running low and working with critical data, removing the browser overhead which is draining you battery should be one of the first things to do.

Re:Your battery status may be used to track you online by aeorgnoieang on Tuesday August 02, 2016 @11:37AM (#12210711)
> But, there's also no way to prevent the information from being sent, once you make it available to javascript code on the device.

Surely it's possible for JavaScript engines to either (a) optionally prevent code from accessing this; or (b) return random nonsense, or even just a single fixed static value (for every instance of the engine anywhere).

Re:Your battery status may be used to track you online by DougWebb on Tuesday August 02, 2016 @03:39PM (#12212690)
Nope; either the information is not available to Javascript code at all, or the Javascript code can do whatever it wants with the info.

A security permission, or config setting, can/should be used to prevent access to the api that returns the battery level. But once access is enabled, there's no way to prevent the code from getting the level (which is just a number) and sending it to a server (which is just calling an ajax request with a numeric argument.)

Re:Your battery status may be used to track you online by Mister_Snuggles on Tuesday August 02, 2016 @11:49AM (#12210783)
I would think that if you architect your app to handle disappearing network connections gracefully, it will probably handle the user shutting down the phone gracefully too. If the battery is critically low, the user will get popups from the operating system at various points and can make a decision whether or not to keep using your application.

You could also expose an offline-only option somewhere in your application. A user might want to do this if they are in an area with marginal coverage (e.g., there is a connection, but it's basically useless) or roaming, etc.

Re:Your battery status may be used to track you online by DougWebb on Tuesday August 02, 2016 @03:46PM (#12212741)
A disappearing network connection is a different case, because the app continues running. Imminent power failure is different because the app is about to be terminated, probably not gracefully. This is also different from the user shutting down the app manually, because that's probably a graceful shutdown which will give you a chance to save some state before termination.
Re:Your battery status may be used to track you online by mikeash on Tuesday August 02, 2016 @01:47PM (#12211677)
The user can close your page at any moment, so you need to design your web app to save data continuously and automatically anyway.
Re:Your battery status may be used to track you online by andybak on Tuesday August 02, 2016 @09:38AM (#12209814)
> Web designers are supposed to figure out an entirely new design mode for the whole site to cater to visitors with low batteries?

You're constructing an obvious straw-man here. It's easy to imagine scenarios where a 'low power mode' would be in the interest of the site and it's visitors. Especially when we're talking 'apps' rather than 'content sites' - there's plenty of desirable but non-essential functionality that could be disabled and for web apps intended for mobile use this could potentially be a great differentiator.

Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @10:15AM (#12210068)
I think you're fighting straw with straw. Think about the development and testing costs of trying to add the functionality and have it work across a host of devices.

Again, there's a litany of things a device can do to reduce power usage itself. Native apps and websites alike should absolutely consider their power profile and reduce it if possible.

The idea which I think is terrible is making this part of unrestricted Web API as 14m possible states. But even as a binary state I think very few apps have the resources to design, develop, and test across multiple devices for dynamically adjusting power consumption.

Re:Your battery status may be used to track you online by andybak on Tuesday August 02, 2016 @10:23AM (#12210132)
> Think about the development and testing costs of trying to add the functionality and have it work across a host of devices.

1. Simple example - any app that does polling for any reason can reduce the polling interval.

2. Interactive WebGL charts could be replaced with static bitmaps

3. Background spell or syntax checking could be disabled and made 'on demand'

4. Chatty network features could be disabled or cut back.

None of the above need to significantly increase development or testing costs. They are quick examples I pulled out of thin air. If we discussed specific applications I'm sure I could suggest more.

Non-browser apps already can do all this and often do. (and I wish they would do it more often)

Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @10:46AM (#12210312)
I guess the way I think of it... if I am visiting a site or web app, I am actively opting to expend the energy required to render the page. Obviously if the page is not visible, and not doing a background task like playing audio, then I expect its CPU consumption to be negligible. So, first and foremost, use the page visibility API.

If I'm low on battery and choose to open that webpage, and now the WebGL charts are static bitmaps, my first reaction is going to be WTF. Now I want a button synonymous with 'Show Desktop Site' -- I guess we could label it the 'Stop Fucking With Me' button.

All code should be aware of the CPU that it is consuming. More efficient code is not just better for battery, but also likely more responsive and better for multitasking. So the question becomes, not how do we reduce CPU and possibly even improve UX, but in what cases would we make the CPU requirement dynamic, and when/where might the trade-offs be made to ultimately improve the user experience.

So first is Page Visibility, as discussed. The very next area where I would consider making CPU usage dynamic is not a battery state, but rather it's an overall device performance adjustment. If someone visits with an iPhone 4 versus a 6s, they have dramatically different amounts of compute available. I would consider investing in dynamic CPU consumption based on a device performance flag a lot sooner than I would do it based on remaining charge, because I think it would improve the UX for a large percentage of users every time they used the site. It's also a static setting from the perspective of the device owner, so they are not seeing changing UX on their device potentially from one moment to the next.

> None of the above need to significantly increase development or testing costs.

I can only offer my opinion based on my experience, but trying to alter functionality to reduce CPU load based on dynamically changing battery metrics across a pool of devices which may behave inconsistently... this is really not simple to code and test and maintain over time. We have a hard enough time just trying to efficiently serve device-specific assets (like lower res images to mobile) and that's based on a static/fixed user-agent string, not a dynamic header, and sites get it wrong so often that user-agents added a special button to try to turn it off!

Re:Your battery status may be used to track you online by josho on Tuesday August 02, 2016 @11:00AM (#12210429)
I agree with your sentiment. However, I also appreciate the web maturing and giving developers similar API abilities as a native app. The API may not have a use for you, but surely across the global audience of web apps there will be more than a few valid use cases.
Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @11:19AM (#12210567)
This is a great point, and I too tend to think in terms of the Web API having parity with native can only be a Good Thing.

The problem is the web is not a very nice place, and (like the ad networks mentioned by the OP) third parties beyond my control often get to run fully-scoped Javascript on my browser. OTOH, at least I get to choose which apps are installed on my home screen.

So I wonder if instead of all the prompts we have today;

  Would you like to allow this page to see your location?
  Would you like to allow this page to use your microphone?
  Would you like to allow this page to use your camera?
  Would you like to allow this page to send notifications?
  Would you like to allow this page to view your battery status?
We need something more holistic. I joked above about NoScript vs. LowScript. I was chuckling to myself imagining a 3-way toggle -- NoScript, LowScript, and YoScript.

There certainly could be use cases for having a comprehensive Web API for charging status, battery capacity, remaining charge, and time till charged. Someone will find this useful. But simply adding it and having it on-by-default is not without tradeoffs...

As Web API matures, there is a plethora of APIs which have privacy concerns, some slight, some grave. We need to communicate to users these trade-offs in some usable way, and give them some control over them. Some APIs definitely need their own unique Yes/No prompt, like turning on my camera/mic, but I wonder if there's a middle-ground of a group of APIs which should be restricted all behind a single setting, akin to favoriting or 'staring' the site gives just that first-party domain access to those APIs. Maybe we even call it "Native Mode", then we put choice back in the hands of the user and we can expose APIs with impunity.

Re:Your battery status may be used to track you online by majewsky on Tuesday August 02, 2016 @09:45AM (#12209864)
The most obvious thing is animations. Android has a powersave mode where all animations are disabled. (It's a bit unsettling, actually, but really helps with conserving the few remaining electrons.)
Re:Your battery status may be used to track you online by m_eiman on Tuesday August 02, 2016 @10:05AM (#12209996)
Sounds like something for the browser to handle automatically, without the site's javascript ever knowing about it.
Re:Your battery status may be used to track you online by andybak on Tuesday August 02, 2016 @10:17AM (#12210083)
How does a browser distinguish between essential and non-essential animations?

(If your answer is 'there are no non-essential animations' then you haven't thought about it for long enough)

Re:Your battery status may be used to track you online by nommm-nommm on Tuesday August 02, 2016 @10:24AM (#12210135)
What's an example of an essential animation?
Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @10:56AM (#12210395)
I think it's way past the point of diminishing returns, but the answer to your question is: with more markup.
Re:Your battery status may be used to track you online by nommm-nommm on Tuesday August 02, 2016 @10:21AM (#12210109)
Then you confuse the users by displaying some of the content only some of the time. Mobile sites are already crippled in functionality so I can't imagine them being crippled more being a good thing.
Re:Your battery status may be used to track you online by dspillett on Tuesday August 02, 2016 @09:40AM (#12209833)
> In the best case scenario, what is supposed to happen?

I assume it is intended for mobile apps written in-browser that are intended to run in some sort of kiosk mode so obscure the OS's default battery display.

Re:Your battery status may be used to track you online by brlewis on Tuesday August 02, 2016 @09:37AM (#12209804)
E.g. weather app that automatically fetches new weather data periodically, but stops when battery is low. That said, you're right that the only data you need for such purposes is binary. The current API provides too much info.
Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @10:24AM (#12210133)
If it's a native app, then it can already do this. If it's a web app, then hopefully it's only fetching updates if the tab is visible, right? I absolutely think web apps should be checking if their tab is foreground and behaving differently based on that.
Re:Your battery status may be used to track you online by brlewis on Tuesday August 02, 2016 @11:09AM (#12210485)
What if I want a notification that rain is coming? https://developer.mozilla.org/en-US/docs/Web/API/Notificatio...
Re:Your battery status may be used to track you online by zaroth on Tuesday August 02, 2016 @11:27AM (#12210635)
So what you're saying is that on top of having to deal with low battery, now you're also getting caught in the rain? :-)

Don't tell Steve, but if I want to save battery, I swipe closed the browser. If I sign up for rain notifications, I better get my darn rain notification!

Re:Your battery status may be used to track you online by brlewis on Tuesday August 02, 2016 @12:09PM (#12210946)
No, I'm not talking about low battery. You suggested that the app stop checking for weather updates when its tab is not in the foreground. If I do that then I get caught in the rain even with a full battery.
Re:Your battery status may be used to track you online by x1798DE on Tuesday August 02, 2016 @02:22PM (#12211986)
Hopefully browser tabs don't have any way of triggering system notifications, in which case how would it matter if a webapp stopped automatically updating when the window loses focus?
Re:Your battery status may be used to track you online by Retra on Tuesday August 02, 2016 @10:23PM (#12215142)
How's it going to notify you if you're not looking at the web page?
Re:Your battery status may be used to track you online by brlewis on Friday August 05, 2016 @01:06PM (#12233989)
See my link above to the notifications API.
Re:Your battery status may be used to track you online by drzaiusapelord on Tuesday August 02, 2016 @10:43AM (#12210295)
>This was a terrible idea from the start. In the best case scenario, what is supposed to happen?

I see two scenarios here:

1. The usual cock-up of the API guys not being the privacy/security guys and managers being unable to find common ground between the two.

2. The pressure to make HTML5 be an "app killer" and making sure devs have everything they need to write HTML5 web apps that can compete with native apps. Security/privacy becomes a browser problem, and if the browser guys screw up (see 1.) then too bad.

Seems to me, a simple middle ground of reporting a less granular battery value would have made sense. Very Low, Low, Medium, High, Very High would probably take care of it. You can probably just shoe-horn this in right now by just assigning a number to each condition and never telling websites the real number (or randomizing it a bit).