yencabulator

It's standard practice to not let mutually-untrusting workloads share a CPU core. Spectre etc.

You seem to have forgotten about how FCC threatened to revoke ABC's broadcast license over some humor by Jimmy Kimmel?

https://www.aclu.org/press-releases/aclu-responds-to-trump-a...

One-way hash -> you need to store the result to look up based on it -> likely better off using random identifier, and not worry about hash weakness etc.

> No country can deny entry to their own citizens.

USA effectively does that, though: https://www.theguardian.com/us-news/2026/may/21/us-travel-re...

The weapons militaries use are also manufactured by corporations.

The question to ask is whether there's a hand-off; who operates the corporation operates the final system. It's completely plausible this is meant to be a product that is sold, not a service that is subscribed to.

https://www.iceye.com/newsroom/press-releases/iceye-and-noki... specifically says "give nations ownership and control of the satellites"

That project is just Claude run rampant. Actually attempt to read this:

https://github.com/Latias94/merman/tree/83e3ea74bf4da30089a8...

So are doormen, even if it's not their only task.

They do the latter, it's $0.40 per million queries.

(And since the records are size-limited, per-GB is roughly the same thing.)

"Except for Alias A/AAAA records mapped to AWS services listed below, you incur charges for every DNS query answered by the Route 53 service."

https://aws.amazon.com/route53/pricing/

My anecdata: Amazon makes the first N of your returns easy. They ramp up the difficulty as you continue being a customer.

You can use http://invalid for a URL that should never be valid.

https://en.wikipedia.org/wiki/.invalid

But for a web app, you probably want to use the current location as the base.

  new URL("/blah", window.location)

> Starlink, the commercial product, was always off limits for military operations (the type that require connectivity at 100+ MPH).

Lots of Ukrainian use of satellite communications is where people are hiding in a makeshift bunker. Those don't usually travel at 100+ MPH.

The people who started the fire are not going to be FSB employees, they're useful idiots that got paid for some vandalism who won't even know who hired them. Plausible deniability.

> sharply restricting -if not preventing- freedom to sync the attested credential

They already did that! That was the first round! It is only through community outcry that "Credential Exchange Format (CXF)" came to existence.

https://github.com/keepassxreboot/keepassxc/issues/10407

This one is specifically about 1Password: https://news.ycombinator.com/item?id=37836783

There was a similar thing about what Google did with Android (basically making only the built-in manager viable, for a while), but I can't find a good link.

There's huge areas of Finland that are very much protected (e.g. you can only walk on two trails in the whole preserve). Do an image search for Kevo trail to get an idea.

https://en.wikipedia.org/wiki/Protected_areas_of_Finland

Finland is the second lowest-corruption country in the world.

https://www.transparency.org/en/cpi/2025

The cookie banners are intentionally designed so that they cause maximum moan and groan in the people who care, and the maximum naive allowance in people who don't.

> not doing a strong action that would be discussed at a diplomatic level.

That's exactly what's happening.

https://brusselsmorning.com/von-der-leyen-proposes-european-...

Supreme Court voting 5-4 means it was very close to being "legally sound" the opposite way. Not very sound, then.

Nurnberg style trials are for the humans behind the actions, not for countries.

HR formed a team -- you might say a squad -- to fire them.

Even better, configuring the built-in static analysis to forbid it is a one-liner.

On a typical Linux box, overcommit and eager or confused OOM killer will ruin your day anyway.

For no_std style work where running out of memory is actually a hard limit, you have two choices:

1. disable the global allocator and use APIs that take Allocator, to force yourself to only consume APIs that can return errors from allocation. (The ergonomics aren't always great, and fattening all types with a pointer to Allocator isn't great; might be able to use a zero-sized Allocator, with trickery. Say goodbye to many libraries.)

2. use static analysis and try to avoid ever hitting a code path like Vec::with_capacity that doesn't return a Result. Make sure the tooling also analyses your dependencies. (Tooling for the static analysis is painful. And still, say goodbye to many libraries.)

I do wish there were more conveniences for alloc-can-fail APIs, like the failable version of Vec::push needs both try_reserve and push_within_capacity (nightly only).

Sure, but it's worth acknowledging that that specific wart is being fixed.

https://doc.rust-lang.org/std/alloc/trait.Allocator.html

No, people who don't actually use Rust just like to pretend it's something more than it is, for some performative outrage or something.

Here's the current list of similar (unsoundness-causing) open compiler bugs in Rust:

https://github.com/rust-lang/rust/issues?q=state%3Aopen%20la...

The sandbox is the point.

Meanwhile, in JJ, per-repo config is also stored in ~/.config, to avoid this attack:

https://www.jj-vcs.dev/latest/design/secure-config/

> vm can only connect to an IP if it came from a DNS lookup of an allowed name

That sounds like more than just the named destination is reachable, if an allowed name uses that same cloud load balancer/CDN.

Meanwhile, I watched a very prominent Microsoft consultancy shop install a client's ActiveDirectory as <nameoforganization>.ad. You know, the country of Andorra? That has an actual real ccTLD?

They should finally set aside .home and .corp as reserved domains. They're already considered not a valid gTLD:

https://en.wikipedia.org/wiki/.home

https://icannwiki.org/Name_Collision

Can we somehow, as a society, eject all lawyers?

> AGB Q118. What is the meaning/definition of the applied-for gTLD string?

> Lan commonly refers to a broadly recognized term used across a wide range of contexts.

> 1. Describe the mission and purpose of the applied-for gTLD, including the intended registrants and users, and the related activities that have been or will be carried out to achieve this purpose.

> The mission of .LAN is to provide a namespace associated with the applied-for string.