My new name doesn't have a middle name yet, so I'm accepting suggestions on what I could adopt that'd break as many systems as possible.

Obvious answers:
* null
* an emoji
* U+FFFD �
* half of a unicode surrogate pair
* EICAR
* some kind of prompt injection
* the entirety of DOOM, base64 encoded
* an illegal prime
* the source to decss
* 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0

@foone from experience, probably a hyphen. especially in a middle name.
@imbl yeah one of my sisters has a hyphenated last name, and it causes no end of issues

@foone @imbl throw an O' in there (with capital afterwards) for good measure to place yourself squarely among the ranks of the absolutely bog-standard centuries old name traditions that are regularly used in multiple cultures but somehow kryptonite for text handling systems.

I think the funniest might be the literal missing-character box codepoint. Everyone will assume that it's actually some obscure glyph their system can't handle, and whenever you write it out on paper on a form that uses little boxes for each letter, you'll just be drawing a rectangle inside the rectangle and whoever has to enter the data will be stumped.

@tiotasram @foone @imbl Alice O'Hyphen Averlong. No, even better: Alice O-Apostrophe Averlong
@foone @imbl why does the hyphen cause issues? I know for the apostrophe, as usually it's written with a quote, and so triggers all injection issues possible. But the hyphen?
@gunstick @foone everything is trying to treat names as a predictably structured string that can be reformatted. hyphens often break that "predictability", and these systems are garbage-in garbage-out. for instance, the name "foo bar baz-quux" (im deeply unoriginal, sorry) could end up as "foo bar baz", "foo bar quux", "foo bar baz quux", "foo bar quux baz", "foo bar bazquux", "foo bar quuxbaz", or something even more ridiculous like a complete misspelling