

As the other commenters have noted, what sort of adversary are you trying to protect against? There is no such thing as “security for its own sake” but rather security measures like E2EE are to protect against specific types of attacks. Do you believe a ticketing system is vulnerable to attacks that E2EE would mitigate?
As an aside, please do not consider PGP to be a pinnacle of signing or encryption. I’ve opined in another project before about why Late 20th Century PGP isn’t that good in the 21st Century.
But even with a modern replacement for PGP, how would E2EE even work for a multi-user ticketing system? If everyone on the support side has the same key, then key management becomes (as usual) the most crucial part of the operation, and remains an unsolved problem at scale. This is no different than physical key management, when every member of the custodial team needs to have the “super key” that opens every door of a university campus.





In California, a U turn is considered a left turn that keeps going. As a result, a U turn is legal anywhere that a left turn is legal, except when signs are posted otherwise. So in a left-turn pocket/lane, it is both reasonable and expected that people will make left turns, some of which will continue into a full 180 degree turn. People who do U turns are doing what is allowed, and they have every right to do so. If this seems like a problem, then talk to your transportation department to restrict U turns.
I’m not aware of any aspect of a U turn procedure that would be any different than than a standard 90 degree turn: use turn signals, look for oncoming traffic, look for pedestrians, turn slowly as required by the radius, roll out of the turn with careful acceleration.