She works in a non-technical field and some percentage of people simply can't grasp the concept that an ordinary person owns their family name as a domain name.
I thought I was being clever at the time, but nobody gets it. Sigh.
"just email me at 'my name at my last name but dot ski'"
super memorable and shows you know your way around the stack :)
And I thought short domains are cool and abbreviated the name to 3 letters. Today I only communicate the full <first>@<last>.name.
I learned a lot about slooowly migrating names along the way.
Having your own phone number was as unusual then as a domain might be for some today.
Spread the word and show it!
Communication of it isn't too bad. I usually say "the word me at {first name}.to, spelled the same way as my name" (since oftentimes they ask for my name first). Other times I literally just spell it out.
Using an arbitrarily chosen noun:
If I have a taco truck and I put in giant font on the side
BURRITO.NET
or
BURRITO.COM
People will immediately get that it's a website.
If I put BURRITO.NAME on it, very few will.
The thing that sucks about namespaces is that there's no way to win. If people can own them without an ongoing cost, they'll go unused (think of people squatting really good social media usernames without activity on the account). If people have to pay an ongoing cost, there will be a lot of stuff where the cost-benefit to them of maintaining the domain part of those [Cool URIs] they picked doesn't make sense... so a lot of cool stuff has disappeared from the internet, especially the personal or non-commercial freely shared resources, leaving an ad-ridden wasteland behind.
So yeah, I do kinda think that people should have their own domains if they have enough internet presence to want to set up a Linktree, but way too many techie people take the drawbacks for granted.
[Cool URIs]: https://www.w3.org/Provider/Style/URI.html is the link everyone knows, but https://remysharp.com/2016/12/22/cool-uris-dont-change is the better one
This is the biggest problem (and yes, I know one can make a .onion website, but I would like to stay on the mainnet).
At least by owning the domain, I can still use GMail as my mail provider, but if something goes wrong there, I can update MX records and continue to receive my email.
> For example, let us create a series of top-level persistent domains y2000, y2001 and so on. One would only be able to acquire a .y2000 domain name during the year 2000. Once acquired one would have it forever.
Disagree with the message of the post. No one is impressed by personal domain names. No one cares about your branding. People only care about the content. And unless you are on the ball regarding payments, you domain and or hosting will lapse sooner than you expect and all your content gone. At least with facebook or substack you do not have to worry about that.
Another lawyer with the same last name owns: lastnamelaw.net
I get email addressed to that firm almost on a daily basis-- even as "responses" to the firm.
My first and last are not super common, but not unusual either.
I get tons of emails for other people sharing my name. Most recently a teacher emailed me a detailed educational plan for a student. I've had doctor appointment reminders, collegiate coaches trying to set up scrimmages, and countless account verification emails, among others.
I notice email domains on resumes. You get bonus points if you list an email from a custom domain on your resume.
I don't look kindly on developer resumes that have emails from aol.com, hotmail.com, yahoo.com etc. The last one indicates that you probably don't care about security.
I mean, you're not giving every developer a fair chance to show their true value. The e-mail provider has nothing to do with their technical skills. Or can you objectively demonstrate such causal relation or at least a statistically relevant correlation?