NoSleep.js

Indeed. I work on the Firefox media stack and we have been grabbing wake locks when video playback is happening for a long time. Occasionally e.g. on some linux desktop variant this has malfunctioned and we're alerted in no time and fix it. The Wake Lock API is for other use cases, such as recipe websites, or other document for which you don't want the screen to go away / dim, the kind where you happen to need to look at the screen for long period of time without touching it/interacting w/ mouse and keyboard. Prior to this API being introduced, websites used to play an inaudible/almost invisible looping media file to keep the screen awake. This has power usage implication, a small single digit number of watts (1 to 3.5 depending on os, hardware, mobile or not) is required to keep audio running (because of high priority threads, frequent w

Awesome project! Reminds me of donothingfor2minutes.com from Calm, but with a different end goal of focus instead of calm. Regarding mobile phones going to sleep, Wake lock [1] might help, unless you can reduce to 59s since I believe 1m is the threshold (make sure to request within the context of the user hitting "start"). Unfortunately on older mobile browsers [2], the best workaround I found was using this NoSleep library[3]. Source: ran into this same issue when building https://www.phonefreehour.com [1] https://developer.mozilla.org/en-US/docs/Web/API/WakeLock [2] https://caniuse.com/wake-lock [3] https://github.com/richtr/NoSleep.js

When I'm stuck on coding something, I find myself reaching for my phone even if I don't have any particular reason to do so. Inspired by Calm's DoNothingFor2Minutes.com which launched on HN 13 years ago [1], I made this simple webapp to see if my friends and I could go an hour without touching our phones. It is surprisingly difficult. According to a 2022 survey [2], the average US adult picks up their phone 352 times per day, or approximately once every 2m43s while they're awake. On browsers that support it (iOS 16.4+, most versions of Android Chrome), it uses the Screen Wake Lock API [3] to keep the page open, and falls back to nosleep.js [4] otherwise. From testing on my iPhone 14 Pro Max running iOS 16.6, battery life only went down 3 or 4 percentage points after an hour with the wake lock. Made this as a web app as a quick demo to be

According to a 2022 survey [1], the average US adult picks up their phone 352 times per day, or approximately once every 2m43s while they're awake. Inspired by Calm's DoNothingFor2Minutes.com which launched on HN 13 years ago [2], I made this simple webapp to see if my friends and I could go an hour without touching our phones. It is surprisingly difficult. If you're reading HN on your phone, definitely give it a shot. On browsers that support it (iOS 16.4+, most versions of Android Chrome), it uses the Screen Wake Lock API [3] to keep the page open, and falls back to nosleep.js [4] otherwise. From testing on my iPhone 14 Pro Max running iOS 16.6, battery life only went down 3 or 4 percentage points after an hour with the wake lock. Made this as a web app as a quick demo to be compatible across all mobile devices. As an app, we can probab

https://github.com/richtr/NoSleep.js/ I wonder if something like this will get "extended" to work for desktop browsers now if this needs to become more popular? I think something simple like looping an empty audio or video file will suffice. Not that I agree with that from a "hijack the user's browser without their consent" perspective. Just spitballing workarounds.

Looks like a restyled https://richtr.github.io/NoSleep.js/example/ but in the source I can't see the patch applied that makes it actually work on Safari v15 and higher https://github.com/richtr/NoSleep.js/issues/135

As Firefox (& I think Safari too) does not support the ScreenWakeLock API are you using NoSleep.js? https://github.com/richtr/NoSleep.js This library implements a hack and plays a very tiny video in a loop too. This should even work on mobile devices and (according to my personal&tiny tests) is not that inefficient as it sounds :)