jeffw@lemmy.worldM to News@lemmy.world · 26 days agoElizabeth Warren calls for crackdown on Internet “monopoly” you’ve never heard ofarstechnica.comexternal-linkmessage-square36fedilinkarrow-up133arrow-down10cross-posted to: technology@lemmy.zip
arrow-up133arrow-down1external-linkElizabeth Warren calls for crackdown on Internet “monopoly” you’ve never heard ofarstechnica.comjeffw@lemmy.worldM to News@lemmy.world · 26 days agomessage-square36fedilinkcross-posted to: technology@lemmy.zip
minus-squaresem@lemmy.blahaj.zonelinkfedilinkarrow-up1·15 days agoI never said they were. I just said .d means directory in another context
minus-squarewhithom@discuss.onlinelinkfedilinkarrow-up1·15 days agoWell, a .com is a CP/M binary file introduced in ~1975, whereas the TLD wasn’t introduced until 1985. So, put that in your pipe and smoke it. 😝
minus-squaresem@lemmy.blahaj.zonelinkfedilinkarrow-up1·15 days agoYeah that’s weird too. So would a TLD of .txt or .doc or can you imagine a TLD of .html? They’re all weird just to various degrees. Why would you want .d as a TLD? To me it would just be weird and confusing.
minus-squarewhithom@discuss.onlinelinkfedilinkarrow-up1·15 days ago.a, .b, .c… Why are they limiting us? Seems like ICANN has an unfair position. Someone should start a competing dns that allows domain registrations with single letter domains. That’s kind of how .onion works (for dns)
minus-squaresem@lemmy.blahaj.zonelinkfedilinkarrow-up1·15 days agoYou haven’t answered why somebody would want these confusing tlds
minus-squarewhithom@discuss.onlinelinkfedilinkarrow-up1·15 days agoIt’s not confusing. It’s just a tld.
minus-squaresem@lemmy.blahaj.zonelinkfedilinkarrow-up1·15 days agoAlright Mr. https://google.com.html
minus-squarewhithom@discuss.onlinelinkfedilinkarrow-up1·15 days agoA url is a url. If your only concern is that it might be confusing to the user, then we shouldn’t have TLDs at all. googIe.com and google.com are different. What now? Force serif fonts?
But TLDs are not “UNIX”
I never said they were. I just said .d means directory in another context
Well, a .com is a CP/M binary file introduced in ~1975, whereas the TLD wasn’t introduced until 1985. So, put that in your pipe and smoke it. 😝
Yeah that’s weird too. So would a TLD of .txt or .doc or can you imagine a TLD of .html?
They’re all weird just to various degrees.
Why would you want .d as a TLD? To me it would just be weird and confusing.
.a, .b, .c…
Why are they limiting us? Seems like ICANN has an unfair position.
Someone should start a competing dns that allows domain registrations with single letter domains.
That’s kind of how .onion works (for dns)
You haven’t answered why somebody would want these confusing tlds
It’s not confusing. It’s just a tld.
Alright Mr. https://google.com.html
A url is a url. If your only concern is that it might be confusing to the user, then we shouldn’t have TLDs at all.
googIe.com and google.com are different. What now? Force serif fonts?