News for hackers. Stuff that matters.

fastest963

Re:Better HTTP/1 connection reuse in Go 1.27 on Thursday October 15, 2026 @12:11AM (#50099046)
Yes, because HTTP/2 in Go is significantly slower: https://github.com/golang/go/issues/47840
Re:AI handles incidents, engineers lose touch with their systems on Saturday September 05, 2026 @11:27PM (#49583046)
How often are there outages? Is there a significant outage every week to do simulations for? The problem with our organization is that outages are so rare that weekly we have nothing to discuss.

Tell HN: Both recent GCP outages caused by fiber optic maintenance

Both of GCP's recent outages were caused by "fiber optic maintenance". On August 20th when us-west1 went down they said [1]:> The disruption originated during scheduled fiber optic maintenance, which unexpectedly compromised network capacity between data centers within the us-west1 region.Then on September 1st when us-central1-b (and collateral affects in other zones) went down they said...

( Read More... | 1 comment | 4 points | on HN )
Re:Google Cloud us-west1 down on Thursday August 20, 2026 @12:29PM (#49376862)
It's now been updated to 13 products and still nothing on the public status page.
Re:Opaque, Interoperable Passkey Records (and a Go API) on Monday July 20, 2026 @11:44PM (#48987780)
The user still needs to provide proof that they own the passkey in order to login. It's not like someone could hack the website, steal the "string" and use it to login.
Rezoning land is extremely difficult and likely requires changes to the Master plan for the city/county. If a citizen is unhappy with a zone nearby do not move there.

If an area is zoned for industrial and someone wants to build a datacenter there without variances I don't see why anyone should be able to say no. Same thing for building condos or single-family homes in areas zoned for those. There's almost always variances though which is why there is even an opportunity to say no.

> The project is expected to generate approximately $310 million in property taxes over 30 years, in addition to utility taxes.

https://www.joliet.gov/Home/Components/News/News/5666/41

This is what zoning is for. If you live near land zoned for industrial or commercial then you can't fight it when someone wants to develop the land. If you don't want to live near something like that you shouldn't have bought/rented next to that zone.
Depends. Is the alternative a loud, obnoxious factory? Or a warehouse with a constant stream of trucks? If you live near land zoned for industrial buildings then something is going to go there eventually.
Datacenters bring millions in tax revenue (I oppose giving them tax breaks, that's a politician issue not an issue inherent to DCs) and are much less of a nuance than factories or warehouses. The increased cost of electricity is a concern but can be helped by an upfront investment, a bond for future grid maintenance, or separate utility infrastructure.

Are the datacenter concerns actually AI fears and they somehow think that stifling datacenter construction will save their jobs from AI? I understand the fear but if there's money to be made, datacenters will get built somewhere, and another municipality will reap the benefits.

Coinbase confirmed on X that the exchange only ran in one AZ for latency reasons: https://x.com/i/status/2052855725857329254
Coinbase claimed multiple AZs were down but the AWS statement was that only a single AZ was affected. Does anyone have more details?
Re:Unbounded connection churn issue in gRPC-go on Friday May 08, 2026 @11:23AM (#48064484)
For the last 3 months I've been trying to get support from Google/gRPC/GCS teams to fix an issue with gRPC which results in thousands of connections and constant connection churn. The underlying issue appears to be a constant backend priority rotation with the endpoints for the client to connect to. The gRPC team seems unwilling to address why the gRPC client is opening several hundred connections when I'm not even using the client.

I was told to open a GCP support ticket and after many messages back and forth the ticket was closed because the discussion would continue on GitHub only for the issue to be closed a few weeks later.

I'm not the only one experiencing this issue either as a related issue was just posted in the google-cloud-go repo: https://github.com/googleapis/google-cloud-go/issues/14538.

Re:GitHub RCE Vulnerability: CVE-2026-3854 Breakdown on Wednesday April 29, 2026 @12:31AM (#47944185)
Yeah, but this still gives any employee RCE on the GHES server right?
Re:Ask HN: What Are You Working On? (March 2026) on Sunday March 08, 2026 @09:11PM (#47303617)
RateRudder: https://raterudder.com

I've been working on a solution to automate solar+battery use to arbitrage the market. I'm on a real-time utility plan but even if you're on TOU it can save you $1+ per day by strategically planning when to use the battery and when to conserve or charge the battery. So far it's limited to a few providers and only FranklinWH batteries but I'm eagerly looking for someone to help me get Powerwall support working and other ESS. It's open-source on GitHub as well.

Re:More Mac malware from Google search on Monday February 09, 2026 @02:47AM (#46942661)
On Mac binaries need to be signed and notarized and Apple could stop the spread of the malware once it's identified or even detect it before notarizing it.
Re:Join the on-call roster, it'll change your life on Tuesday December 09, 2025 @10:32PM (#46213705)
I wouldn't say it's without pay. It's in the job description when you're hired and the pay should compensate for that. SREs are typically paid very well.
Re:Go Proposal: Secret Mode on Tuesday December 09, 2025 @10:29PM (#46213686)
I'm not sure there's a realistic alternative. If you need to generate a key then it has to happen somehow on unsupported platforms. You can check Enabled() if you need to know and intend to do something different but I assume most of the time you run the same function either way you'd just prefer to opt into secret mode if it's available.
Re:How/why to sweep async tasks under a Postgres table on Thursday November 27, 2025 @03:23PM (#46072936)
It can be more complicated depending on your environment but I'd prefer instead to use a Pub/Sub pattern instead. You can have a generic topic if you want to model it like the generic table but it handles retries, metrics, scaling, long-running, etc all for you. If you are running in the cloud then Pub/Sub is something you don't need to maintain and will scale better than this solution. You also won't need to VACUUM the Pub/Sub solution ;)

Older ยป