NoRH is technically impossible. You would need a closed-down hardware to do it. Something what cannot be even jail-broken and no other peripherials allowed than official (guaranteed by cryptography).
In Chrome, the local override feature can override any JavaScript code.
Even if the code would run at server-side (and only transmitting the sound and video), the pressed keys could be recorded and played back until needed, from there, continue driving. Takes much more time than just rewinding with the replay viewer, but Replay Handling would be still possible.
Even if someone streams in live how they play (with their hands on the keyboard visible), a script might run in the background to send the proper keypress events, while just omitting the real ones, not to interfere. Hard to catch if there is some discrepancy between what's seen on the monitor and on the keyboard.
A solution could be to publish the new track at a given time (e.g. 8 PM), and there would be only 10 minutes to submit replays.
In Chrome, the local override feature can override any JavaScript code.
Even if the code would run at server-side (and only transmitting the sound and video), the pressed keys could be recorded and played back until needed, from there, continue driving. Takes much more time than just rewinding with the replay viewer, but Replay Handling would be still possible.
Even if someone streams in live how they play (with their hands on the keyboard visible), a script might run in the background to send the proper keypress events, while just omitting the real ones, not to interfere. Hard to catch if there is some discrepancy between what's seen on the monitor and on the keyboard.
A solution could be to publish the new track at a given time (e.g. 8 PM), and there would be only 10 minutes to submit replays.