When I opened the link, I just laughed for 5 mins straight
Days since last GitHub incident
121–130 of 142 posts
Re: Days since last GitHub incident
#122Earlier quoted context omitted.
The DGX Spark is not good for inference though it's very bandwidth limited - around the same as a lower end MacBook Pro. You're much better off with a Apple silicon for performance and memory size at the moment but I'd recommend holding off until the M5 Max comes out early in the early as the M5 has vastly superior performance to any other Apple silicon chip thanks to its matmul instruction set.
Oof, I was already considering an upgrade from the M1 but was hoping I couldn't be convinced to go for the top of the line. Is the performance jump from the M# -> M# Max chips that substantial?
> Is the performance jump from the M# -> M# Max chips that substantial
From m1? Yes, absolutely. M3 is marginal now but m5 will probably make it definite.
Re: Days since last GitHub incident
#123It should always be at 0, because GitHub is unreachable over IPv6, which in 2025 should be considered an incident.
mobile adoption is high, desktop (residential and corporate) is still quite low. I'm a big advocate for github to add ipv6 support , but let's not pretend it's critical for their business.
Aren't there serveral hosts now where IPv6 access is included but you have to pay for each attached IPv4? E.g. AWS and Hetzner
Re: Days since last GitHub incident
#124Earlier quoted context omitted.
mobile adoption is high, desktop (residential and corporate) is still quite low. I'm a big advocate for github to add ipv6 support , but let's not pretend it's critical for their business.
Aren't there serveral hosts now where IPv6 access is included but you have to pay for each attached IPv4? E.g. AWS and Hetzner
Yep
Re: Days since last GitHub incident
#125Earlier quoted context omitted.
mobile adoption is high, desktop (residential and corporate) is still quite low. I'm a big advocate for github to add ipv6 support , but let's not pretend it's critical for their business.
just a few hours ago we found a pretty nice residential desktop use case for proper v6 (with prefix delegation), due to no need for NAT the old router (2013) became less of a bottleneck!
Double check (I mean by remote port scan) that your firewall is working. I’ve seen routers with no IPv6 firewall . And it actually matters
Re: Days since last GitHub incident
#126Earlier quoted context omitted.
The DGX Spark is not good for inference though it's very bandwidth limited - around the same as a lower end MacBook Pro. You're much better off with a Apple silicon for performance and memory size at the moment but I'd recommend holding off until the M5 Max comes out early in the early as the M5 has vastly superior performance to any other Apple silicon chip thanks to its matmul instruction set.
Oof, I was already considering an upgrade from the M1 but was hoping I couldn't be convinced to go for the top of the line. Is the performance jump from the M# -> M# Max chips that substantial?
The main jump is from anything to M5; not because it's simply the latest but because it has matmul instructions similar to a CUDA GPU which fixes the slow prompt processing on all previous generation Apple Silicon chips.
Re: Days since last GitHub incident
#127Earlier quoted context omitted.
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.
I mostly agree, but a generalized attack at the remaining GitHub workers by calling them "losers" and then "rookies" is unwarranted and leaves a bad taste IMO. 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 cul…
A structural engineer will not sign off on bad designs no matter how much pressure the company applies to them. They will resign and/or report the incident to their local regulator as a safety issue.
We don't have that for developers. Maybe shame/offense is our next best bet. You are free to work for a terrible company accepting and/or encouraging terrible design decisions, but you need to take into account the potential of being laughed at for said decisions.
Re: Days since last GitHub incident
#128GitHub Actions is a good example of systems thrown together that at face value have something to offer until they get put under stress. Just now I found: * a job that's > 1 month old, still running * another job that started 2 hours ago that had 0 output * a job that was marked as pending, yet I could rerun it * auto-merges that don't happen * pull requests show (1), click it, no pull requests visible Makes me wonder…
That's just post-Windows 8 Microsoft quality for you. Every product has been like that - looks "ok" on the outside (in reality it looks shit, but at least that's intentional), but the second you dig deeper and start using it you get all kinds of paper cuts like that.
Re: Days since last GitHub incident
#129Re: Days since last GitHub incident
#130Earlier quoted context omitted.
Friendly reminder to stop saying friendly reminder when what you're saying isn't a reminder.
For any ESL folks here - "Friendly reminder" is typically used for reminding people of common knowledge. Especially for beneficial but inconvenient things that some or most people neglect to do, either because they're annoying, inconvenient, or time consuming. Things for which busy people might need a "wink wink, nudge nudge". Friendly reminder to floss. Friendly reminder to have your cancer screening. Friendly remin…
[flagged]