General tip for structuring user data. Try to treat it as obscure blobs, whenever possible.. Imagine it's encrypted so it's not even printable/human readable.

General tip for structuring user data. Try to treat it as obscure blobs, whenever possible.. Imagine it's encrypted so it's not even printable/human readable. > forms, CON, CONIN$, CONOUT$, PRN, AUX, NUL, COM1 to COM9, LPT1 to LPT9, desktop.ini, _vti_ If they have to restrict those because some user input is going straight into their FS, then they mucked up. Probably should have been given a safe ID (perhaps uuid4, perhaps something more like a digest of the channel name instead of using the user input directly. For me it's a smell when someone says "You cannot use these characters". I automatically think "Why not? You're not using this unencoded or plaintext, right?" eg passwords, or usernames, or content that will show up on a webpage like a comment or such. This all being said, perhaps it's just an easter egg gone sideways... Perhaps they were just trying to have a bit of fun :)