The site looks nice, which fools us into thinking thought and effort was put into this.

I think that for this sort of _interactive_ application, there's no avoiding the need to manage scroll/history.

Sure, it may be _possible_ the account is acting "autonomously" -- as directed by some clever human. And having a discussion about the possibility is interesting. But the obvious alternative explanation is that a human was involved in every step of what this account did, with many plausible motives.

Curl-bash without hash-checking from a four-month-old domain with full k8s cluster access? All the identities connected are brand new, including the brand-new HN account that posted this. There are four commits in the repo, and three are back-dated to exactly 1 year ago.

But this "semi-monopolistic trade union" not only inflates their wages (which maybe that's a good thing), but it also harms the lives of the population they purport to serve. Many (most imo) people in the US simply cannot afford the monopoly's prices, and the monopoly has little incentive to innovate. This cartel of doctors actively prevents lower-cost, more efficient alternatives from coming to market.

Presidential pardons do not limit or prevent private civil lawsuits.

I suggest in general using function scoping to drive the lifetime of contexts, etc. This works also for defers and tracing spans in addition to the canonically shadowed `ctx` variable.

There is an old issue in the tracker proposing changes to alleviate this: https://github.com/golang/go/issues/34510. The original author (bcmills) of the errgroup package shared insight into the design choices/tradeoffs he made.

They _are_ smart people. There's more to the differences in perspective than "lib smart, maga stupid".

Have you tested whether you can receive email directed to firstlast@gmail.com? Perhaps theirs is really firstlastt@gmail.com and all their contacts "correct" it.