This plus 2FA is a perfect combination for headaches. I'm already often not logged in while browsing GitHub because 2FA on every login is a pain, and now they're taking away features?
GitHub doesn't show search field unless you sign in
61–70 of 95 posts
Re: GitHub doesn't show search field unless you sign in
#62Earlier quoted context omitted.
Google rate limits unauthenticated sessions. Try using Google over tor. They are pretty heavy-handed about it too. Github isn't tiny enough to use ddos as an excuse.
TOR still uses cookies so a session ID can be set for the user agent and rate limited. DDOS scripts create new sessions on every attack request. It's a very hard problem to solve without blocking legitimate traffic too.
Well, at some point you have to block legitimate traffic. My thought was it doesn't have to be black and white. Maybe require the user to solve a captcha after the nth search from the same IP address? How big are the biggest of botnets? A few hundred thousand computers? Or maybe even require captcha for every unauthenticated search.
Re: GitHub doesn't show search field unless you sign in
#63Earlier quoted context omitted.
I feel like this is a part of a trend that reflects how github itself is changing - slowly making access to things harder, then finally removing it. Github used to have an awesome and public way to explore projects ( http://web.archive.org/web/20130730125837/https://github.com... ) - I remember using it a lot to look for projects to learn to read code because it allowed me to easily find projects by language. They re…
OTOH, a trend towards self hosted solutions will only make finding projects to explore harder.
gitlab.com is a fine compromise, albeit I'm not a fan of their "private repos for free" model, it means a lot of software that might have utility if it were default-open will be lost behind default-privte repositories.
But if gitlab jumps the shark like github is doing we can always have anyone in the ecosystem selfhost a clone, albeit we would need to reimplement all the enterprise features people want.
Re: GitHub doesn't show search field unless you sign in
#64Maybe it was just disabled due to load issues from web crawlers, no bad intent? Personally that seems the simplest explanation.
Re: GitHub doesn't show search field unless you sign in
#65Just go to
https://github.com/search
Re: GitHub doesn't show search field unless you sign in
#66I noticed this a few days ago at work. I don't want to sign in to my personal Github account at work, but I'd still like to be able to search within a repo. I've been searching for code snippets with Google recently with lower (but non-zero) success rate.
Re: GitHub doesn't show search field unless you sign in
#67Earlier quoted context omitted.
I feel like this is a part of a trend that reflects how github itself is changing - slowly making access to things harder, then finally removing it. Github used to have an awesome and public way to explore projects ( http://web.archive.org/web/20130730125837/https://github.com... ) - I remember using it a lot to look for projects to learn to read code because it allowed me to easily find projects by language. They re…
OTOH, a trend towards self hosted solutions will only make finding projects to explore harder.
Self hosted solutions lend themselves towards being freely indexable via search engines, many of which are optimized towards source code repositories.
Re: GitHub doesn't show search field unless you sign in
#68I was banging my head against this earlier last week. It was such a jarring change to visit GitHub and not be able to navigate. It gives me pause to see how suddenly an easily-navigable site can become almost impenetrable with the removal of a single search bar. What are they thinking? The "Explore" menu is worse than useless, too. It is an interesting case study in UX - the difference between a great experience and…
For me search if one of GitHub's key features. It's nice to take a look other people's code, explore other coding styles, find examples of library usage which is great for under documented code.
Unfortunately it does let you escape common characters that are common in code, doesn't give you the option of maintaining white space/line breaks in your query, doesn't let you search in other branches.
Re: GitHub doesn't show search field unless you sign in
#69Earlier quoted context omitted.
TOR still uses cookies so a session ID can be set for the user agent and rate limited. DDOS scripts create new sessions on every attack request. It's a very hard problem to solve without blocking legitimate traffic too.
Well, at some point you have to block legitimate traffic. My thought was it doesn't have to be black and white. Maybe require the user to solve a captcha after the nth search from the same IP address? How big are the biggest of botnets? A few hundred thousand computers? Or maybe even require captcha for every unauthenticated search.
Millions.
Re: GitHub doesn't show search field unless you sign in
#70Earlier quoted context omitted.
OTOH, a trend towards self hosted solutions will only make finding projects to explore harder.
gitlab.com is a fine compromise, albeit I'm not a fan of their "private repos for free" model, it means a lot of software that might have utility if it were default-open will be lost behind default-privte repositories. But if gitlab jumps the shark like github is doing we can always have anyone in the ecosystem selfhost a clone, albeit we would need to reimplement all the enterprise features people want.
In my experience it was the other way around. I signed up with gitlab only because they offer free private repos. Now since I already have an account with them and I don't have to go through the hassle of setting up stuff again, I'm only a couple clicks away from putting some project in the open.