amacfie / human_powered

Chrome extension that periodically prompts the user to do a stretch/exercise/posture check. Uses pose estimation via webcam. Runs after e.g. every 5ᵗʰ new tab opened.

Human Powered

Dev install: Clone then follow instructions here

icon from https://freeiconshop.com/icon/lightning-bolt-icon-outline/

alternatives:

• https://github.com/meko-deng/sit-better-extension

human_powered's Issues

Options are lost when Chrome is updated

Upgrade manifest.json to Manifest V3

indicate when it's disabled

pretty complicated

Misc

set 1

• disable closing the page, never open twice?
• handle error if webcam in use
• docs/instructions
• allow user to set constants
  • see guide
• uncomment popup in manifest and use it for something. e.g. "disable for x hours" (see tutorial)
• basic scheduling

set 2

• advanced scheduling
• pose tags, enable/disable by tag
• perf improvements
• choose canvas size according to webcam resolution. this may affect distance
• other triggers
• switch to bodypix?
• allow doing a bunch of poses in a row to charge for a while
• allow sequences of poses, e.g. pushup up and down
• when the user finishes matching the pose show how long it took them

pass through JS de-linter

Recognize pose regardless of position or angle

this would require a different library

Basic Greasemonkey version

greasemonkey script just increments counter on page load and when modulus is reached it opens a tab

the tab is a localhost static page that does the webcam stuff and uses localstorage for persistent data

must be compatible with qutebrowser's GM implementation

• confirm closing
• dismiss if webcam unavailable/in use
• scheduling
• show warning via "snackbar" e.g. https://www.w3schools.com/howto/howto_js_snackbar.asp
• "disable for X hours" form
  • this seems to work for sending data from page to GM script. for custom events see this
  • can't do: no cross-origin storage

chrome ver: remove from browsing history?

would require history permission

check if Chrome version can upgrade to latest p5

v 0.9.0 has this issue