I went to look at a repo on Github today. Clicked on the "xxx commits" link to see the commit history, and got told I've hit a secondary rate limit and need to wait.
I'm the only person on this network that would even look at Github, and my connection has a dedicated IP, no CGN.
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.
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
Yeah this is just typical techbro gaslighting. There is no rate-limit and hasn't been for years (it's just default deny), but they refuse to change the wording to reflect.
The parent's experience which mirrors my own - on a clean residential IP that hasn't sent any traffic I hit that "rate-limit" on my first request to the commits list view.
So there is no rate-limit, it's a default deny for unauthenticated requests... which could be fine but at least update the error message to reflect that.
Computer used to mean "human who does math". Before machine computers, we had human computers. Machine computers replaced all of these human computers.
> But how is it any different from keeping them open?
If all open issues are actionable items, that makes expected workload a lot easier to handle.
If most open issues are actually in "needs triage / needs review" state, you lose the signal from the noise.
The issue tracker for a project exists primarily as a tool for maintainers, not for outsiders. Yes, the maintainers could change their workflow to create a new view that only shows triaged tickets.
Or, they could ensure the default 'open' view serves their needs.
Somehow going through closed issues just to reopen them sounds like more effort than just using the built in label system which is made for this purpose, but maybe that's just me.
I don't think the GP is calling contributor guideline restrictions a form of DRM.
I think the GP is focusing on:
> I guess we're giving up on the idea that you're free to do whatever you want with software you own? ... But I see this as no different from DRM and user hostile
If I clone an open source git repository, I should be free to point an LLM to review it in any way I choose. I can't contribute code back, but guess what, I don't want to. I want to understand the codebase, and make modifications for me to use locally myself. I don't have a dev team, I have a feature need for my own personal use.
The LLM enables that. The projects that deliberately sabotage the use of LLMs cease to be providing software that meet the 'libre' definition of free software.
I think the other way to think of it is: You're still free to do whatever you want with a the repo. The restriction is happening on the LLM's end, so ultimately it's the LLM's fault, so use a LLM without the restriction you want to avoid.
> The projects that deliberately sabotage the use of LLMs
They don’t though. They add a mild inconvenience for users of a specific restrictive AI provider which has bizarrely glitchy checks.
In a way they are doing you a service if you are this serious about libre software you shouldn’t be using a closed platform which employees dark patterns to begin with.
> Respectfully, After a certain level of compensation, you are indeed judged purely off of input and output. Workplace improvement does not justify your salary.
I'd have to disagree. There's a narrow band in the middle where that's true, but once you exceed that, your personal inputs and outputs matter less and less, and the contributions you make to the overall workplace, and how well you enable those around you, make a larger part of why you're compensated.
Even as an IC, the more you're able to mentor and elevate the people around you, the more your compensation will grow (if you're in the right place, and thus already at the right earnings bracket)
Rosetta 1 delivered 50-80% of the performance of native, during the PPC->Intel transition. It turns out, you can deliver not particularly impressive performance and still not ruin your app ecosystem, because developers have to either update to target your new platform, or leave your platform entirely.
You can also voluntarily cut off huge chunks of your own app ecosystem intentionally, by giving up 32bit support and requiring everything to be 64bit capable.
...because users have no other choice when only one vendor controls the both the hardware+software. They can either use the apps still available to them, or they can leave. And the cost of leaving for users is a lot higher.
And yet my wife will disagree hard with you, as all her fingerprints on my laptop screen will attest to. She always defaults to trying to swipe the screen instead of going to the mouse.
> Touchscreen computers have failed for a reason.
The only people who think touch screens have failed are people who actually use computers, and we are a tiny minority of the population these days. The majority of people live on touchscreen devices already.
> This has been my theory for a while: during this autumn Apple will release a version of Apple Intelligence that runs locally and works better than ChatGPT.
In this theory, can you explain why Apple has announced it’s paying Google for Gemini too?
Eventually, this may be true. This autumn? Highly unlikely.
I'm the only person on this network that would even look at Github, and my connection has a dedicated IP, no CGN.
reply