Hacker Newsnew | past | comments | ask | show | jobs | submit | tylergetsay's commentslogin

wouldn't that be a problem with a lot of other domains? like locality domains

It definitely is. <ingress>.k8s.<mydns>.com regularly confuses what password I want to use if I have different authentication per ingress. More commonly if I run something else at <name>.<mydns>.com firefox and chrome are both happy to offer up my password for <other service>.<mydns>.com.

Closed. Wont fix.


We solve that problem with the public suffix list. The problem is there's a lot of .name domains, each of which would need to be added to the list.

yes, but other locality domains are fairly static and well-known

.co.uk wouldn't have the same problem because everyone knows that combo is a TLD in and of itself. with a seemingly infinite possible combinations of blah.name that could be a TLD itself, or, might just be a subdomain of .name, it gets really weird


> with a seemingly infinite possible combinations

Verisign claimed approximately 22,000 third level domains [1] in July 2026. I don't see an estimate of the number of shared second level domains, but it's finite. The current public suffix list includes 10414 names [2]; so at maximum, the list would approximately triple in size --- not ideal, but feasible.

Edit: another post [3] claims approximately 2000 second levels names with multiple registrations; that's only a 20% increase in size for the existing list, which is again a lot, but feasible. There's some more specific data in an issue for the suffix list [4], that shows there were nine second level domains with multiple registered names underneath them, one of which might all be the same registrant (domain.name)...

Nine would be totally doable, if the request came from Verisign...

[1] https://itp.cdn.icann.org/en/files/consensus-policies/fessen...

[2] including some with wildcards, re: your other post

[3] https://news.ycombinator.com/item?id=50446780

[4] https://github.com/publicsuffix/list/issues/2306


22,000 now, but there was no limit and more importantly no rhyme or reason or other way to tell what was a third level registration and what was a subdomain on a normal second level registration

Verisign could have published a list of every third level registration, it wasn't an impossible problem to solve, but it is different than static regional TLDs like .co.uk or .<state>.us


If your machine has a TPM chip you can also use that and require a PIN to unlock it, with a mandatory lock out period enforced by the chip

Toyota also uses flutter for their infotainment

For really long runs in industrial settings they have battery powered pullers that use a really strong string.


Palworld is an actually good game


That's precisely my point.


It's a prisoners dilemma. The total market share remains the same, but if only one grocery store was on DD they'd be at an advantage over those who don't


These grocery stores are all going to continually lose market share to Amazon, Walmart, etc. as online ordering increases. The pricing of in person grocery stores is outrageous and the experience shopping at them is annoying. I hope to see many go out of business sooner than later so we can have better businesses take their place!


When shopping from kroger you can pay extra to get 2-3hr delivery from insta cart. If not your order gets routed through a more efficient planned route that hits multiple houses


I believe the CEO of Ford something along those lines


Incase anyone was unaware part of the consideration for where to sink it is access for divers -- the top will be around 55ft deep which will make it accessible for recreational divers


>The ship is expected to rest in approximately 55m (180ft) of water, with her upper decks reaching depths of around 17–18m (55–60ft), making the wreck suitable for recreational and technical divers alike.

It should be very good for both


Between 55 feet and 55 meters, how poetic.


Or about 33 wash machines or half of a (US) football field


Are those imperial or metric washing machines?


Ironically, Whirlpool.


The block chain can't though once the coins are transferred


That assumes the key is actually on the server.


I assume even if it isn't, attacker could deface the website so heavily everyone would know they win.


The server could simply be running a patched PHP.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: