News for hackers. Stuff that matters.
Re:Using a catch-all domain is a mistake by walrus01 on Wednesday June 01, 2022 @01:58PM (#31585600)
reminds me a bit of the family member who owns [email protected] and can't get random non technical people to believe that their email address domain really is lastname.com

"but don't you mean at gmail.co..."

no

Re:Using a catch-all domain is a mistake by mmastrac on Wednesday June 01, 2022 @02:08PM (#31585755)
I've been using [email protected] for ages and this doesn't happen to me. Usually it's "huh that's neat", but I also have a very unique last name
Re:Using a catch-all domain is a mistake by Macha on Wednesday June 01, 2022 @02:16PM (#31585872)
Mine is [email protected]. Most just accept it (all when I visit California, maybe that's your experience?), but I do get queried about it from time to time in my home country
Re:Using a catch-all domain is a mistake by Kab1r on Wednesday June 01, 2022 @09:51PM (#31590392)
I have had the same experience with [email protected]. My last name is also pretty unique.
Re:Using a catch-all domain is a mistake by omnibrain on Wednesday June 01, 2022 @02:23PM (#31585985)
I used [email protected] and sometimes even like the op "service"@firstname.lastname.name for some time. This lead into all kinds of trouble, social and technical. Social as in people did not understand why I "owned" "service"@..., why I did not have something like [email protected]/web.de/gmx.de/googlemail.de, that a third level domain is even possible, or they did not recognize .name.

Technical trouble was almost the same: Systems did not recognise the new at the time .name or Systems had trouble with third level domains. Somstimes I could sign up, but something in the backend broke and I never received mails.

Re:Using a catch-all domain is a mistake by gowld on Wednesday June 01, 2022 @02:29PM (#31586085)
There's a 199X NYTimes article about how prestigious lastname.com is. Maybe someone can find it in the archives