I feel like the primary use case for such a technology is manipulating and profiling people over video chat, maybe even autonomously. Hiring managers, HR, landlords, and police are obvious customers.
It’s not very accurate. Maybe because of the camera fidelity. It was about 10bpm lower than actual for me. Seems to operate off of subtle motions caused by pulse. It was even worse at detecting breathing.
I would prefer some kind of privacy statement or even some kind of explanation about what is going on before I just randomly turn my webcam on. This might be great and I’m proud of you for launching but I don’t do things like that. Heck, videos can make a person’s heart race - I had my first attack at 39 and that’s a hell of a lot of risk.
I haven't dug deeper due to time availability, but for the same sake of privacy, I've found:
1. `/api/event` endpoint mentioned in the `/stats/script.js` file;
2. There's `/parties/lobby/main/telemetry` in a minified JavaScript chunk asset;
3. There's VitalLens mentioned, and there's an error string in the same asset: "A valid API key or proxy URL is required to use VitalLens. If you signed up recently, please try again in a minute to allow your API key to become active. Otherwise, head to https://www.rouast.com/api to get a free API key."
I feel like the primary use case for such a technology is manipulating and profiling people over video chat, maybe even autonomously. Hiring managers, HR, landlords, and police are obvious customers.
The response I anticipate will be "But this will help doctors over telehealth and stuff!" - Please see https://calebhearth.com/dont-get-distracted
Can you explain how https://calebhearth.com/dont-get-distracted applies to the potential response you described? I don't get it.
They will weaponize it.
It’s not very accurate. Maybe because of the camera fidelity. It was about 10bpm lower than actual for me. Seems to operate off of subtle motions caused by pulse. It was even worse at detecting breathing.
May be related: Explanation of motion and color amplification in video by Steve Mould https://youtube.com/watch?v=rEoc0YoALt0&t=722s
He even shows pulse detection (around 8:30).
It registered in the low 40s for me, while my watch was saying 72-75. I guess YMMV
Could be interesting, but allowing the webcam crashes my browser.Repeatedly
macOS 15.7.1 (24G231) Brave 1.87.186 (Official Build) (arm64) Chromium: 145.0.7632.45
In the minified source code, we may see, it uses:
``` try { const l=await navigator.mediaDevices.getUserMedia({audio:!1,video:{facingMode:"user"}}); /* ... */ } catch { this.showError("Could not access webcam. Please check permissions.") } ```
There are alternatives to verify mediaDevices support as https://addpipe.com/getusermedia-examples/
I would prefer some kind of privacy statement or even some kind of explanation about what is going on before I just randomly turn my webcam on. This might be great and I’m proud of you for launching but I don’t do things like that. Heck, videos can make a person’s heart race - I had my first attack at 39 and that’s a hell of a lot of risk.
I haven't dug deeper due to time availability, but for the same sake of privacy, I've found:
1. `/api/event` endpoint mentioned in the `/stats/script.js` file;
2. There's `/parties/lobby/main/telemetry` in a minified JavaScript chunk asset;
3. There's VitalLens mentioned, and there's an error string in the same asset: "A valid API key or proxy URL is required to use VitalLens. If you signed up recently, please try again in a minute to allow your API key to become active. Otherwise, head to https://www.rouast.com/api to get a free API key."
This is really kind of you - I appreciate this. Thank you for taking that time!
Worked for me on Android. Love the simplicity.