What a bizarre move.

Reminds me of the chaos monkey. Building resilience by breaking and fixing stuff.

Not sure if applicable here, though.

Github should focus on getting their core offerings in shape first.

I stopped using GH actions when I ran into this issue: https://github.com/orgs/community/discussions/151956#discuss...

That was almost a year ago and to this date I still get updates of people falling into the same issue.

This reminds me slightly of some copilot nonsense I get. I don’t use copilot. Every few days when I’m on the GitHub homepage the copilot chat input (which I don’t want on my homepage anyway) tells me it’s disabled because I’ve used up my monthly limit of copilot.

I literally do not use it, and no my account isn’t compromised. Trying to trick people into paying? Seems cartoonishly stupid but…

I cannot recommend Gitea enough. It is easy to install, can be very well integrated into the usual corporate Microsoft networks (ldap/adfs) and has very simple workers, which just reliably execute the actions defined in the .gitea folder of your repository. Installing workers is an extra step, but you don't really need a PhD to get it running.

You can build a very efficient and reliable CI pipeline this way and you are not dependent on third parties at all. The interface is mostly 1:1 Github. Just the bullshit is ripped out.

Well, this behavior makes sense. They're a bluechip trying to maintain the illusion that theyre a growth stock juuuust a little bit longer.

Ah, the critical problem dilemma. Some percentage of free users become paid users, but the free users take up an unreasonable amount of your time/energy/support.

The solution seems simple. Buy their product.

I don't follow, we pay them for the actions and everything and still ran into this issue.

That's why it's an issue.

What's the issue, as you see it?

I've quoted the response on that ticket below. Is there something you disagree with? The "issue" is that usage exceeds the amount that's been paid. The solution sounds pretty simple: pay for your usage. Is your experience different somehow?

> If usage is exceeded, you need to add a payment method and set a spending limit (you can even set it to $0 if you don’t want to allow extra charges).

> If you don’t want to add billing, you’ll need to wait until your monthly quota resets (on the first day of the next month).

Edit: also, one of the other comments says this:

> If you’re experiencing this issue, there are two primary potential causes:

> Your billing information is incorrect. Please update your payment method and ensure your billing address is correct.

> You have a budget set for Actions that is preventing additional spend. Refer to Billing & Licensing > Budgets.

I paid or tried to for the extra billing, I followed all the instructions and still got the same error. Attempts to get help land you in that catch-all issue.

Its a problem with their own systems and it's easier to role out your own alternative than to get a handle of a support person.

> The solution seems simple. Buy their product.

Buying half baked software would probably encourage this. Quarter baked software!

GitHub made more things free than in the past after MS acquisition, so this is driven by them, not just by users, making your 'buy their product' not really viable in this case.

I remember having to pay to have private repos in the past, but I guess MS didn't want my money and now I am a free user. If they offer stuff for free, doesn't mean it should be unreliable and best effort.

Looks like the issue linked above affected both paid and free users.

"In shape" in what sense? This is just hitting the limits of a free account, and the message clearly states that.

> people falling into the same issue.

Every SaaS provider with a free tier has this issue. How do you suggest it should be addressed?

As I stated above, the problem is that even when I tried to pay, it was still failing under the same error.

I don't mind paying for software, I hate paying for half-assed, unsupported software.

This affected (probably still affects) paid and free tier users. There’s obviously some corrupt state for some accounts on the backend. As stated in the issue, if you are successfully able to engage support they’re gonna run a script to get your account unstuck. I’m reading between the lines a bit, but that seems to be the gist of it.

I've been a paying Github user for years now, and as an open source maintainer who uses Github Actions, I'm annoyed that my money has been funding AI bullshit instead of fixes and improvements for their core offering.

Yes, exactly I had to stop myself starting the game after 7 else I don't sleep

We were building on C# Godot and I think it is a second class citizen in the sense that 1) you can't export to wasm and 2) they are moving the interface to be handled by gdextension.

That said, I think once you get the gist of it and understand the landmines, it is really nice to use vanilla dotnet rather than unity's fork.

Yes, exactly. The discourse has been so far off the rails now.

The universe is infinitely detailed and incredibly complex. These machines are and will remain for a while anchored to solving problems that we as a species have solved before. Seek the problems and tasks that are novel, that are groundbreaking and meaningful. Seek the boundary of knowledge and craft, what neither human nor machine has done. Seek the problems that require both humans and machines.

I frankly don't understand why they keep CC proprietary. Feels to me that the key part is the model, not the harness, and they should make the harness public so the public can contribute.

Yes, this article was one of the best articles in the last few years. And to this day I think about it. It has that property of good writing that lingers with you way after you read it.

Can't wait to read the book!

Yes, I think this makes sense. I think if you are paying by token w/ an API key, then you're good to go, but if you're hijacking their login system then that's a different story.

Nice to see an egui project that doesn't have super obvious egui aesthetics.

How did you find working with egui?

egui is fantastic for rapid prototyping - immediate mode makes state management simple. Main limitation: TextEdit isn't designed for code editors (no multi-cursor, can't hide folded text). v0.3.0 will replace it with a custom widget. The default styling does scream "egui" - spent time on custom theming to avoid that

Native code and speed will be a differentiator.

If the value of JavaScript programming goes down, Rust programming will probably hold value a little bit longer.

How would this have worked outside of catering to browsers?

You can render React all over the place now!