You must never use this colour.
You can like it as much as you want.
You can buy a dress in this colour for your girlfriend.
Your mum might have it as the colour of her eyes.
Feel free to paint your house like it.
But never use it on a website. Never.
This colour is the porn colour.
You must never copy the porncolours.
Still cracks me up.
EDIT: for those who have no idea what k10k was, here's the story: http://www.cubancouncil.com/work/project/kaliber-10000
Aren't links blue (#0000ff) by default?
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.
The new color is #0366D6, while the old color is #7FA5CF. The new blue color is far more saturated and is much less light, but is actually still a pretty big step down from ultra-hard blue #0000FF. IMO, it's much more readable than the previous blue and stands out nicely.
github.css: https://www.diffchecker.com/STyCXVyk framework.css: https://www.diffchecker.com/x1uMGh3h
It makes sense to separate access ("this person has access to Example Corp's repos only as long as they work for Example Corp") from identity ("this person owns this account").
Introducing single-sign-on as one way to simplify login, and potentially as a second-factor for gaining access to repositories run by the business, makes sense. Making developers create entirely separate accounts doesn't.
There are perfectly valid reasons for segregating accounts so that there is complete separation between them.
I am happy that they continue to add features like this, but I feel like some of the more common wishlist items are not being addressed.
you can use the "user:" search operator + the name of the topic to filter your repos and then just bookmark the searches that youll be using often. its better than nothing for now