My thoughts exactly. You should not be choosing TLDs that are volatile to upsets like this. Stick with the tried and true .com or .net, or one of the new TLDs that are not bound to a nation (unless you can comply with the stipulations) or particular type of organization.
Yeah I wasn’t thrilled when I heard the news. I have one maybe two domains with Google and I’m going to be shipped off to somw third party for my renewal. I haven’t checked but I’m pretty sure the domain business is being sold to one of those “build your website with us in half an hour” companies and I just cannot wait for the go-daddy like service…which I left go-daddy because of.
I think they are selling to square space and I think their website builder is pretty damn good actually, but not sure if I’d want to buy a domain from them unless it’s for a site hosted on squares space. I mean, they don’t exactly specialice on selling domains, but then again not really did google eather so we’ll see how the service will be I quess.
Hello there stranger. As completely factually appointed ambassador of lemmy.zip, I’d like to extend a warm welcome to all and am glad to see you’ve discovered our existence.
Back in the day, like early 90’s when they were managed by the university, they also hand reviewed each request. I had a customer with a registered company name something like “Wood Supplies Canada Inc.” and they wanted “woodsuppliescanada.ca”. They rejected it because “…canada.ca” was superfluous …
You don’t even need to be a citizen or PR, you just need to have “a Canadian presence”, which can be as simple as owning a trademark registered in Canada
No, practically speaking the domain name should have no effect on access time. DNS has so many layers of caching that as long as SOMEONE has accessed the website nearby (including you), the domain lookup will be local and therefore fast.
Anyway, DNS lookup times, even slow ones, are still not going to be noticable to the end use originally.
And you spread that server load by selecting different servers. While what you’re saying is technically true, in a practical sense if everyone picked a more local server that would be one way to achieve what you’re saying.
you don’t need a uniform distribution. if the server distribution mirrors the population distribution (and why wouldn’t it?), that will still achieve the desired effect.
.com and .net are under US jurisdiction they are not stateless. I could also see why the original lemmy developers would not want to use such a domain.
That may be technically true, but both TLDs are ubiquitous and it’s extraordinarily unlikely that the US will suddenly start confiscating millions of .com and .net domain names operated by non-Americans.
Do people not remember back in the 2010s when bit.ly was the main link shortener used everywhere on the internet, and then Ghadafi, the then dictator of Libya, declared the site to be incompatible with Muslin decency norms because it was used for porn? And then all bit.ly links were just dead links?
How many times do we have to learn this lesson? Domain name hacks are fun but just not worth it. And in 2023, now we have all the new TLDs. This was a dumb decision
My thoughts exactly. You should not be choosing TLDs that are volatile to upsets like this. Stick with the tried and true .com or .net, or one of the new TLDs that are not bound to a nation (unless you can comply with the stipulations) or particular type of organization.
Even gTLDs aren’t entirely safe. .dev is iffy right now because only Google can give those out and Google domains is going away.
What the hell, how am I just hearing about this now?
They didn’t even tell domain holders.
Yeah I wasn’t thrilled when I heard the news. I have one maybe two domains with Google and I’m going to be shipped off to somw third party for my renewal. I haven’t checked but I’m pretty sure the domain business is being sold to one of those “build your website with us in half an hour” companies and I just cannot wait for the go-daddy like service…which I left go-daddy because of.
I think they are selling to square space and I think their website builder is pretty damn good actually, but not sure if I’d want to buy a domain from them unless it’s for a site hosted on squares space. I mean, they don’t exactly specialice on selling domains, but then again not really did google eather so we’ll see how the service will be I quess.
.dev was stupid from the beginning due to how many local domains like that…
Alright https://lemmy.zip it is!
Edit: No way someone already did it
Hello there stranger. As completely factually appointed ambassador of lemmy.zip, I’d like to extend a warm welcome to all and am glad to see you’ve discovered our existence.
damn that theme is nice
Zip is the dumbest TLD of all. It is a phishers dream come true. invoice.zip explains it.
Or if you absolutely have to, choose the TLD of a country you live in.
That works, too. I’m on lemmy.ca. Buying a .ca domain requires confirmation of citizenship or other qualification before you can even use it.
Back in the day, like early 90’s when they were managed by the university, they also hand reviewed each request. I had a customer with a registered company name something like “Wood Supplies Canada Inc.” and they wanted “woodsuppliescanada.ca”. They rejected it because “…canada.ca” was superfluous …
If I remember correctly it’s an honor system thing. You need to declare your a citizen or PR or something
You don’t even need to be a citizen or PR, you just need to have “a Canadian presence”, which can be as simple as owning a trademark registered in Canada
Other countries have different requirements so it’s good to always check in any case.
Agreed. I went with lemmy.ca since I’m Canadian and the instance is in my country.
I also heard Lemmy should perform a little quicker for me too this way.
No, practically speaking the domain name should have no effect on access time. DNS has so many layers of caching that as long as SOMEONE has accessed the website nearby (including you), the domain lookup will be local and therefore fast.
Anyway, DNS lookup times, even slow ones, are still not going to be noticable to the end use originally.
No, I meant the instance itself. The server. The one who runs lemmy.ca is here in Canada with me.
It’s like when playing a game; You choose servers closet to you for the lowest ping time.
The other reason I neglected to mention was I like to support local. 😎
It makes a difference for a game, but it’s not really significant for a website.
The server load and resources will have a much bigger impact on performances than geographic proximity.
And you spread that server load by selecting different servers. While what you’re saying is technically true, in a practical sense if everyone picked a more local server that would be one way to achieve what you’re saying.
No because the population is not even close to being uniformly distributed geographically.
you don’t need a uniform distribution. if the server distribution mirrors the population distribution (and why wouldn’t it?), that will still achieve the desired effect.
.com and .net are under US jurisdiction they are not stateless. I could also see why the original lemmy developers would not want to use such a domain.
That may be technically true, but both TLDs are ubiquitous and it’s extraordinarily unlikely that the US will suddenly start confiscating millions of .com and .net domain names operated by non-Americans.
Nobody said they would confiscate millions of com or net domain names or random non-Americans. We are talking about the lemmy developers specifically.
But there is no reason to get a US registered domain as a non US citizen who is also not hosted in the USA.
I really doubt they’d do that either.
Do people not remember back in the 2010s when bit.ly was the main link shortener used everywhere on the internet, and then Ghadafi, the then dictator of Libya, declared the site to be incompatible with Muslin decency norms because it was used for porn? And then all bit.ly links were just dead links?
How many times do we have to learn this lesson? Domain name hacks are fun but just not worth it. And in 2023, now we have all the new TLDs. This was a dumb decision