http://ff6600.bikeshed.com/ to be precise.

I'm impressed with how much effort he put into his dynamic subdomain parser.

More obscure colors work as well:

http://fuschia.bikeshed.com/ http://limegreen.bikeshed.com/

He does NO parsing; the subdomain is literally applied to the <body bgcolor="{{ subdomain }}">. http://libria.bikeshed.com/ http://thezilch.bikeshed.com/

Happy to see browsers are still shipping with a "crap" color :^)

http://crap.bikeshed.com/

If you look at the page source he actually does parse the color to determine if the text should be white or black.

To be pedantic, he does NO parsing _of the subdomain_; he "parses" the computed-style color designated by the browser's parser.

I wrote that javascript, and I like my bikeshed painted pedantic (http://pedantic.bikeshed.com/)

Happy everyone is enjoying it!

It's too bad the original post and no comment links to http://bikeshed.bikeshed.com/. The best kind of right.

NOTE: RELATED: /bikeshed in Google Hangout takes on a similar role.

> To be pedantic, he does NO parsing _of the subdomain_

To be correct, he parses the subdomain. The input is what is "parsed".

At best, he parses the hostname / FQDN to extract the subdomain; after which, my previous post applies.

> after which, my previous post applies.

Which is to say it doesn't apply at all since you meant to refute parsing of the subdomain. It's okay to be wrong, just admit it.

Hopefully no one will notice your consistent troll posts.

Except that it's http://fuchsia.bikeshed.com/ :)