News for hackers. Stuff that matters.
Re:EBCDIC Is Incompatible with GDPR by wink on Wednesday October 25, 2023 @05:57AM (#38011112)
I can tell you that German bank thing I signed up in 2023 and can't be older than ~5 years asked for my FULL name as written on my ID, in my case it's "First Second Last" but I go by "First Last" but in their infinite wisdom they decided to ask for the full thing (which I understand, it's bank stuff) but never think about what they call me in their stupid email. No one's ever called me "First Second" - not even my parents. And I can't even be mad, but I'm still disappointed. (Fortunately my name is ASCII and since we can do more than 8+3 I've never had problems.)
Re:EBCDIC Is Incompatible with GDPR by rjsw on Wednesday October 25, 2023 @06:47AM (#38011392)
I made a similar mistake in France, the system decided to call me Firstsecond Last.
Re:EBCDIC Is Incompatible with GDPR by bandrami on Wednesday October 25, 2023 @07:12AM (#38011559)
My first name starts with a W (let's say it's "Walter"). In India multiple times I have spelled it out over the phone and then received a letter addressed to "Uualter".
Re:EBCDIC Is Incompatible with GDPR by secondcoming on Wednesday October 25, 2023 @07:44AM (#38011750)
A friend named 'Alice' is 'Erith' in a UK council's database.
Re:EBCDIC Is Incompatible with GDPR by coldpie on Wednesday October 25, 2023 @09:19AM (#38012478)
Please keep her away from ex-soldiers with very long swords.
Re:EBCDIC Is Incompatible with GDPR by felixg3 on Wednesday October 25, 2023 @08:28AM (#38012067)
Hehe, and my name contains an ß which is often confused with a B. I started to point out the machine readable area instead of just showing my passport…
Re:EBCDIC Is Incompatible with GDPR by squarefoot on Wednesday October 25, 2023 @09:22AM (#38012514)
Could it have been a too literal transcription of its spelling? W is spelled "Double U".
Re:EBCDIC Is Incompatible with GDPR by bandrami on Thursday October 26, 2023 @06:52AM (#38023943)
Right, yes, that is my assumption
Re:EBCDIC Is Incompatible with GDPR by selimthegrim on Wednesday October 25, 2023 @07:00AM (#38011478)
This happens to me on United all the time for some reason.
Re:EBCDIC Is Incompatible with GDPR by Jailbird on Wednesday October 25, 2023 @07:12AM (#38011557)
I've seen that forever and not just on United. I have thought it's something about the underlying SABRE system that many airlines use. Maybe someone here knows more.
Re:EBCDIC Is Incompatible with GDPR by pavlov on Wednesday October 25, 2023 @07:41AM (#38011733)
Happens to me as well. My first, second and last names are quite short, five letters each. So my guess is that’s it’s related to that.

Maybe there’s simply the COBOL equivalent of the following somewhere:

  if len(first) + len(second) + len(last) <= MAX_LEN_ON_TICKET:
    first_name_on_ticket = first + second
Re:EBCDIC Is Incompatible with GDPR by raverbashing on Wednesday October 25, 2023 @08:32AM (#38012091)
I've asked ChatGPT for the COBOL equivalent... and it's 18 lines
Re:EBCDIC Is Incompatible with GDPR by kvmet on Wednesday October 25, 2023 @07:48AM (#38011765)
I can tell you from personal experience that if you have four names it will turn "First Second Third Last" into "Firstsecondthird Last" (I usually fly Delta).

I asked a checkin agent to fix it but they said it will start rejecting my ID if they change it at all.

Re:EBCDIC Is Incompatible with GDPR by noodlesUK on Wednesday October 25, 2023 @10:46AM (#38013393)
On British airways (and I believe other ticket systems that use Amadeus), I often get LastnameTitleFirstnameSecondname all as one word (in caps). It certainly looks funny on the boarding pass, but I've never had any issue getting through security.
Re:EBCDIC Is Incompatible with GDPR by pseudonamed on Wednesday October 25, 2023 @08:20AM (#38012010)
Names with hyphens are also contracted by SABRE... Subname-Subname becomes Subnamesubname.
Re:EBCDIC Is Incompatible with GDPR by tivert on Wednesday October 25, 2023 @09:18AM (#38012472)
> I've seen that forever and not just on United. I have thought it's something about the underlying SABRE system that many airlines use. Maybe someone here knows more.

I don't remember the precise details, but some airline website's password had restrictions at one point that made it super-obvious that they were internally converting alphanumeric passwords to digits based on the US telephone key mapping.

I remember thinking at the time it might ultimately have been due to SABRE (because I believe that's literally one of the oldest computer system still in use), and screen-scraping some telephone menu system depressingly seems like something someone would do for expediency.

I wouldn't be surprised if a system like that also mangles names.

Re:EBCDIC Is Incompatible with GDPR by dpkirchner on Wednesday October 25, 2023 @10:10AM (#38012995)
Fidelity does this as well:

> Usernames and passwords containing letters need to be translated to numbers to enter them in a Fidelity phone system (like FAST, or if you call a representative). Use your telephone keypad to convert the letters to numbers. There is no case sensitivity. Substitute an asterisk (*) for all special characters. https://www.fidelity.com/customer-service/need-help-logging-...

Re:EBCDIC Is Incompatible with GDPR by weinzierl on Wednesday October 25, 2023 @08:54AM (#38012262)
"FULL name as written on my ID"

This is completely normal for official documents in Germany and it makes sense for us.

Technically we do not have first, second or any other numbered names. Our given names form a set in the mathematical sense and any one is equally valuable. This comes from the tradition of given names being given by godmothers and godfathers and we wouldn't want to get into the issue to ever have to value one of them over another. At least this has been the case in some parts of Germany and has influenced the official regulations for names.

Of course the names have to be put into an order on your ID and to keep things simple banks, schools, authorities, etc. ask you to use that order on their documents.

Traditionally, official documents just used the surname with "Herr" or "Frau" but nowadays they often use just the given name in first position on your ID.

If never heard of a "First Second" case with one exception:

Given names can be connected with a dash. In this case the order is fixed and the whole unit is treated like a single name. While in principle arbitrary names can be combined there are certain very common combinations, like "Hans-Peter", "Karl-Heinz" or "Franz-Xaver". If you happen to be named "Hans Peter" (without dash) it's likely that they assume the dash and will call you "Hans Peter" or "Hans-Peter" all the time.

Re:EBCDIC Is Incompatible with GDPR by hunter2_ on Wednesday October 25, 2023 @10:50AM (#38013444)
> it's likely that they assume the dash

There is a very mild version of that in the US -- lower likelihood of blind assumption, but still present: when a set of two given names starts with "Mary" or ends with "Ann/Anne". Examples include "Mary Jane", "Mary Kate", "Jo Ann", and of course "Mary Ann". Some have simply merged into single names like "Maryanne" and "Joanne" more recently. There are probably others.

Re:EBCDIC Is Incompatible with GDPR by wink on Friday October 27, 2023 @07:49AM (#38037301)
> This is completely normal for official documents in Germany and it makes sense for us.

Of course, and I mildly apologize for my case of Whataboutism because I actually described the reverse. They're taking the rules too literally and are using the thing they need for official documents everywhere (their marketing/status emails).

I'm just just kinda puzzled why they'd think it's a good user experience, especially for people who are not just not used to reading their government id name but actually uncomfortable (i.e. pending name change).

Re:EBCDIC Is Incompatible with GDPR by throwaway251023 on Wednesday October 25, 2023 @09:35AM (#38012612)
Something kinda similar, I applied for a PH passport and they ADDED a third name to my name. Instead of my actual "first second last" on my official PH documents I'm " first-second third last". The third isn't anywhere in my name/us birth certificate or any other identifying documents and not at all what my parents named me. I only use my US passport now because it caused a bit of confusion with my US departing airline ticket first name not matching my PH passport and if it had that, then the arrival into the US would not match my US passport.