Mmh, wasn’t .ml a commie place? Maybe everything went better than expected
Well I think some instances like lemmy.ml interpreted the domain as marxist-leninist, but over the whole web this will be the minority. Many websites covering machine learning use(d) that domain.
The domain bs is a interesting case of scummy practices in general, .tv was missused in a similar way with awful contracts, essentially scamming a already increadably poor country!
TLDs are a non-tangible arrangement of characters that are defined by a committee at a whim. The countries they are given to have not contributed anything to make them worth more. I don’t see how that can be seen as a scam when they don’t get free money based on a random decision by someone outside of their country.
Didn’t Tuvalu massively benefit from being assigned a TLD that is popular? I read they were able to build an airport with .tv money
They reclaimed many domain rights and are now renting them out for big money, yeah. They were still scammed off by many.
This brings a disturbing thought to mind… if an instance domain name like foo.bar lapses and someone else snaps the domain up (or of it gets stolen) can the new controller plop Lemmy on a server and be instantly federated? If so what kind of damage could they do?
This is why you don’t let your domain registration lapse. It’s not the only way computers on the internet verify each other’s identity, but a hell of a lot of internet security features are based around domain names, so keeping yours functioning is a very big deal.
Domain registration ≠ internet security. Root of trust is in cryptographic keys, not domains. DNS is not the security cornerstone you make it out to be. PKI says hi!
Yes, but it is very quick and cheap to get a domain validated cert from a CA that is generally trusted by most web browsers, so once the bad actor has the domain, the should be able to trick most users, only maybe certificate pinning might help, but that is not widely used.
Man, hacking, DDOS and now this. The fediverse just can’t catch a break…
I cant believe this is just coincidence. This is coordinated.
Hi, professional DNS engineer here! if anyone has any questions about the inner workings of DNS or top level domains, ask away! (THIS IS MY MOMENT)
We had a situation at a shared space here where an OpenWRT client device accidentally somehow managed to announce itself into the network in a way that its v6 local link address (
fe80::) got inserted into /etc/resolv.conf as a third DNS option (with the first two being the ones from DHCP) and then served incorrect records when queried. What mechanism is that and were the engineers who designed that feature on drugs? Also, how can I tell my Linux system to not accept such announcements?
