*.name isn't a good solution either, because the vast majority of registrations are at the second level.

If you want to do it properly, you really do need to include all of the second level domains that have more than one third level registrant. And update that periodically as domains expire... there might be three registrants under .example.name today, but if they all (or all but one) stop paying, example.name is no longer a public suffix and it should be removed.

▲

OkayPhysicist a day ago | parent [-]

Having "no cookies shared between subdomains" as a restriction on the entire TLD isn't completely beyond the pale. There are other TLDs that have restrictions, like HTTPS being required for .dev

▲

toast0 a day ago | parent | next [-]

Having it imposed on existing registrants after the fact really is beyond the pale, IMHO.

It'd be one thing if it was there since the beginning, like https for .dev, but it would probably break existing sites if you add it after the fact.

▲

londons_explore a day ago | parent [-]

With only 22000 registrants, the number of sites broken might be just a handful.

	▲	toast0 a day ago \| parent [-]
		It's not 22000 registrants for .name, it's 22000 registrants of third level domains. There's lots more second level registrations in .name; it is massively more popular to register a second level domain, but it wasn't always an option.

▲

thbb123 a day ago | parent | prev [-]

How can they enforce that? If my DNS config points www.mydomain.dev to my vps, what can prevent me from answering on port 80?

	▲	swiftcoder 16 hours ago \| parent [-]
		No cookie sharing between subdomains is enforced client-side, not server side.