jiveturkey

> That notice is meant to provide a chance to challenge the request.

That's the author's interpretation. The promise doesn't indicate anything of the sort (as of this writing). And users cannot challenge these requests -- users don't own the data (in the US). The promise is very clear that Google will provide the data, if the request is compliant.

Now the text of the notification was past tense, that the information was provided, whereas the promise is crystal clear that Google will notify before providing the info, but to me that could amount to a simplification of "we have verified that the request is legally compliant and will be providing the info to them in 250 ms".

Don't get me wrong, I'm not on Google's side. I'm a huge privacy nut. But the fix is to not give your info to Google, not trust that they will abide by any policy. Especially in a case like this where your freedom is at risk. Most people are completely unaware and unthinking but this guy seems that he was fully aware and placed his trust in Google.

Right, a PR is "just" a set of commits (all must be in the same branch) that are intended to land atomically.

Stacked PRs are not breaking up a set of commits into divisible units. Like you said, you can already do that yourself. They let you continue to work off of a PR as your new base. This lets you continue to iterate asynchronously to a review of the earlier PRs, and build on top of them.

You often, very often, need to stage your work into reviewer-consumable units. Those units are the stack.

You "just" need to know the original merge-base of PR B to fix this. github support is not really required for that. To me that's the least valuable part of support for stacked PRs since that is already doable yourself.

The github UI may change the target to main but your local working branch doesn't, and that's where you `rebase --onto` to fix it, before push to origin.

It's appropriate for github to automatically change the target branch, because you want the diff in the ui to be representative. IIRC gitlab does a much better job of this but this is already achievable.

What is actually useful with natively supported stacks is if you can land the entire stack together and only do 1 CI/actions run. I didn't read the announcement to see if it does that. You typically can't do that even if you merge PR B,C,D first because each merge would normally trigger CI.

EDIT: i see from another comment (apparently from a github person) that the feature does in fact let you land the entire stack and only needs 1 CI run. wunderbar!

> MySQL, arguably the world's most popular database management system,

eBPF runs in an extremely constrained environment, in order to protect the kernel. indeed, it's quite high performance. but not high flexibility.

a blog about traceroute in 2026. imagine that. hard to believe it could possibly be of any interest at all, especially written by someone that only just discovered it. but i'm oh so glad i stopped in, to learn about trippy! it looks amazing.

2002 - Estimating Router ICMP Generation Delays[0]

2015 - Characterizing ICMP Rate Limitation on Routers[1]

[0] https://pages.cs.wisc.edu/~suman/courses/640/papers/govindan...

[1] https://inria.hal.science/hal-01111190/document

I guess you haven't actually implemented anything in eBPF.

They sell aggregated information.

surely, the security protocols and radio modulation techniques of the day did not consider a modern-day internet threat landscape. i'm a bit surprised no one has sent their own command signals to Voyager. i'm guessing massive transmit power must be required.

TFA doesn't say -- does anyone know if this applies to 5k and 6k monitors? On my 5k display on a M4 Max, I see the default resolution in system settings is 2560x1440. Which is what I'd expect.

If the theory about framebuffer pre-allocation strategy is to hold any water, I would think that 5k and 6k devices would suffer too, maybe even more. Given that you can attach 2x 5k monitors, the pre-allocation strategy as described would need to account for that.

Not in the Apple world, and this article is centered on Apple.

https://bjango.com/articles/macexternaldisplays/

  - 24" you need 4k
  - 27" you need 5K.
  - 32" you need 6k.

Windows subpixel aliasing (Clear Type) manages a lot better with lower pixel density. Since Windows still has a commanding market share in enterprise, you might be right about the industry standard for HiDPI but for Apple-specific usage, not really.

> It costs me zero paper. It costs me zero toner.

> For the recipient, a fax is a physical reality. It requires paper. It requires ink. It requires time.

Interesting misconception in 2026.

Of course if you read on, it's clear the story is embellished.

I sure hope they created a restore point first.

no, but many apps can independently use a different Apple (nee iCloud) Account specifically for that app.

that said, you can create multiple users per macOS device, and each can have a different Apple Account. that's a nightmare, because some significant areas of device management assume a single Apple Account. So for example you can use a 2nd account to get around Activation Lock in some cases.

you wouldn't. a business without an IT department would choose this.

you only need to do the domain lock part if you plan to use MAIDs. For 20 people you probably didn't need to do that, at least not at the same time as the rest. You can do it as a later step, not the first step.

I'd find this more compelling if you looked at a few thousand Vanta or Drata reports grouped by auditor. You're going to find the same commonalities with only trivial language differences.

SOC2 reports are private between you and the auditor (that way if you "fail" you can just find another auditor or have a re-do, and no one is the wiser), and basically always gated behind a sales touchpoint (another hint about what utility they provide). I guess the Delve ones leaked which is why they can all be compared.

220 out of 494 "no exceptions" seems quite high to me. Nobody I've ever dealt with allows an exception to make its way into the report.

i don't think you can really descend below zero?

it does highlight the efficiency value of boilerplate. you only have to proof it once, really well of course. all downstream instances get the benefit of that one very good review.

boilerplate is one word. sorry for the nit, feel free to backpfeifengesicht

> I have always envisioned a ai server being part of a family's major purchases

and an oxide rack

Chuck Norris doesn't die. He prepares himself for the next battle, with Jeff Dean.

> Anytime someone refers to a sector as a "space" (as in "I'm really getting into the AI space") it's like they're making me chew tinfoil.Anytime someone refers to a sector as a "space" (as in "I'm really getting into the AI space") it's like they're making me chew tinfoil.

oh come on.

jargon is incredibly useful. here on HN we know that very well. clanker, agent, +1, LGTM, these are extremely convenient jargon we use daily. and here, he's complaining about 'space' not 'AI'. AI is itself jargon. There's nothing "artificial" about it (just non-organic), and nothing "intelligent" either.

'enshittification' is jargon.

> I steer clear of jargon used by firms to lionize themselves, like "hyperscaler."

it's just descriptive (usefully so), not self-congratulatory.

and what's wrong with "thought leader"? it's a pejorative, not acclaim. even more so when the user takes themselves seriously.

he does go on to get to the point about "bullshit", and i would agree completely with the title, that there is a correlation. why lament and complain about it? i absolutely adored adobe flash -- ad blocking was oh so easy in those days. i would actually narrow the problem from "bullshit" to "doublespeak". i think that is where the real problem lies. bullshit is just bullshit, it's fine.

> It is the top EV market.

per-capita or by total volume? i ask because a sibling or child comment says that the number of cars sold in norway is pretty small (in part because the population is small). a quick google says 180k cars sold in norway in 2025 (we can round up to 100% EV) and 34M sold in China. It also says China has 50% EV sales. So by total volume Norway isn't close to the top.

ratio'd

That's not a counter-argument. You are protecting the physical access, and your threat model doesn't include someone willing to bypass your locks and sensors. (or it does and you just didn't go into those details.)

The argument was that physical access gives up the FDE key.

https://entire.io thinks so

How about Entire?

https://techcrunch.com/2026/02/10/former-github-ceo-raises-r...

https://news.ycombinator.com/item?id=46961345

why doesn't HN rewrite this to the canonical x.com hostname?