2 ms·

What you are describing are essentially an extended version of various security http headers. * first requirement can already be done using Content-Security-Po

• Timon3 2y ago
  That's partially true, but it would be important for this to both work without a server, and at runtime. Not relying on a server makes this functionality available for downloaded sites. I'm a big fan of offering single file builds for web utilities, and the pledge should be part of that build instead of something the user supplies. Having this as a runtime API would enable easier integration - say I'm developing a video editor that needs some WASM blobs. It might be a lot easier to load the blobs and pledge no further network access than having the URLs known on the server-side.