Why was the name of this post adjusted to remove mention of Kenneth? I think that the fact that this is Kenneth Reitz is a major element of this story.
https://hn.algolia.com/?sort=byDate&dateRange=all&type=comme...
A nice fix would be if github.com/username could appear to the right of the title instead of just github.com. That's on our list, but not implemented yet.
On HN, the one thing we're optimizing for is intellectual curiosity. That's merely one kind of curiosity and by no means the most powerful. Interest in personalities, especially celebrities or the infamous, tends to be fuelled by one of the higher-octane varieties—call it social curiosity. There's nothing wrong with social curiosity. It's human. But intellectual curiosities are smaller fish than that, and on HN we need to do things to prevent the bigger fish from eating them all up. Everything in our bag of moderation tricks is there to help with that.
Your optimisation approach seems to me to be working out nicely.
Edit note: At the time of writing, the article title did not include "Requests".
The most notable repo involved is "requests", an HTTP library more widely used than the one in Python's standard library (I'm under the impression it has become bundled with the Python standard install but am unable to find a citation for that).
How about changing the title too "Python requests library and other repos seeking new home"?
i'd generally expect titles to be close to the original title of the post. and the first version of the title just doesn't feel like a title that anyone would put onto a post, let alone an issue report in a tracker. with 'requests' added it feels more real and interesting.
edit: i was thinking of this title "Issue: find a new home for repos" which is not the original one. somehow that "all" makes a difference, as does adding "request"
If people encounter a title that doesn't fully yield to 300ms of parsing, that causes irritation, which is a good thing. Not good in itself—irritation is a bit painful—but good because it causes the rapid-reflexive subsystem to throw an error and pass control to the slower, reflective system that is able to process more information. That's the system we actually want to get activated. One's it's engaged there's a chance that it will remain engaged, which—this is the hypothesis anyway—will lead to higher-quality thoughts and comments. That's why I say it's good for HN users to have to work a little.
"You won't believe who's giving a way a repo
#2 will shock you"
That kind of title operates even less by intellectual curiosity than the kind I was talking above, so it's even worse for HN. They are the kind we edit and everyone agrees with the edit.