Hacker News Reader

Comment by blinded | Hacker News Reader

The only real way to browse the site is to be logged in.

They will gradually authwall everything they can. Just look at linkedin.

Wouldn't this break Go and other build systems (npm?) that pull packages from github by default? Not that I endorse the practise, but will Microsoft really kick out such a big class of users?

Can't count the times a "nuget restore" in our CI fails with 401, just to succeed on a 2nd attempt a few seconds later. Seems like the IP range is somehow flagged, so there's definetly a downside to it.

It does break it, from experience authorizing the pulls with a bot user fixes it.

In the case were the build happens from a github action there are standard builtin credential (workflow permissions).

https://docs.github.com/en/rest/using-the-rest-api/rate-limi...

sadly even that isn't an option for me. i spent half an hour yesterday trying to create a github account. i couldn't. my @proton.me got rejected. captchas take several painful minutes to complete. and even when I did manage to create an account (at least the page displayed a success mesage), it got disabled the instant I logged in for "TOS violation". i wish i was joking, but i literally cannot create a github account. a few years ago this would have seemed crazy. but here we are.

i'm stuck having to use google (another pain in the ass) for discovering codebases that contain specific snippets. but some repo contents (such as wikis) are not exposed at all to search engines

Could you make a throw away gmail or something?

currently gmail requires that you send (yes, send) a text to them with a code in order to sign up

https://discuss.privacyguides.net/t/google-account-registrat...

wild, I had no idea.

Take that as a hint. Make an account somewhere else. The article lists several alternatives.

having an account elsewhere won't help with the use case i mentioned

Reply on news.ycombinator.com