> In APIs, passively safe means failures (crashes, timeouts, retries, partial outages) can't produce duplicate work, surprise side effects, or unrecoverable state.

I thought that was what 'idempotent' meant.

It's mostly semantics. Passive safety is the "why" while idempotency is the "how".

Please don't credit Niklas Luhmann for what Sönke Ahrens did: https://www.soenkeahrens.de/en/takesmartnotes

Subdomain version: https://zarasurfs.substack.com/p/weve-optimised-ourselves-in...

The instructions that you give in the prompt are advisory.

You must use a security system to ensure that the access is actually limited.

The error in the original article has been corrected.

https://developer.nvidia.com/blog/nvidia-800-v-hvdc-architec...

Correction: $22, $23, and $26 per TB respectfully.

Subdomain version: https://cocakoala.substack.com/p/ai-consciousness-a-biologic...

Pricing per byte doesn't work as it undervalues or overvalues items.

To get more money out of this system people will make their items larger. For example a movie or track might only be available in its high resolution uncompressed form because that form is the one that has the highest total price.

> Pay 0.001 USDC per 1MB of a movie

A DVD contains about 5700MB at that rate it would be 5.7 USD. No publisher is going to post a DVD size version when they can get 307.2 USD for the 300GB Blu-ray upscale.

The "Full internal write-up" is in French.

Reminds me of _A Vision of Universal Functionality for Tomorrow's User Interfaces_ https://garyperlman.com/papers/ozchi.html