phillipseamore

"The Seaglider is designed to handle ocean swells up to a meter and a half high" - that severely limits where it can be used or during which seasons.

"Ice eye" - it started as project to see if SAR could be used to monitor ice features in the artic

Stupid me thinking they only spent time on brute force-able problems with pure compute, not sure there's much intelligence here. What could a mathematician do with $20M worth of compute to try to brute force one single problem?

I just took an old PHP site I used to run (no framework or libraries) and had codex transpile it to rust. Ran it behind identical nginx config, just switching out php-fpm's socket for the rust/tokio one. Rust was way worse, so I let codex time the performance resulting in it opting for micro-caching everything and then we got about comparable rps and latency - but those improvements would all help in PHP as well.

"During the exercise, this traffic will securely reroute over the public internet."

So disconnecting the private backbone and moving traffic over the internet instead does what exactly for sovereignty?

No, I'm proposing that TLD can handle issuance themselves since they technically have 100% control over domains under their TLDs anyways. I think this might be important when we look at a combination of short (and getting shorter) lifetimes for end-user certificates and increasing volatility of the world (cyberattacks, sabotage and war). It would be desirable for ccTLD's specifically to be able to maintain certificate issuance even though the country was virtually or physically isolated from the rest of the world. (Which DANTE could/would have mitigated but is not my proposal here)

Would like to see them working more with TLD operators here, I'd like to see a CA partner with TLD ops to offer distributed and resilient issuance (especially with shorter cert lifetimes) with intermediate certificates locked to their TLDs, TLD operators are already a significant part of the chain of trust since it's all based on DNS today.

Not a huge difference between buying the root cert itself and getting a cross-sign. LE started out with cross-signs from Identrust.

"On October 19, 2015, the intermediate certificates became cross-signed by IdenTrust, causing all certificates issued by Let's Encrypt to be trusted by all major browsers."

Certainly, these aren't new standards and have been available on Android. We like to offer a split page when a foldable is used in a book pose and avoid having anything (especially interactive elements) in the middle.

Looks like Safari 27.1 on Duo ships without support for CSS viewport segments and any other CSS or JS to handle foldables.