LLM analysis of this: --- IETF Status: The draft (draft-ietf-wpack-bundled-responses) expired in 2021 and isn't being actively pushed through IETF standardization. WICG Status: Still active. - webpackage repo: 1,083 commits, 1.2k stars - substantial ongoing work - Subresource Loading with Web Bundles: Updated July 2024 - Isolated Web Apps: Separate WICG repo, uses signed web bundles (.swbn), actively developed Bottom line: The format isn't dead - it's in WICG incubation rather than IETF standardization. The spec work continues, tooling exists (wbn CLI, Go/JS implementations in the repo), and the format is well-defined. What Chrome did was deprioritize native browser support for loading .wbn files directly. But: - You can still create and serve web bundles - Tooling can read/write them - The format is stable and documented - Isolated Web Apps (which need offline + security) still use them For NIP-82 purposes: The application/webbundle MIME type is valid. A client can download a .wbn, verify its hash via the Nostr event, and serve it through a WebView - no browser-native support needed.