Programming

28431 readers

85 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

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 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

186

Github confirms random 401 responses on unauthenticated git clones are no mistake (eviltoast.org)

submitted 1 week ago by orhtej2@eviltoast.org to c/programming@programming.dev

78 comments fedilink hide all child comments

Since yesterday a lot of users in Europe found their workflows failing due to Github seemingly randomly throwing HTTP/401 on git clone/git pull when interacting with public repos without authentication.

It was now confirmed by staff member that this indeed is intentional and no further steps are planned at this point.

you are viewing a single comment's thread
view the rest of the comments

[–] esc@piefed.social 7 points 1 week ago (2 children)

I believe that it is some fuckup and they don't know where exactly problem is and while they are looking for a way to fix it they've created plausible lie. When they'll fix it or believe that it's fixed there would be a public announcement like 'we heard the community and reversed our decision' and users will be happy. There is a serious need for github mirror, they are becoming less and less stable every year.

[–] orhtej2@eviltoast.org 13 points 1 week ago

I'm 100% sure this is damage control on their part, they refused to acknowledge the incident and are looking for their way out.

What users found in this thread is

problem is limited to EU
problem is limited to subset of git builds (gix version x TLS lib x TLS lib version in place)
problem goes away if you switch back to HTTP/1.1 for some reason

If these are LLM scrapper mitigation steps then apparently fighting LLM scrappers is 7D chess game or something 🤷

[–] Dirk@lemmy.ml 5 points 1 week ago

The Microslop marketing department was always their best department.