There should be some browser-level enforcement of this. For example, it would seem possible to detect a user frustratingly mashing the back button, and offer a remediation dialog to disable any hackery that's hijacking the back buttons.
It would seem like a naive solution would be some arrangement where Discord would ask for a proof-of-age from an official service ran by the State (which issues your ID)
A side note: I am very sad that HDMI-CEC apparently can only support like 3 "console-like" devices. I have an Apple TV, Nintendo Switch 2, Sound Bar (eARC) and PS5 hooked up, but only 3 can really interact with CEC.
It took me a long time to diagnose why it seemingly wouldn't work with my Nintendo Switch 2.
I ended up disabling it on my PS5 because I never use the darn thing, but it kind of stinks since most TV's have 4 HDMI inputs.
The key that is punched into the input field is based on where your finger lifted up. So if you have slide-to-type on, the pop-up paddle that showed up on key-down won't change to where your finger slid to for key-up. That's why when typing fast with slide-to-type on you can get confusing UI hints like this.
It kind of seems like the grace period for the paddle hiding with slide-to-type needs adjustment. I just leave slide-to-type off.
I'd bet a lot of this behavior is heavily correlated with how we generally read top to bottom, which is in itself, probably an arbitrary decision made by ancient text writers.