I doubt it. As explained by GitHub user tbrandirali, the stated goals seem to be inherently contradictory. Quoting in part:
"This internal contradiction is further demonstrated by the fact that the proposed solution to prevent misuse by websites - holdbacks - is to simply sabotage the functionality of the system itself, by making attestation probabilistic. This is not a workable solution to the problem: if the holdback rate of requests is low enough, the denial of service to legitimate users will simply be a cost of business that websites will accept; if instead it is high enough, websites will not use this system as it does not provide meaningful enough information, even for analytics purposes, due to the high uncertainty. There is no goldilocks zone where this system is useful but not open to abuse by implementer websites. You're either implementing a feature that can - and most likely will - be used by websites to exclude unattested clients, or you're implementing a useless feature."
Why wouldn't a 10% holdback work? Would a company consider it "simply a cost of business" to block 10% of people at random? That's going to cause a huge amount of support load and probably a lot of negative press. 90% of data will still be good for analytics.
Is there a way to get updates with your project's progress?
Human movement notation is also a hard problem for dance and choreography that needs solving. My partner has been talking about it for years, and there would definitely be interest from the dance world.
I don't have a GitHub repo or anything going yet. I can update this comment when I do. My email is in my profile if you want to stay in touch. In fact, I would really appreciate it. Dance and choreography would certainly be a big aspect.
It's just an open question, and as such, it does seem it's an afterthought, when it should be front and center if anyone care for an open web.