Make confusable character warning less jarring

[n0toose]

This commit assumes that the warning can be made more discreet
so as to make it less annoying for the people that do not actually
need the warning, without necessarily increasing the risk for those
that do need it.

This doesn't fix the underlying problem of the warning being shown
in certain cases that, say, a certain kind of whitespace character
like 0x1E could be absolutely justifiable from a technical
perspective.

[n0toose]

No warning's and error's are used anymore, as it is assumed that the large header is enough to attract the attention of the user.

I considered two cases:

• use warning's in both cases
• only use warning's in one of the two cases (but I wasn't too sure about that)

[delvh]

Any screenshot?

[n0toose]

Any screenshot?

Sure, give me a second.

[n0toose]

Full disclosure that I should've mentioned earlier: Considering that the change is minor and does not contain any logic changes or anything that could otherwise prevent the site from rendering correctly, I recreated the change again using "Inspect Element" (removed the tag, changed the text content) on Codeberg to save time.

I didn't see a reason to do so, but I can test this thoroughly if necessary.

[techknowlogick]

Thanks for this PR. I'm hesitant to approve with the warning removed, as this is in place to remedy a security concern and otherwise the security reporters had wanted to request a CVE without the warning.

[n0toose]

Maybe we could use warning instead of error? I understand the reason why this is in place and would not like to compromise the readability of this warning (and therefore this isn't the kind of hill I'd be willing to die on), it's just that some users that have valid reasons to use e.g. form feeds get very annoyed by it as well.

Feel free to close this if you believe that this isn't the right way to do this.

[denyskon]

I think using warning in both cases would be the best compromise.

[n0toose]

I think using warning in both cases would be the best compromise.

I addressed this.

[denyskon]

@techknowlogick Do you want to block or is this compromise acceptable for you?