Tell HN: GitHub is blocking search unless you are logged in
41–50 of 76 posts
Re: Tell HN: GitHub is blocking search unless you are logged in
#42This has been the case since the new code search replaced the old one ~9 months ago. The new code search is more resource intensive so Github chose to only make it available to users. I agree that it sucks to not have code search available when logged out, but it's not a new change and I don't think it was done with malicious intent.
Re: Tell HN: GitHub is blocking search unless you are logged in
#43It's time we all moved away from GH
Re: Tell HN: GitHub is blocking search unless you are logged in
#44Re: Tell HN: GitHub is blocking search unless you are logged in
#45Re: Tell HN: GitHub is blocking search unless you are logged in
#46Re: Tell HN: GitHub is blocking search unless you are logged in
#47Re: Tell HN: GitHub is blocking search unless you are logged in
#48Earlier quoted context omitted.
I think this will be the new normal. There are a lot more AI projects hungry for data to train their models on. This puts content companies in an uncomfortable situation: trademark infringement claims, loss of intellectual property, and more.
But Github is not a content company and they don’t really own copyright to almost anything hosted there.
Re: Tell HN: GitHub is blocking search unless you are logged in
#49Earlier quoted context omitted.
Seems like a good time to mention that (despite anecdotal lack of enforcement) GitHub's terms of service continue to officially forbid having more than one free account for manual use. https://docs.github.com/en/site-policy/github-terms/github-t...
Can they let their business customers know that? Companies making their employees create new accounts for their org is not uncommon. I’m not talking about Enterprise instances.
Telling employees to make their own personal account to do company work seems like a bad idea.
Re: Tell HN: GitHub is blocking search unless you are logged in
#50I’ve been running into this too and it’s very annoying. Although I don’t think it’s particularly new either. Just feels like an unnecessary step. Sure I have an account and can log in, but why? I just want to know which file has X function, so i can read the implementation. I don’t want to have to download the repo or sign in.
Most likely anti-scraping measure. So they can detect and shut down bots or really anyone they feel like if activity looks nonstandard. Not suggesting it’s good, but it’s consistent with the in vogue trend to lock down recipient public APIs nowadays.
If necessary, let's focus on the use case of searching a single repo.