this post was submitted on 27 Nov 2023
187 points (100.0% liked)

Programming

423 readers
4 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
187
GitHub: Can no longer search code without being logged in (github.com)
submitted 11 months ago* (last edited 11 months ago) by mac@programming.dev to c/programming@programming.dev
32 comments fedilink hide all child comments
 

Edit:

Since theres been some confusion with dates

In 2016 github made site side searching login only and hid the search bar if you werent logged in. This didnt include searching within a repository so that could still be done, just not all repositories

This year was the change being referred to in this link which made repository level searching require logging in

Blog post: https://github.blog/changelog/2023-06-07-code-search-now-requires-login/

top 32 comments
sorted by: hot top controversial new old
[–] SamsonSeinfelder@feddit.de 103 points 11 months ago (2 children)

Hey Guys, Microsoft is cool now, they really care for Open Source now, they changed.

How do people always forget, how often they get fucked by that company in the last 20 years, that they think anything changed? They still abuse their monopoly, they still buy up the work of others and they still will then dilute it down for their bottom line and restrict it to force you to use a login to harvest data on your profile (see also Windows).

Everyone who said it's cool that MS bought Github, because they are now Pro-Open-Source: Can we please have a round table every 2 years and talk. Because I think you guys are victims of the Stockholm syndrome and do not even notice.

[–] technom@programming.dev 2 points 11 months ago

Apparently, this change was in 2016 - before MS bought them. However, I agree with your point. But the proof of that isn't in restricting search to logged in users. It's in how they ripped off FOSS code (esp GPL code) for training copilot. They did something that fundamentally damaged the roots of FOSS activity.

[–] Jaysyn@kbin.social 1 points 11 months ago* (last edited 11 months ago) (2 children)

restrict it to force you to use a login to harvest data on your profile (see also Windows).

FYI, there is no forcing here. Heavy suggestions, but no forcing. I've never used a MS or Hotmail account to log into Windows 10 or 11.

[–] stifle867@programming.dev 14 points 11 months ago* (last edited 11 months ago) (1 children)

On new installs it does force you. I had to do it today (Windows 10). There are workaround such as attempting to log into a banned account, or other weird hacks involving disconnecting the internet and know the right combinations of hidden menus to navigate.

load more comments (1 replies)
[–] ParetoOptimalDev@lemmy.today 2 points 11 months ago

If some has to know to unplug the internet, try to sign up, and force an error to bypass sign up...

It is forcing.

[–] agilob@programming.dev 78 points 11 months ago* (last edited 11 months ago) (5 children)

Fantastic way to start a shitstorm. You people don't even use search function logged out, because if you did, you would know they changed it in 2016. Microsoft has nothing to do with it.

https://news.ycombinator.com/item?id=11321623

[–] mac@programming.dev 42 points 11 months ago* (last edited 11 months ago) (1 children)

searching across all of github was made to be logged in then

repository level searching though is relatively recent. Heres the blog post about the change dated in June this year https://github.blog/changelog/2023-06-07-code-search-now-requires-login/

This comment by an employee in the thread also calls out it was in 2023 and links to the blog post

[–] agilob@programming.dev 3 points 11 months ago

Heres the blog post about the change dated in June this year

Half year too late for that outrage anyway :)

[–] burliman@lemm.ee 20 points 11 months ago (2 children)

I’m getting so exhausted with the constant outrage in every goddamn feed in my life.

[–] whoisearth@lemmy.ca 5 points 11 months ago (1 children)

Ignore it, laugh and increase your awareness that people are dumb as shit but also have the humility to realize you're also people and are also dumb as shit.

It makes life far more palatable.

[–] Ringmasterincestuous@aussie.zone 3 points 11 months ago* (last edited 11 months ago) (1 children)

So begins our final transformation… idiocracy

[–] whoisearth@lemmy.ca 2 points 11 months ago

The alternative is depression

[–] emptiestplace@lemmy.ml 3 points 11 months ago

do a post

[–] TheHobbyist@lemmy.zip 13 points 11 months ago

I have been able to search logged out within a repository, up to this year. I think what you are referring to is search across all repositories. That was indeed disables a while ago. But things did change this year, unfortunately. So yes there is a legitimate and new issue... Once more.

[–] onlinepersona@programming.dev 2 points 11 months ago

It's not new, but it's possible that this is the first ticket created to discuss it. I don't search github using their shitty search anymore anyway: Long live https://sourcegraph.com/

[–] mark@programming.dev 1 points 11 months ago* (last edited 11 months ago)

This is helpful. Thanks. Didnt even realize it. No need to use something to point out how its not a good look. It's still good to bring more awareness around how sites like Github are becoming a more of walled gardens. I agree with everything else you said though.

[–] lysdexic@programming.dev 20 points 11 months ago (1 children)

The biggest news to me is that GitHub allows users to search code. Every single time I tried to search something in GitHub, search results were next to completely useless, and always a sure-fire waste of time and effort.

There's hope, I guess.

[–] SinTacks@programming.dev 32 points 11 months ago (2 children)

lol? That must have been a half ass attempt on your part because GitHub search is fantastic.

[–] lysdexic@programming.dev 6 points 11 months ago

must have been a half ass attempt

How hard do you need to try to use a feature for it to be considered decent? Do you expect something as basic as a search to put up a fight?

[–] NotSteve_@lemmy.ca 3 points 11 months ago

I don't find the search too bad but what does make it difficult is digging through a million forks of a library. Sometimes I want to find how other people used an obscure library method and I end up having to wade through endless forks with the same repeated bit of code.

This is more a complaint of people using forking as a like button but I do wish there was an option to exclude them from search.

[–] onlinepersona@programming.dev 10 points 11 months ago

Honestly, I can't wait for Forgejo to implement federation. Gitlab might do so too after Forgejo shows that it's possible and gets a major following. They already are letting one external dude implement it after having slept on it for a good decade.

[–] ISometimesAdmin@the.coolest.zone 9 points 11 months ago (7 children)

Fuck's sake, people. Gitlab already didn't allow search unless you were logged in.
This ain't enshittification.

load more comments (7 replies)
[–] Jaysyn@kbin.social 7 points 11 months ago

And this is why my Org rolled our own Gitea server.

[–] farcaller@fstab.sh 5 points 11 months ago* (last edited 11 months ago)

FWIW Sourcegraph chrome extension adds a neat “open in Sourcegraph” to github pages and SG is just superior. Why would you use Github's mediocre search either way ¯\_(ツ)_/¯

[–] Anders429@programming.dev 3 points 11 months ago

It's been this way for years. Really?

[–] ParetoOptimalDev@lemmy.today 2 points 11 months ago

Microsoft sucks for this, outlook, "open source vscode", and many other reasons.

That said my current workaround is to use sourcegraph.