4 ms·

Yikes. I've got my own first@firstlast.com but I've never ran into an instance where I wasn't able to use it. I do now have a hyphen in my last name which is n

Yikes. I've got my own first@firstlast.com but I've never ran into an instance where I wasn't able to use it. I do now have a hyphen in my last name which is not accepted everywhere. Some companies accept the hyphen but replace it with a space (some credit cards), some reject the hyphen so I either make it all one word or add my own space.

deleted 6y ago
[deleted]
walrus01 6y ago
I wonder if yours is more successful because the domain is firstlast.com , not just lastname.com. I've run into it most often with checkout systems that have separate fields for first and last name, it appears that some systems are matching for the field for last name cannot be exactly the same as the part of the email address after the @ symbol.
- KingMachiavelli 6y ago
  What category of site do you observe this issue on? My curiosity suggests that there may be a huge UX problem for extreamly popular sites; banks, government services, etc., where a large percentage of their usage base absolutely will entery 100% incorrect information unless extrenous safe guards are in place. Essentialy, if your site targeted every age demographic or even had a preference for older and/or less tech savy demographics, how can you prioritize the edge case that <0.00001% of your users has their own lastname.tld vs is entering an incorrect email address.
  - walrus01 6y ago
    It's spread out across a wide range of things. No specific market segment comes to mind. Personally I encountered it with enough things, often enough that it became a point of frustration, and I started using a gmail address for most 'ordinary' online purchases, which is an inbox set to auto-forward-everything to the firstname@lastname address. I agree that it's a huge UX problem - one of the reasons why a lot of online checkout processes have you type your email address in two separate fields, twice. Without some guardrails in place, there is probably a not insignificant number of people who typo their email address in a single field, or type a malformed address, and then complain to customer service or their credit card company when they never receive an emailed invoice.
    - KingMachiavelli 6y ago
      Interesting. Of course I'd speculate that some service like AnonAddy [1] or just having a secondary, anonymous, domain would be a better solution. Or even the most simplest is using a somthing-else@lastname.com email as I would expect them to at least check both parts. Worse case scenario, you could use firstname@subdomain.lastname.com. Even something like 1.lastname.com would likely work. I suppose it depends on your reasons for using your own domain in the first place but having to employ the use of a gmail acount negates a lot of the privacy & security of a personal domain IMO. [1] https://anonaddy.com/ https://anonaddy.com/
- saghm 6y ago
  > I've run into it most often with checkout systems that have separate fields for first and last name, it appears that some systems are matching for the field for last name cannot be exactly the same as the part of the email address after the @ symbol That's incredibly obtuse of them; what possible reason could they have for doing that?
  - walrus01 6y ago
    My best guess is an overly cautious UX guard rail for elderly people, persons very new to the internet, or people who think they can type their twitter username, facebook account name, or some other non properly formatted email address into the "Email:" field and get things delivered.

deleted 6y ago

[deleted]

walrus01 6y ago

I wonder if yours is more successful because the domain is firstlast.com , not just lastname.com. I've run into it most often with checkout systems that have separate fields for first and last name, it appears that some systems are matching for the field for last name cannot be exactly the same as the part of the email address after the @ symbol.

KingMachiavelli 6y ago
What category of site do you observe this issue on? My curiosity suggests that there may be a huge UX problem for extreamly popular sites; banks, government services, etc., where a large percentage of their usage base absolutely will entery 100% incorrect information unless extrenous safe guards are in place. Essentialy, if your site targeted every age demographic or even had a preference for older and/or less tech savy demographics, how can you prioritize the edge case that <0.00001% of your users has their own lastname.tld vs is entering an incorrect email address.
- walrus01 6y ago
  It's spread out across a wide range of things. No specific market segment comes to mind. Personally I encountered it with enough things, often enough that it became a point of frustration, and I started using a gmail address for most 'ordinary' online purchases, which is an inbox set to auto-forward-everything to the firstname@lastname address. I agree that it's a huge UX problem - one of the reasons why a lot of online checkout processes have you type your email address in two separate fields, twice. Without some guardrails in place, there is probably a not insignificant number of people who typo their email address in a single field, or type a malformed address, and then complain to customer service or their credit card company when they never receive an emailed invoice.
  - KingMachiavelli 6y ago
    Interesting. Of course I'd speculate that some service like AnonAddy [1] or just having a secondary, anonymous, domain would be a better solution. Or even the most simplest is using a somthing-else@lastname.com email as I would expect them to at least check both parts. Worse case scenario, you could use firstname@subdomain.lastname.com. Even something like 1.lastname.com would likely work. I suppose it depends on your reasons for using your own domain in the first place but having to employ the use of a gmail acount negates a lot of the privacy & security of a personal domain IMO. [1] https://anonaddy.com/ https://anonaddy.com/
saghm 6y ago
> I've run into it most often with checkout systems that have separate fields for first and last name, it appears that some systems are matching for the field for last name cannot be exactly the same as the part of the email address after the @ symbol That's incredibly obtuse of them; what possible reason could they have for doing that?
- walrus01 6y ago
  My best guess is an overly cautious UX guard rail for elderly people, persons very new to the internet, or people who think they can type their twitter username, facebook account name, or some other non properly formatted email address into the "Email:" field and get things delivered.