Uh... yeah.

Just hold the sysadmins hand over the lighter until they tell you the password.

Never forget the easy way in ... the humans.

Like the classic xkcd on security

https://xkcd.com/538/

Good luck hacking a Switch using that method and getting away with it.

Explain your needs and they will be incredibly gracious.

They will also be sad for you to miss the rice.

There are still contradictory customs around this enough that it is standard practice to warn exchange students from Europe that if they finish absolutely everything on their plate that this is a signal in many American homes that you should be served more. This can lead to some real discomfort as the student tries to eat everything they are given which leads to being given more and more.

So at the same time it is considered poor taste to take more than you can eat, it is also considered poor form to offer a guest anything less than more than they can eat. This also shows up when people rate restaurants by the serving size.

At that point I would be very impressed if you could remember what the timers are for.

Check out emacs for options like this.

And, yes, there is a circumstance if you want to include Arabic or Hebrew in comments or strings. You need the zero width left-right markers to make that work.

To prevent ligatures from forming when you need that.

That's the job of a typesetting language.

As do tabs, ems, ens and quads.

Unicode shouldn't be a typesetting language. The proper tool for that is Latex.

They only render differently in some fonts, on some displays.

But these characters only look identical in some fonts. Are you saying that if you change font, some characters in a string should change appearance and others should not?

And what about the round-trip rule?

And ligatures? Aren't those a semantic distinction?

> But these characters only look identical in some fonts.

That's a problem with the fonts.

> And what about the round-trip rule?

Print Unicode on paper, then ocr it, and you'll get different Unicode. Oh, and normalization.

> ligatures

Generally an issue with rendering.

> semantic distinction

Unicode isn't about semantics (or shouldn't be). Consider 'a'. It's used for all kinds of meanings.

One of the ground rules of Unicode is the round trip rule. You have to be able to translate to and from Unicode without loss of information.

They threw that out the window with normalization.