urlencoding is not idempotent

is there a good succinct way of saying "this is an edge case we don't need to handle because it'll only be hit by people who are looking for edge cases"? it's a feeling i am very familiar with from videogame making, but i don't know of a good way to name it.

(it's also a little risky - you do wanna make sure people can't hit an edge case & break other stuff, or get access they're not supposed to)

@v I've used "simulation boundary" for this.

As in, this wacky user interaction is outside the simulation boundary so the user won't be upset that we don't handle it well.

@jeff oh, that is a nice way to think about it!