You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current interface identifies Mediapipe hand landmarks on the server side. The webcam is fetched through the server, and served to the client through an iframe. This approach will lead to technical debt in the future and was initially only implemented for fast-tracked development. I did have a functioning approach with WebRTC but chose to not continue that approach because it required a WiFi connection to work.
Ideally, the React client will identify the Mediapipe landmarks in the client side to reduce the load on the server and also so anyone in the world can access the interface from their home.
The text was updated successfully, but these errors were encountered:
Description
The current interface identifies Mediapipe hand landmarks on the server side. The webcam is fetched through the server, and served to the client through an iframe. This approach will lead to technical debt in the future and was initially only implemented for fast-tracked development. I did have a functioning approach with WebRTC but chose to not continue that approach because it required a WiFi connection to work.
Ideally, the React client will identify the Mediapipe landmarks in the client side to reduce the load on the server and also so anyone in the world can access the interface from their home.
The text was updated successfully, but these errors were encountered: