Avaer Kazmer

The proxy route is serving back the app: https://local.webaverse.com/@proxy/https://https-vrchat-com.proxy.webaverse.com/ It should be serving the proxied content. This is a `totum` feature.

Possible fix attack vector: https://github.com/webaverse/totum/blob/da65086a54e5c3798aa8ae955463977726d2f39b/util.js#L34

This should be going through the proxy to load the VRChat home page:  Instead, it errors. ``` metaversefile-api.js?t=1659763895440:435 error loading "/@proxy/https://https-vrchat-com.proxy.webaverse.com/" SyntaxError: Unexpected token ':' ```

I'm back on it, it needs a bit more work.

I actually think the pose resolution calculations in kalidokit leave a lot to be desired. That code uses mostly vector math hacks with _tons_ of corner case detection, which has...

This page really helped me: https://google.github.io/mediapipe/solutions/pose_classification.html Especially this diagram:  With basic 3d maths you can easily compute the corresponding avatar bones quats. 

For posterity, here is the face geometry map for mediapipe: 

Examples of kalidokit hax/code problems: https://github.com/yeemachine/kalidokit/blob/505e21e5bcb86771edf96acaa72a0493bd358200/src/utils/vector.js#L243 https://github.com/yeemachine/kalidokit/blob/505e21e5bcb86771edf96acaa72a0493bd358200/src/PoseSolver/calcHips.js#L29

This is almost done. I rewrote the core to use my own math rather than kalidokit and indeed, it turned out cleaner code and higher quality output. We should probably...

I ended up implementing the isolated origin iframe version of this to take advantage of the strict process separation in that mode. Note that to make this work, fake RAF...