Running arbitrary code was such a problem that I just completely ruled it out for bitser. Instead of serializing functions, you can register safe functions as resources. This doesn't solve the upvalue problem, though.

> cover fills the entire width and height of the node.

Does that work like the CSS background-size: cover; or background-size: 100% 100%;?

> ratio maintains the aspect ratio of the background image.

Does that mean CSS cover? contain? Something else?

The client sends the encrypted (via HTTPS) but not hashed password to the server, both for changing your password and checking your password. So the server receives the password in plaintext but shouldn't store it.

Whatever the client sends to the server, an attacker can send too.

Especially if Jack's your uncle and he's on a horse...

If you do want to use another term for laypeople, I think "bullshitting" or "BSing" would have connotations that are more relevant than "hallucinating".

This sort of an approach often causes there to be hidden bugs, which do not generate errors now, but will cause some problem down the line.

It also has a tendency to lead to cargo cult programming (https://en.wikipedia.org/wiki/Cargo_cult_programming), which is less immediately problematic, but is still not great, especially for whoever needs to maintain that code.

If you really need a full name, it'll be because you need it for a specific institution, like government or bank. In that case, you probably need the ability to provide a separate full name for each institution.