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.
franzap
npub1wf…3dgh9
2026-01-30 14:35:11 UTC
in reply to nevent1q…9nc0
Author Public Key
npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9Seen on
wss://nostr.landPublished at
2026-01-30 14:35:11 UTCEvent JSON
{
"id": "69ab0208d7b842bb0748fad491a582d416ca271fb03716133f6575326376b43c",
"pubkey": "726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11",
"created_at": 1769783711,
"kind": 1,
"tags": [
[
"e",
"638a3651256f17b3f9138771de66b8d193b2c5a5658ae2ec4b93b3586dbdc32f",
"wss://relay.damus.io/",
"root",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11"
],
[
"e",
"ac6f2844a7623d116bed9f31f37cff1ade9ace3326c7fb3410fb8ae0bd3d624e",
"wss://nos.lol/",
"reply",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11"
],
[
"p",
"78ce6faa72264387284e647ba6938995735ec8c7d5c5a65737e55130f026307d"
],
[
"p",
"7579076d9aff0a4cfdefa7e2045f2486c7e5d8bc63bfc6b45397233e1bbfcb19"
]
],
"content": "LLM analysis of this:\n\n---\n\nIETF Status: The draft (draft-ietf-wpack-bundled-responses) expired in 2021 and isn't being actively pushed through IETF standardization.\n\nWICG Status: Still active.\n - webpackage repo: 1,083 commits, 1.2k stars - substantial ongoing work\n - Subresource Loading with Web Bundles: Updated July 2024\n - Isolated Web Apps: Separate WICG repo, uses signed web bundles (.swbn), actively developed\n\nBottom line:\nThe 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.\nWhat Chrome did was deprioritize native browser support for loading .wbn files directly. But:\n - You can still create and serve web bundles\n - Tooling can read/write them\n - The format is stable and documented\n - Isolated Web Apps (which need offline + security) still use them\n\nFor 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.",
"sig": "79d1702e45975ebab2431f5e308b675400aa4bf0ed1a5e0791f78519a3bc32f3475157ee23949d8d5acaaafe826f54508a258635e67afd49b87e2d0ed6f0666c"
}