I do plan to have a front-end for manual annotation of referee performance: correct relative position, timing, determining attacking/defending wrestler etc.
538 karma · joined March 13, 2019
I do plan to have a front-end for manual annotation of referee performance: correct relative position, timing, determining attacking/defending wrestler etc.
Indexing multiple captured video streams with awarded action points and adding athlete/referee positions overlay. Stretch goal -- controlling PTZ camera for predictive capture of the high intensity actions.
"We don't want to build the perfect solution." Can both mean "no need to cover use cases we don't care about" and "no need to deal with divizion by zero in a product, where a number is divided by the user entered number".
When a company sets C2 as a requirement, it can be interpreted as "must have a degree from German University".
Consider a doorman or a waiter in low-trust status based society: to get a service one must exaggerate status signaling and/or bribe the gatekeeper to be deemed worthy of a service. Kiosk doesn't accept bribes and you can trust "no vacancy" from kiosk more than from the doorman.
So cheap. Comparing to Germany.
And I have more examples, where I, personally, was on the both sides of the fence: defined by my level of the same problem understanding, not by the tooling.
It's just friends buying from friends.
> Seeing as this has made the orange site, let it be known this person is a model security researcher.
> The issue was not in any FFmpeg release, and a report was sent three days after a new code was added to FFmpeg Git.
> There was no big CVE ADVISORY "MUH SECURITEH" "you need to fix this now or you will be hacked and the world will end" associated with the report.
At least for me there was nothing indicating there is not enough clearance.