51–60 of 227 posts
Do TLDs even matter? I'm working on building a professional blog, and although a .dev TLD seems appropriate, using a cheaper one like .co or .be, or even .io seems functionally identical and a lot less costly. Paying hundreds or thousands for .dev seems like paying for pure vanity. Is it going to help people reach your site? I kinda doubt it. Will Google use it to index your site differently? Maybe, but I dunno. I ho…
There is one thing that annoys me about generic TLDs like .dev, .website, .cloud, .network etc. For example, Salesforce have https://crm.dev - are they the only CRM in the world? Hell no, but they're the biggest, so they can be the only one in the .dev space. Same with workers.dev.
What's your proposed alternative? That generic category names should be disallowed within a TLD? Or that some public or community-driven version of a for-profit service should control the generic names?
I wonder whether a different approach would work. Instead of basing TLD name spacing on nebulous terms (com,net,org,io,edu,etc) create a naming system that better reflects the real world. The abstracted terms lead to clashing. So addressing actually reflects physical addressing. There’s only ever going to be one company at Apple’s corporate address. Not sure how it’d work.
Edit-the tech to do this via gps even exists today.
Do TLDs even matter? I'm working on building a professional blog, and although a .dev TLD seems appropriate, using a cheaper one like .co or .be, or even .io seems functionally identical and a lot less costly. Paying hundreds or thousands for .dev seems like paying for pure vanity. Is it going to help people reach your site? I kinda doubt it. Will Google use it to index your site differently? Maybe, but I dunno. I ho…
> ...it requires HTTPS to connect to all .dev websites. This protects people who visit your site against ad malware and tracking injection by internet service providers The latter is true (it protects against injection), but I'm not sure how the former is. How would it protect against ad malware?
Me: "Wow [myfirstname].dev is available! I gotta get it!" Aaaaaaand its $11,500.
> ...it requires HTTPS to connect to all .dev websites. This protects people who visit your site against ad malware and tracking injection by internet service providers The latter is true (it protects against injection), but I'm not sure how the former is. How would it protect against ad malware?
Do TLDs even matter? I'm working on building a professional blog, and although a .dev TLD seems appropriate, using a cheaper one like .co or .be, or even .io seems functionally identical and a lot less costly. Paying hundreds or thousands for .dev seems like paying for pure vanity. Is it going to help people reach your site? I kinda doubt it. Will Google use it to index your site differently? Maybe, but I dunno. I ho…
On a recent thread Google personnel mentioned that ICANN forces all domain providers to backup their data so that any domain provider going bankrupt won't affect domains. However there was no mention of what procedures Google Domains themselves have put in place to protect their customers in case their customers get irreversibly banned somewhere within Google's vast empire. https://news.ycombinator.com/item?id=191787…
I used to work for a registry, and ICANN had very strict escrow rules for registrys'. This was for a real TLD but I suspect that there is something similar for vanity domains.
https://google.dev/ says: > There was no service found for the uri requested.