Misleading headline? It links to an unresolved GH issue, so no evidence that there is an actual change of policy (rather than, let’s say, a bug, or a temporary hiccup)
There is nothing worse than some Muppet who finds what's probably almost certainly a mistake or config error and then posts alarmist and "This is now a fact" posts.
Post it like "I don't seem to be able to view unless I login" or "Does anyone else find that they need to login" not as a statement of fact.
Comments moved to https://news.ycombinator.com/newsguidelines.html)
The headline reads as if this is intended behaviour but it's clearly a bug (and it doesn't even occur when I try)
https://github.blog/changelog/2025-05-08-updated-rate-limits...
Misleading headline? It links to an unresolved GH issue, so no evidence that there is an actual change of policy (rather than, let’s say, a bug, or a temporary hiccup)
https://github.blog/changelog/2025-05-08-updated-rate-limits...
There is nothing worse than some Muppet who finds what's probably almost certainly a mistake or config error and then posts alarmist and "This is now a fact" posts.
Post it like "I don't seem to be able to view unless I login" or "Does anyone else find that they need to login" not as a statement of fact.
> There is nothing worse than some Muppet who finds what's probably almost certainly a mistake
Aged like milk within minutes
https://github.blog/changelog/2025-05-08-updated-rate-limits...
Ok, not a mistake, rate limits.
Still an A-Grade Muppet headline, because you very clearly can still browse code when you're not logged in.
Aged like wine now you've posted that.
2 replies →