Rik Cabanier

> @toji @Manishearth @cabanier - PTAL, resurrected this PR given that we now have an interop issue related to underspecification of the pose. Also fixes #114. Thanks for making that...

This is now part of the layers spec and shipping in Quest Browser

> I'd love faces as a tracked object in a mode like this to allow developers to make simple filters like accessories and such in a safe privacy preserving way...

> Facial effects/features are being worked by other groups (Khronos, VRM, Snap) are looking at facial detection, identification, and anchors. It would be good to make sure the work is...

> I believe there may be more support for XR features now such that I'd have a different opinion on how to go about doing this. Regardless, I don't think...

Thanks @alcooper91! Interesting how this is different from [OpenXR](https://developer.oculus.com/documentation/native/android/move-face-tracking/). There you get a list of "expressions" and it's up to the author to map those to an avatar. So, there...

> +1 Agree they shouldn't block. Was trying to ensure I didn't derail this issue with discussion of "face-tracking"/"face-detection". Those should likely me discussed in other issues in this current...

There is interest but every time we discuss the proposal, we come up with more security problems that require workarounds. :-(

> > I am seeing the same error on Magic Leap 2 device. I think the issue is because `depth-sensing` implementation in threejs does not use [XRDepthStateInit](https://immersive-web.github.io/depth-sensing/#dictdef-xrdepthstateinit), while using depth-sensing...

> @cabanier Do you mind rebasing this PR? Sorry for overlooking it. But now that depth sensing is fixed via #28530 the PR can be eventually merged. I can do...