The list of all their owned TLDs are at [0]. There is an icannwiki page with all the ones they’ve applied for, but not just the ones they currently own. 0: https://ntldstats.com/registry/Charleston-Road-Registry-Inc
No post body was provided.
Google owns TLDs: .web .meme and .lol
81–90 of 94 posts
Re: Google owns TLDs: .web .meme and .lol
#82Earlier quoted context omitted.
KiwiFarms is excluded for all the doxing and stalking material, not for "unpopular opinions".
KiwiFarms isn't the only example. And would you provide a source for your assertion?
Putting a reply here because HN won't let me reply to the other leaf comment. 1) Implicated by whom? 2) That KiwiFarms doxes, or that the doxing bothers people, wasn't my question. My question is where is it stated (convincingly) that doxing is the reason Google filters the results?
Re: Google owns TLDs: .web .meme and .lol
#83If ICANN wasn't just a giant extortion racket they would have yanked this from Google squatting on it years ago - clearly they haven't actually met any of the listed goals considering they have never used the TLD (or opened them for general availability like their original application implies). In reality all ICANN cares about is $$$
#Web3 Fixes this
Yes! We could manage internet addressing on the blockchain instead!
DNS is quite distributed already but it’s far from “democratic”. Instead of domain squatting and hoarding through through multiple private companies, we could domain squat through… multiple _other_ private companies. That’s Real Democracy™.
We could even speculate with domain names and tlds and maybe steal them from each other in completely new and exciting ways.
Maybe we could make it so only the early adopters can afford these tlds or domain names for a reasonable price and then everyone else could prop up its price until a rug pull happens.
What if we we make this system consume an insane amount of energy? Our current solution is probably inefficient in certain ways, but we can always go further!
There’s lots of possibilities! #web3FixesThis
Re: Google owns TLDs: .web .meme and .lol
#84Re: Google owns TLDs: .web .meme and .lol
#85Re: Google owns TLDs: .web .meme and .lol
#86Fix the title OP to just Google owns .meme or something since the rest is incorrect.
Re: Google owns TLDs: .web .meme and .lol
#87Earlier quoted context omitted.
These companies don't really "own" the names. They're paying $180k/yr for the privilege of ICANN delegating the responsibility of managing that gTLD to them. But this privilege isn't any kind of legal right; the company doesn't have a deed to or easement on that gTLD that would hold up in court. ICANN has just agreed, as their side of the contract, to 1. accept that company's zone-registration modifications vis-a-vis…
Our company tried to register a TLD with ICANN. ICANN's process was so complicated, when we asked questions, they suggested we hire a law firm to help us. Turns out the partner at the firm was a former ICANN employee so they referred us to their former colleague. This law firm wanted $250k up front for the application, told us it could take over 2 years, and did not offer any guarantees that the TLD we wanted would b…
If browsers supported Handshake just like they do DNS, you can bet you wouldn't have just paid 1000 bucks for a TLD. You'd probably have paid more than what it costs for a TLD under ICANN.
Re: Google owns TLDs: .web .meme and .lol
#88Google does not own .web. They were in the running to acquire it but it will ultimately go to Verisign (who runs .com) after a ~5 year legal dispute.
Yes, for a moment I thought Google acquired .web from Verisign. Latest News on .web [1]
>after a ~5 year legal dispute.
Is it finally "settled"? It seems some are suggesting Afilias will continue to sue.
[1] https://circleid.com/posts/20211228-irp-panel-sanctions-afil...
Re: Google owns TLDs: .web .meme and .lol
#89Re: Google owns TLDs: .web .meme and .lol
#90Earlier quoted context omitted.
That looks awful as a concept. I hope it doesn’t get any traction.
I wonder if it feels more natural for different cultures or language structures, to me doing something like sheets.new isn't the order I output in - something like "/new sheets" (and without the .) feels normal, natural, but perhaps because of my own personal experience and exposures.
In fairness, that's because domains are for some reason written backwards from the rest of the URL anyways. By rights, that URL should be https://new.sheets/ just as this discussion should be https://com.ycombinator.news/item?id=29769511