I think that particular issue is older though, I'd guess 1999 or 2000. If I recall correctly people were still going on about the information super highway around that time, along with very literal illustrations of "surfing the web." 2005 is just when the snapshot is from I think.

They fixed some awkward "custom routing" screens a while ago. I've been using my single account with different companies for years now. I just make sure my git `config.email` is set right, set GitHub to route notifications for work repos to my work email, and it's done.

I've also been the admin on those Business accounts. It's easy.

In the same way that turning up the volume helps people who are hard of hearing to hear. Colorblindness is a spectrum, not a switch; many people who suffer from it simply have reduced sensitivity to a color. I'm mildly colorblind myself; I can see green, but I can't see it as well as you can.

Upvoted because this is a legitimate question.

I'm slightly grey-green colorblind, and if you make text standard CSS green (#008000) I sometimes have trouble telling that it's actually green and not dark grey. If you make it just a little more green (say #00A000) it's much easier for me to see.

That's not how colorblindness works. Green things aren't invisible to colorblind people. They just can't discriminate some colors from others as well. I would guess that this color is more different from the body text in some color channel that's extra useful for contrast for colorblind people.

I believe that's the reference right there. Porn sites, along with most other sites, were usually not quite as spiffy as they are these days. Aside from some creative hot spots that really overdid it with the GIFs (geocities 4 life!) most sites were typically just browser defaults with perhaps some changes to background colors, maybe add a nifty tiled background image and such. Web design (not to mention development) was quite different back in the late nineties, early naughts, than what it's like now – the default blue link color was everywhere.

This whole issue is effectively a sarcastic response to that lack of design, and referring to the default blue as "the porn color" I read to mean "don't be cheap and stick with the defaults; don't be a porn site."

The joke doesn't age very well, but it was really funny back then.

It's "blueprint blue" - a reference to the cheap printing process used to make the posters for pornographic films, and also the reason they got the nickname "blue movies."

From the above Internet Archive link, looks like the color is #0033FF.

But it's not just about having access to example corp. If I log in to GitHub from my work laptop then my company technically has access to my personal GitHub account and the repos of any other organization I happen to belong to. It goes the other way around to. If an attacker hacks my personal laptop and I'm logged into GitHub then they have access to all of my companies repositories.

There are perfectly valid reasons for segregating accounts so that there is complete separation between them.

It is the first scenario not the second. The person is gaining access to the GitHub organization via SAML SSO. They are bringing their own identity and do not lose access.

I think we should give it a few months to see if the fact that it doesn't look good is inherent to the color or just because we've become accustomed to it looking one way for so long. I can't count the number of interface redesigns I've seen in services I used that I hated at first and now I look back at the old design and can't fathom how I ever thought it was better.

And if colorblind people aren't inconvenienced (and don't have to navigate to a menu to de-inconvenience themself) then that's enough of a reason for me.

    Accept: text/css; color-blind=trichromatic

Why not have colorblind mode be the default? Much more courteous to make the nitpickers change their mode than casual browsers who just want to be able to use the site.