4 ms·

Why not just use keep awake? https://chrome.google.com/webstore/detail/keep-awake/bijihlabcfdnabacffofojgmehjdielb?hl=en https://chrome.google.com/webstore/det

• tailspin2019 4y ago
  Why not just use nosleep.page? https://nosleep.page https://nosleep.page
• 40four 4y ago
  I can think of a few reasons. Looking at that page, the extension seems to only be compatible with Crome OS. A pretty limited audience can use that. Also, I assume this is a pet project of the author. They had a need, and found a way to solve it. They probably had fun, and learned some things along the way. Often, that’s kind of the whole point of a weekend project. Even if there is another established solution, ‘Why not just … some other thing’ isn’t great feedback. Discovering people’s ideas and projects is one of the beautiful things about HN. This is a perfect example. I didn’t even know the Screen Wake Lock API existed, so I learned something new!
  • mrep 4y ago
    It has worked on every OS that has chrome that I have used and takes like 30 seconds to install. It is easier to click a chrome extension to stay awake than go to a webpage in my opinion. You do you though
    • 40four 4y ago
      Hey fair enough. Good to know. But you’re the one who asked ‘why’? I guess you thought that was rhetorical? :) I was just going off the docs which specifically mention Chrome OS and Chrome-books. Personally, I’ve never really had a use case for something like this. My only point is, I still applaud the author’s effort here, and it taught me something new about Web APIs. It’s interesting that you can do that at all with a web page!