“We call her Carrie, because of the carriage return.”
You can also try to give the child NULL as middle name for additional fun.
someone tried that with their license plate, it turned out well: https://www.wired.com/story/null-license-plate-landed-one-hacker-ticket-hell/
edit: archive link
I just realized that the shitty software on the other side of the divide is casting null to ”null", which absolutely explains that issue. What a cluster
He is being too nice. He needs to get a lawyer and sue that shitty company for harassment and whatever else.
ETA: The US isn’t overly litigious. We are under litigious if anything.
Oh no, it gets worse:
Prank or not, Tartaro was playing with fire by going with NULL in the first place. “He had it coming,” says Christopher Null, a journalist who has written previously for WIRED about the challenges his last name presents. “All you ever get is errors and crashes and headaches.”
Archive link: https://archive.ph/o/Foe1r/https://www.wired.com/2015/11/null/
asking questions like this is how i found out that one of the allowed characters in names in my country is ÿ, which is fine in Latin-1 but in 7-bit ASCII is DEL.
This sounds like it would create a whole list of fun and irritating edge conditions for some poor bugger to debug. Love it.
If someone else has to debug the problems caused by a parent naming their child with a special character, does that make the parent the bugger? 🤔
That’s easy, just call it Jhon\nDoe
John\0Doe will fuck with all C (and C based derivatives) software that touches it.
I have an apostrophe and it’s super annoying as some companies see it as a SQL injection hack and sanitize it.
So I’ve received ID with Mc%20dole or they add a space in it. Or I’ll get a work email with an apostrophe but I cant use it anywhere because sites have it disabled. And I’ve missed my flight because I changed my ticket once to add the apostrophe and the system just broke at the gate.
Worse yet many flight companies have “you will not be able to board if your ID doesn’t exactly reflect your details” but their form doesn’t allow it. Even most forms for card payments don’t allow it even though it’s the name on my card.
I have an apostrophe and it’s super annoying as some companies see it as a SQL injection hack and sanitize it.
My surname contains a character that’s only present in the Polish alphabet. Writing my full name as is broke lots of systems, encoding, printed paperwork and even British naturalisation application from on Home Office website. My surname was part of my username back at uni, and everytime I tried to login on Windows, it would crash underlying LDAP server, logging everyone in the classroom out and forcing ICT to restart the server.
%20 is encoded space if I remember right, so even then they were already incorrect
Always worth posting this classic.
There’s also the version with examples if you want to know exactly what and why it breaks.
And the git that collects all of these in one place, if you want to really nerd out.
Also relevant: https://www.wired.com/2015/11/null/
Same shit with American custom forms. On the one hand, they threaten you with Armageddon if you fill out the form incorrectly, on the other hand, they only allow plain letters, numbers, and a handful of special characters. Nobody there has the capacity of the mind that maybe a name cannot be correctly represented with that tiny subset of characters. So it is simply impossible to fill out that form without breaking the law. And it is a customs form, so they should know that people filling it out are most likely foreigners.
you will not be able to board if your ID doesn’t exactly reflect your details"
Do they care about an apostrophe though? I can see any punctuation being a problem.
I had to convince people to let me on board a plane because my name contain a swedish letter (å). Their computer system translated it into “aa”, which then didn’t match my passport.
That one I can actually see, having an extra letter that doesn’t match. Dropped punctuation or symbols (whatever the flair is called) though personally I wouldn’t care.
Your name is transliterated in your passport? That’s on the Swedish authorities then.
I have an apostrophe
Scottish/Irish?
some companies see it as a SQL injection hack and sanitize it.
Which kind of apostrophe?
A straight apostrophe, fine - that can and does get used in valid SQL injection attacks. I would be disgusted at any input form that didn’t sanitize that.
But a curly apostrophe? Nothing should be filtering a curly apostrophe, as it has no function or use within SQL. So if you learn how to bring that up in alt codes (Windows, specifically), Key combos (Mac) or dead keys (Linux), as well as direct Unicode codes for most any Win/Mac/*Nix platform, you should be golden.
Unless the developer of that input form was a complete moron and made extra-tight validation.
Plus, knowing the inputs for a lot of extended UTF-8 characters not found on a normal keyboard is also a wee bit of a typing superpower.
… why are you putting an apostrophe in McDole? The O-apostrophe in Irish names is an anglicisation of Ó, eg. Ó Briain becomes O’Brien. Mac Dól would become MacDole/McDole.
Yeah fuck this guy for spelling his name the way it was given to him what an asshole
Probably some bureaucrat decades ago making an incorrect assumption that passed down through generations. Happened to my family. No Irish roots whatsoever, yet somehow we ended up with the annoying form-breaking apostrophe in our ‘legal’ name just because it begins with the letter ‘o’.
“Oscar??? Surely, you’re mistaken. I hereby decree your name to be O’Scar!” ~Arsehole circa 1937
Once I was tasked with doing QA testing for an app which was planned to initially go live in the states of Georgia and Tenessee. One of the required fields was the user’s legal name. I therefore looked up the laws on baby names in those two states.
Georgia has simple rules where a child’s forename must be a sequence of the 26 regular Latin letters.
Tenessee seemed to only require that a child’s name was writable under some writing system, which would imply any unicode code point is permissible.
At the time, I logged a bug that a hypothetical user born in Tenessee with a name consisting of a single emoji couldn’t enter their legal name. I reckon it would also be legal to call a Tenessee baby 'John '.
Sounds like you did a thorough job as a QA tester. As a software engineer, I love to see it.
By the time the app was due to go live, we’d only reported bugs with the signup and login flows. This was misinterpreted as there only being issues with the signup and login flows, and the app launched on time. In reality, it was impossible to get past the login screen.
And then let me guess… Of course the QA testers get the blame, when in reality it’s either management or marketing that wanted to pushe the app out.
