Follow

why do you even offer your services outside the US?

@videogame_hacker my message to support:

Hey, I know this might seem unusual, if you've never been outside the US or never spoken with someone in the US who's not a white guy, but my name and my address do not fit into US ASCII

That doesn't mean that they are INVALID.

ironically, support person who wrote back to me (and then went silent) seems to have a Russian (first) name (Bohdan)

@meena oh gods not namecheap

they ask for credit card information and address separately, and they let you save the address from the payment information so you don't have to type it out twice, but one of these input fields allows cyrillic text and the other doesn't, so if you successfully saved an address that contains non-ascii characters, you can't actually use it even if it was /successfully/ saved

it's such a pain

@AgathaSorceress they also somehow keep showing me my deprecated name / card / address from years and years ago

i haven't lived in Austria in 5 years, but i renew domains every year…

@meena tbh I've been using namecheap for only ~1.5 years but it's already been enough for me to seriously consider switching to something else like porkbun

I can't imagine how messy it will get for me with all the legal document changes and immigration and namecheap's painfully bad payment information handling :/

@AgathaSorceress if naming is bad, then renaming is usually bad, too

@meena@cathode.church either this or an email saying that you look suspicious so the account failed and to simply try again later

@meena English letters? Maybe they only accept runic input?

@emacsomancer i don't know, but they certainly don't support ï and é

strikes me like pure naïvité.

@meena not only are they name cheap, they're also rather letter cheap and diacritic cheap too.

@emacsomancer i think I'll use this as reason why i'm migrating elsewhere.

@shibao Unicode has a lot of problems 👀 but just ignoring all of that and only using ASCII isn't gonna solve any of them

@meena I can agree on the disappointment, but in this specific case (domain names) the problem is not purely on registrars, but also on registries. The underlying protocol (EPP) allows contact data to be either localized (full Unicode) or internationalized (basically just ASCII). Now the problem is that some registries handle only "int", some only "loc", some say one is mandatory, the other optional, etc. etc. From first experience, I can tell you this is hard.

@meena And domains have billing contacts, so this data may need to be sent to a registry. It can be argued about, but sometimes just taking the least common denominator is the fastest. Surely not the most perfect or beautiful, but market does not favor perfectness or correctness, just easiness and fastest in production.

@pmevzek Unicode is is turning 30 this month and most places on this planet can't store or process or display my name correctly.

this should be embarrassing to everyone involved.
but most people don't care enough except to make excuses for it.

so all it ends up being is denigrating to the people who care, who are trying their damnedest to not give up their names.

@meena Maybe you read me wrong, but I agree with you and I curse those cases as well (see my first message). I was just trying to give you some context and explain how the situation can be complex. No one can solve the problem before understanding the scale of the problem and the actors involved (not a single one for domain names). At least, you have the "choice" to find another provider that will take more care, and there are some, especially outside of USA. The error string is awful, granted.

@meena It is true however that the "US" mindframe percolates in far too many forms. For example, thinking that all countries have states and that they are mandatory in an address is an often found error. Or allowing only numbers in postal codes. At least in EPP the "st" and "pc" nodes to store all of that are optional.

@meena@cathode.church It's funny how in the US last names can aparently contain numbers but a letter with an accent is a no go.

@meena Sorry, you foreign languages are invalid. Lovely <3

@IngaLovinde i was thinking i could go by Gali8 or something, but nothing felt right

@meena
Enter your name exactly as it appears on your payment card (or passport, or whatever)

No, not _that_ exactly!!

@suetanvil because we ignore all the people with spanish names…

@meena

So one time when I was living in the US, I went home to Canada for a week or so to visit family. I found myself in the food court of a Canadian mall with the ubiquitous obnoxious flat-panel TVs showing news, and there was something about EU politics on. Not big news, just some debate or something.

It took me a moment to realize why this felt off: the US equivalent would never show non-US news, ever.

So in conclusion, this blind spot doesn’t surprise me.

@be don't worry, it's been explained to me that this is, once again, a DNS issue: framapiaf.org/@pmevzek/1072477

@meena
(What we mean is) Having separate first and last name fields is very 1999 also.

@FiXato i really wonder where it's coming from

WHOIS name record is just one line

don't know enough about EPP: framapiaf.org/@pmevzek/1072477

@meena it's been close to a decade (or perhaps longer) since I last briefly worked with EPP, so I can't really remember the details.
I do remember some ISPs' backends being a mess when it comes to storing things like phone numbers, addresses and other data...

@FiXato i wonder if "Extensible" in Protocol names is like "Lightweight" or "Simple"…

@meena @FiXato In almost all cases Yes. Sometimes Yes with extra swearing.

Sign in to participate in the conversation
Cathode Church

A place for trans makers, coders, tinkerers and dreamers.