178
Github confirms random 401 responses on unauthenticated git clones are no mistake (eviltoast.org)
submitted 4 days ago by 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
[–] 7 points 4 days ago (1 child)

Well given the waves of "buy book, scan, scrap" scrappers might become an acceptable version as well soon.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 4 days ago (1 child)

    We’re talking about AI bots scraping GitHub in this post. Nothing to do with books.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 3 days ago

    Yes, and I was talking about the practice of some AI companies buying books in bulk to feed to their LLMs en masse which sometimes/often destroys the book in the process.

    I was trying to build a bridge between those two related topics to "justify" the mistake and make it an intentional remark instead.

  • permalink
  • fedilink
  • source
  • parent