being aware of the multitude of systems it would break. (It won’t even fit on most credit cards, since I’d refuse to make any of it the middle name.)
I’d like to see, within my lifetime, more ways for folx to try on new names and have that be as far reaching as they like. Real name policies must be destroyed as soon as possible, and not just on Facebook, but everywhere. Payment cards shouldn’t have names, but if they must, we need to be able to put anything we like in that field and have it update without shipping a new card. As long as I establish the link between myself and the name, I should be able to have as many names as I want and still be able to file my tax return.
All these things are possible. It is policy, law, and cisnormativity that prevents it. Let’s fix that.
By the way: you don’t have to be trans to change your name to whatever you like.
I’ll admit, I spent a good while trying to break things with Phone Tool’s preferred name field, and ended up learning a lot about how names are distributed across the company.
Emoji are sadly not allowed (not even symbols later retconned as emoji). But fullwidth forms are.
I then learned about the many ways where applications get people’s names. For Amazon users, Chime uses Active Directory, and whatever syncs names from Phone Tool to AD has some interesting conversion logic.
After spending some time trying to figure out if there was a way around HTML tag stripping (because who wouldn’t want <script>alert("sup")</script>
as their last name), I decided to go with “iliana weller’;DROP TABLE users;—”, until someone with the wrong kind of mind for security (three weeks later) emailed my director. (The single quote was specifically selected because there are plenty of people with apostrophes in their names, and the load bearing symbols didn’t even make it through AD conversion.)
After that was “iliana :)”, which Active Directory kindly transformed to ”), iliana”. And then, “iliana destroyer of worlds”.