Earlier quoted context omitted.
This should have been fixed here: https://github.blog/changelog/2025-12-04-notifications-trigg... Are you still seeing it, would you mind checking? Our team will get on it if so.
I had the same. The dot is cleared on the mobile site. It is present on the desktop site.
Days since last GitHub incident
101–110 of 142 posts
Re: Days since last GitHub incident
#102I found out when Actions started failing again for the Nth time this month. The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.
Re: Days since last GitHub incident
#103I found out when Actions started failing again for the Nth time this month. The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.
GitHub has seem to come under the same management as VSCode, everything has to be made AI and that is the only priority. It's like the Google+ of old but stupider.
Re: Days since last GitHub incident
#104Re: Days since last GitHub incident
#105Earlier quoted context omitted.
I had the same. The dot is cleared on the mobile site. It is present on the desktop site.
Somewhat similar situation here. Cleared cache and logged back in on mobile, dot was fixed. Haven't tested on my laptop yet.
Re: Days since last GitHub incident
#106Re: Days since last GitHub incident
#107Once GitHub fully migrates to Azure, it should be known as GitHub 11.
Re: Days since last GitHub incident
#108This is why I keep encouraging folks to a) have a mirror & b) make sure their tools automatically pick up the mirrors. I recently got mirror support upstreamed into Nixpkgs for fetchdarcs & fetchpijul which actually work on my just-alpha-released pinning tool, Nixtamal https://darcs.toastal.in.th/nixtamal/trunk/README.rst >, for just this sort of thing.
That's great for the repository, but what about if you're using ghcr, actions, issues, or copilot?
Re: Days since last GitHub incident
#109I found out when Actions started failing again for the Nth time this month. The internal conversation about moving away from Actions or possibly GitHub has been triggered. I didn't like Zig's post about leaving GitHub because it felt immature, but they weren't wrong. It's decaying.
If you consider that an American maintainer was cheesed off enough to move an entire project off GitHub two days before Thanksgiving then the tone of the original post was completely in line with the energy involved. Anger is a communication tool. It should absolutely be used when boundaries are being violated. Otherwise you’ll get walked all over.
See the edit history here: https://news.ycombinator.com/item?id=46133179
Edit: 1. just to be clear, it's very good that they have accepted the feedback and removed that part, but there's no apology (as far as I know) and it still makes you wonder about the culture. On the other side, people make mistakes under stress. 2. /s/not warranted/unwarranted/
Re: Days since last GitHub incident
#110Earlier quoted context omitted.
An NVIDIA DGX Spark is $4000, pair that with a relatively cheap second box to run GitLab in the corner and you would have pretty good local AI inference setup. (you'd probably have to write a nontrivial amount of software to get your setup where you want) The local models are just right on the edge of being really useful, there's a tipping point to where accuracy is high enough so that getting things done is easy vs…
I can't say I'm not tempted looking at the Spark, I could probably save some cash on heating my house with that thing. Though yeah unless there's some good software already built around a similar LLM workflow I could use it'd probably be wasted on me, or spend its time desperately trying to pay for itself with crypto mining. Adding Claude to my rotation is starting to look like the option with the least amount of bui…
A big part of my success using LLMs to build software is building the tools to use LLMs and the LLMs making that tool building easy (and possible).