I've been told that Adult sites applied for .sex, .porn, and .sucks
.Sucks
And that made me laugh. I like to laugh, so bring on more tld's.
.Sucks
And that made me laugh. I like to laugh, so bring on more tld's.
I appreciate that, but as it stands most companies will want .com or .co.wherever, rather than .net rather than .org; didn't realise .xxx actually materialised, I knew they were talking about it for a while.evilneko said:.fi is the country TLD for Finland, so that's kinda taken already.GonvilleBromhead said:I rather like the clarity of the current system. You know what the website is, and what country it's from. I wouldn't mind seeing a few more (.fi for financial institutions, .xxx for stuff you don't want the kid seeing, .cha for charities), and foreign alphabet additions are harmless...but this idea just doesn't really work for me. Rather strikes me as being allowed to change ones address to just "Google" without the street or postcode, etc..xxx already exists. .org is, ostensibly, for non-profits, in practice not so much. The current system actually isn't as you describe either. Anyone anywhere can get a .com, whether they're a commercial entity or not, similarly I can get a .net without having anything to do with being an actual network. Even country codes aren't reliably descriptive (how many .tv and .ly domains are actually hosted in Tuvalu and Libya?) Heck, the only reliably accurate TLD is .gov.
Why do I get the feeling that .sucks is going to be used more by haters and disappointed fans than actual porn? masseffect3ending.sucks... Good job that domain didn't exist during all that furore a couple of months back!Easton Dark said:I've been told that Adult sites applied for .sex, .porn, and .sucks
.Sucks
And that made me laugh. I like to laugh, so bring on more tld's.
SSL is not so easily tricked. Besides, I believe it would be very fast and easy to find out who owns the .bnk top level domain. It's like trying to scam people but doing so in your home while handing them your real CV - you can fool them but they also know who you are. Finally, would somebody really throw obscene amounts of money to try to do something that's likely to backfire? This is the Internet, you know - even if for every thousand or ten thousand clueless users there was only one "in the know", there would still be not enough time for his scheme to cover the expenses.mad825 said:Sorry but it can be used to trick people into thinking that the site is secure and the average internet user will easily get confused on true and boogie Suffixes. The current use of SSL certificates are doing just fine to be honest.
A typo like ".bnk" or ".bqnk" instead of ".bank" would be used easily to mislead vulnerable users.
A typo like that would simply lead to an error, unless your DNS provider or ISP subverts the protocol to send users to an ad-laden search page.mad825 said:A typo like ".bnk" or ".bqnk" instead of ".bank" would be used easily to mislead vulnerable users.
Google want it primarily for semantic searching. Knowing what kinds of business take up certain suffixes allows them to index and categorise the web much easier than now.PsykoDragon said:-snip-