Minawhy do you even offer your services outside the US?
@@meena fuckin monolingual anglophones i stg
@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)
(mapcar #'emacsomancer objs)@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.
Ripp (Old Account ➡ Chitter)@meena Yay I get to link this again https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
Patrick Mevzek@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.
@pmevzek this was a form for Billing data, tho....
@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.
Inga stands with 🇺🇦 🇵🇸@meena at least it allows numbers in last name
@IngaLovinde i was thinking i could go by Gali8 or something, but nothing felt right
@IngaLovinde i want my acute c!
a cute c...!
@meena could have used u0107
@IngaLovinde excellent point!
@meena I'd even say, excellent code point
Be@meena cringe 😬
@be don't worry, it's been explained to me that this is, once again, a DNS issue: https://framapiaf.org/@pmevzek/107247795431322502
Patrick Mevzek (@[email protected])
@[email protected] 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.
Dick Smiths Fair Go Supporters@meena
First name, last name is very 1999.
First name, last name is very 1999.
@meena
(What we mean is) Having separate first and last name fields is very 1999 also.
(What we mean is) Having separate first and last name fields is very 1999 also.
FiXato
@FiXato i really wonder where it's coming from
WHOIS name record is just one line
don't know enough about EPP: https://framapiaf.org/@pmevzek/107247795431322502
Patrick Mevzek (@[email protected])
@[email protected] 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 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...
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"…