Slashdot Mirror

It would make much more sense for ICANN to accept registration of a domain by name and then they just register the subdomains while the main domain is held unregulated by the owner. This would yield proper operation of Slashdot's domain of SLASHDOT.ORG to be organized as a service of http://org.slashdot/ in structure. By ICANN registering Slashdot as the domain then it would be reserved to Slashdot for not only ORG but also COM and NET and all the others. It just makes more sense.

Yeah. Though arguably even 31/12/1990 is suboptimal, it -does- have the advantage of not having the least-significant-part in the *middle*, but it still, for example, sorts wrong regardless of if you sort numerically or alphabetically.

Generally, the most significant part should be -first-

1990-05-30 is superior for this reason, it sorts correctly both numerically and alphabetically, and follows the general convention we have of having the most significant part come FIRST.

URLs suffer from the same problem, with the most significant part being in the middle of the URL. It would really be a lot more logical to have:

http://org.slashdot/folder/file

Yea I thought this the same as you, but then I realized that these aren't actual domains but supplemental suggestive presumed profiles of the content to be hosted through that reservation. .COM, .NET, .ORG, .GOV...it's all redundant because all self-governing or quasi-governing organizations are in commerce to host a route to their network for commercial purposes. The entire registry scheme is bogus in that regard, and the country code scheme you and I would originally agree to is actually debased from any relevance because the nature of that directory system impedes the 1st-come 1st-serve independent registries.

I would prefer ICANN kicked-out so an independent Torrent-like replacement would replace what ICANN ever could accomplish. I always asked myself why any governing agency would require their ardent domain suffix when it has no logical purpose at the root servers. DNS is nothing more than a turring of a tiered DHCP server. We all should be able to type http://slashdot/ and we arrive here, and instead have domain prefixes that suggest the function of a server to reference like http://org.slashdot/index.html for organizational structure or http://com.slashdot/index.html for commercial pursuits: all determined by the owner of that Slashdot domain.

Obviously ICANN is the reason DNS sucks.

This was how domain names were written on JANET and a few other networks in the '80s and early '90s. It made more sense, because going from left to right was a progressive refinement. The weird middle-endian system we seem to have ended up with is just confusing. This article would be http://org.slashdot/article.pl (and so on).

Should be http://org.slashdot/comments.php

You want to see Slashdot rewritten in *PHP*?!

True. Either way, aslong as it's consistent.

The most-significant part could be at either end, aslong as it's consistent.

Except with URLs it's not. The most significant part is in the MIDDLE which is plainly braindead.

http://3.2.1/4/5

That look like a sensible arrangement to anyone ?

Atleast with email it's 3@2.1 so in a sequence, though the oposite one from the one we -normally- use.

US dates share the same sillyness. day-month-year is fine, as is year-month-day, but whoever decided on putting the least-significant part in the freaking MIDDLE as in month-day-year ?

Should be http://org.slashdot/comments.php

http://org.slashdot/ or is it org.dotslash://http or org.dotslashcolon://http or.... ah, hippo it!