Repository navigation
Expand file tree
/
Copy pathindex.html
More file actions
512 lines (480 loc) · 45.2 KB
/
Copy pathindex.html
File metadata and controls
512 lines (480 loc) · 45.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta
http-equiv="Content-Security-Policy"
content="default-src 'none'; base-uri 'none'; object-src 'none'; form-action 'none'; font-src 'none'; frame-src 'none'; manifest-src 'none'; media-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data: blob:; connect-src 'self' https: wss: http://localhost:* ws://localhost:* http://127.0.0.1:* ws://127.0.0.1:* http://*.onion ws://*.onion; worker-src 'self' blob:; trusted-types 'none'; require-trusted-types-for 'script'"
/>
<meta name="referrer" content="no-referrer" />
<meta
name="description"
content="Encrypt files in your browser. Keep copies or recoverable parts on storage nodes you choose, with replication, sharding and owner-controlled repair."
/>
<meta name="theme-color" content="#f4f3eb" />
<meta property="og:title" content="Wildbloom · Files that outlive their host" />
<meta
property="og:description"
content="Encrypt your files, keep complete replicas or recover from a threshold of shards, and repair storage on nodes you choose."
/>
<meta property="og:type" content="website" />
<meta property="og:url" content="https://wildbloom.forgesworn.dev/" />
<link rel="canonical" href="https://wildbloom.forgesworn.dev/" />
<link rel="icon" href="data:," />
<title>Wildbloom · Encrypted publishing and storage you control</title>
</head>
<body>
<a class="skip-link" href="#client">Skip to the client</a>
<main class="shell">
<nav class="site-nav" aria-label="Primary navigation">
<a class="wordmark" href="#top" aria-label="Wildbloom home"><svg viewBox="0 0 28 28" aria-hidden="true"><path d="M14 24V12M14 17C3 18 3 7 3 7s11-1 11 10ZM14 12C14 2 25 3 25 3s1 10-11 9Z" /></svg>Wildbloom<span class="preview-label">Preview</span></a>
<div class="nav-links"><a href="#what">Why Wildbloom</a><a href="#storage">How it works</a><a href="#install">Get started</a></div>
<a class="nav-client" href="#client">Open the client <span aria-hidden="true">↗</span></a>
</nav>
<div id="overview">
<header id="top" class="landing-hero">
<div class="hero-main">
<p class="eyebrow"><span class="preview-dot" aria-hidden="true"></span> Open source. Yours to grow.</p>
<h1>Your files.<br />More than one<br /><em>way home.</em></h1>
<p class="hero-copy">Encrypt in your browser. Keep copies on nodes you trust, or split a file into recoverable parts. Stay in control when a host goes offline.</p>
<div class="hero-actions">
<a class="button-link" href="#client">Open the client <span aria-hidden="true">↗</span></a>
<a class="hero-secondary" href="#film">Watch the 32-second story <span aria-hidden="true">↓</span></a>
</div>
<p class="hero-note">Public preview · Bring your own storage and signer</p>
</div>
<div class="bloom-art" role="img" aria-label="An encrypted file connected to four separate storage nodes, with multiple paths back to the file.">
<svg viewBox="0 0 460 460" aria-hidden="true">
<defs><pattern id="bloom-grid" width="24" height="24" patternUnits="userSpaceOnUse"><circle cx="1" cy="1" r="1" /></pattern></defs>
<circle class="bloom-field" cx="230" cy="230" r="224" />
<circle class="bloom-orbit" cx="230" cy="230" r="172" />
<circle class="bloom-orbit inner" cx="230" cy="230" r="108" />
<path class="bloom-stem" d="M230 230Q110 230 110 110M230 230Q350 230 350 110M230 230Q110 230 110 350M230 230Q350 230 350 350" />
<path class="bloom-leaf" d="M230 230C122 233 116 144 143 143C233 116 233 122 230 230Z" />
<path class="bloom-leaf light" d="M230 230C227 122 316 116 317 143C344 233 338 233 230 230Z" />
<path class="bloom-leaf light" d="M230 230C233 338 144 344 143 317C116 227 122 227 230 230Z" />
<path class="bloom-leaf" d="M230 230C338 227 344 316 317 317C227 344 227 338 230 230Z" />
<g class="bloom-node"><rect x="84" y="84" width="52" height="52" rx="18" /><text x="110" y="116">01</text></g>
<g class="bloom-node"><rect x="324" y="84" width="52" height="52" rx="18" /><text x="350" y="116">02</text></g>
<g class="bloom-node"><rect x="84" y="324" width="52" height="52" rx="18" /><text x="110" y="356">03</text></g>
<g class="bloom-node"><rect x="324" y="324" width="52" height="52" rx="18" /><text x="350" y="356">04</text></g>
<circle class="bloom-core" cx="230" cy="230" r="48" />
<g class="bloom-lock"><rect x="213" y="224" width="34" height="26" rx="5" /><path d="M221 224v-9a9 9 0 0 1 18 0v9" /><path d="M230 234v6" /></g>
</svg>
<p><span class="art-line" aria-hidden="true"></span> Encrypted first. Distributed by you.</p>
</div>
</header>
<ul class="principle-strip" aria-label="Wildbloom principles">
<li><span aria-hidden="true">↗</span> Your storage</li>
<li><span aria-hidden="true">⌁</span> Your signer</li>
<li><span aria-hidden="true">✳</span> Open protocols</li>
<li><span aria-hidden="true">○</span> No Wildbloom account</li>
</ul>
<section id="what" class="marketing-section" aria-labelledby="what-heading">
<div class="section-heading"><p class="section-kicker">01 / Take ownership</p><h2 id="what-heading">A file deserves more<br />than a fragile link.</h2><p>A disk fails. A service closes. A link stops working. Wildbloom helps you decide where your files live, who can read them, and how to bring them back.</p></div>
<div class="benefit-grid">
<article><span class="benefit-icon" aria-hidden="true">01 / PRIVATE</span><h3>Encrypt before<br />it leaves.</h3><p>Content, filename and file type are encrypted in your browser by default. Storage nodes receive encrypted bytes. You keep the recovery key.</p></article>
<article><span class="benefit-icon" aria-hidden="true">02 / RESILIENT</span><h3>Give your file<br />another way back.</h3><p>Keep complete copies or recoverable parts on separate nodes. Choose a layout that can survive losing a host.</p></article>
<article><span class="benefit-icon" aria-hidden="true">03 / YOURS</span><h3>Choose the people.<br />Choose the places.</h3><p>Use your own machines or storage from trusted operators. Your signer approves actions; Wildbloom never asks for your private signing key.</p></article>
</div>
</section>
<section id="film" class="marketing-section film-section" aria-labelledby="film-heading">
<div class="film-intro"><p class="section-kicker">A file’s way home</p><h2 id="film-heading">A little room for<br /><em>the unexpected.</em></h2><p>See how encryption and recoverable parts give a file more than one way home.</p></div>
<figure class="film-player">
<video id="recovery-film" playsinline preload="none" width="1280" height="720" poster="/src/assets/film/poster.png" aria-label="A file’s way home: illustrated recovery explainer" aria-describedby="film-caption" tabindex="0"></video>
<figcaption id="film-caption">32 seconds · Silent, with on-screen text · Illustrated 2-of-4 recovery</figcaption>
<button id="play-recovery-film" class="film-play" type="button" aria-controls="recovery-film">Play the story <span aria-hidden="true">▷</span></button>
<p id="film-status" role="status"></p>
</figure>
<details class="film-transcript"><summary>Read the story instead</summary>
<ol>
<li><strong>Your files. More than one way home.</strong> An encrypted file sits among four storage nodes. A little room for the unexpected.</li>
<li><strong>Private before it leaves.</strong> Your browser encrypts the file. Storage nodes receive encrypted bytes. Your key stays with you.</li>
<li><strong>Spread the parts. Keep your options.</strong> Choose nodes you trust. In this illustrated 2-of-4 layout, each of four nodes receives a different part. Any two parts can rebuild the encrypted file.</li>
<li><strong>Two nodes offline. Still a way back.</strong> Nodes 2 and 4 go offline. The parts on nodes 1 and 3 remain available. Recover from those parts with your saved receipt and recovery key, then verify the result.</li>
<li><strong>Keep your key. Keep your way home.</strong> Save the signed recovery receipt. Keep the recovery key separately. Wildbloom is a public preview. Bring your own storage.</li>
</ol>
<p>This film illustrates recovery; it is not a live storage test. Choose independent nodes and keep your receipt and key safe. The example below lets you try the same recovery threshold.</p>
</details>
</section>
<section id="storage" class="marketing-section storage-section" aria-labelledby="storage-heading">
<div class="storage-intro"><p class="section-kicker">02 / Make room for failure</p><h2 id="storage-heading">One node goes away.<br /><em>Your file needn’t.</em></h2><p>Replication keeps complete encrypted copies. Sharding with erasure coding creates parts that can rebuild the file, even when some are missing.</p><p>Try taking nodes offline in this example. Any two of the four parts are enough to recover.</p><a class="text-arrow" href="#install">Build your own storage pool <span aria-hidden="true">↗</span></a></div>
<div class="recovery-demo" aria-labelledby="demo-heading">
<div class="demo-topline"><h3 id="demo-heading">A little room for the unexpected</h3><span>Interactive example</span></div>
<div class="demo-count"><strong>2 <span>of</span> 4</strong><p>parts needed<br />to recover</p></div>
<div class="demo-nodes" role="group" aria-label="Example nodes: pressed means online">
<button type="button" data-demo-node aria-pressed="true"><span class="node-symbol" aria-hidden="true">Ⅰ</span><strong>Node 1</strong><span class="node-state">Online</span></button>
<button type="button" data-demo-node aria-pressed="false"><span class="node-symbol" aria-hidden="true">Ⅱ</span><strong>Node 2</strong><span class="node-state">Offline</span></button>
<button type="button" data-demo-node aria-pressed="true"><span class="node-symbol" aria-hidden="true">Ⅲ</span><strong>Node 3</strong><span class="node-state">Online</span></button>
<button type="button" data-demo-node aria-pressed="false"><span class="node-symbol" aria-hidden="true">Ⅳ</span><strong>Node 4</strong><span class="node-state">Offline</span></button>
</div>
<p class="demo-instruction">Tap a node to take it offline or bring it back.</p>
<p id="demo-result" class="demo-result" role="status"><strong>Your file can come home.</strong><span>2 parts available. Enough to recover.</span></p>
<p class="demo-caption">An illustration, not a live storage check. Recovery also needs your saved receipt and recovery key. Nothing is uploaded or contacted here.</p>
</div>
<div class="layout-options">
<article><p class="section-kicker">Single node</p><h3>A simple start.</h3><p>One encrypted copy. Best when you already keep a separate backup.</p><span>No redundancy</span></article>
<article><p class="section-kicker">Replication</p><h3>More complete copies.</h3><p>Any verified copy can restore the file. Two copies use twice the storage.</p><span>Simple recovery</span></article>
<article><p class="section-kicker">Erasure-coded shards</p><h3>Parts with a plan.</h3><p>Each node receives a part. For example, 4-of-6 uses about 1.5× the encrypted file size.</p><span>Recover from a threshold</span></article>
</div>
<p class="storage-footnote">Choose independent machines and locations: nodes sharing a disk, power supply or connection can fail together. Pool storage is a preview. <a href="https://github.com/forgesworn/wildbloom/blob/main/docs/POOL-STORAGE.md" rel="noreferrer">Understand recovery and its limits ↗</a></p>
</section>
<section id="protocol" class="marketing-section journey-section" aria-labelledby="protocol-heading">
<div class="section-heading"><p class="section-kicker">03 / From file to safe return</p><h2 id="protocol-heading">A few deliberate steps.<br />A clear route back.</h2></div>
<ol class="journey-list">
<li><span>01</span><div><h3>Prepare it locally</h3><p>Choose your file and storage layout. The browser encrypts it. Save your recovery key somewhere safe.</p></div></li>
<li><span>02</span><div><h3>Choose where it lives</h3><p>Approve uploads with your signer. Encrypted bytes go to your chosen Blossom nodes, with hashes checked on read-back for pools.</p></div></li>
<li><span>03</span><div><h3>Keep your route home</h3><p>Save the signed file event or private pool receipt. Keep the recovery key separately. You need both to recover.</p></div></li>
<li><span>04</span><div><h3>Recover. Verify. Repair.</h3><p>Retrieve and decrypt locally. Restore lost redundancy in the browser, or explicitly enable the separate owner repair service.</p></div></li>
</ol>
<div class="protocol-note" id="blossom"><strong>Built on open protocols.</strong><p>Blossom stores the bytes. Nostr carries signed file pointers when you choose to publish them. Pool receipts stay private. Optional WebTorrent offers another delivery path.</p><a href="https://github.com/forgesworn/wildbloom-node/blob/main/docs/PROTOCOL.md" rel="noreferrer">Read the protocol ↗</a></div>
</section>
<section id="services" class="marketing-section" aria-labelledby="services-heading">
<div class="section-heading"><p class="section-kicker">04 / Know your storage</p><h2 id="services-heading">Trust your people.<br />Verify your bytes.</h2><p>Run a node without selling storage, or choose an operator with an offer that suits you. Each connection is your decision.</p></div>
<div class="service-grid">
<article><span class="service-mark" aria-hidden="true">↗</span><h3>Find trusted nodes</h3><p>Discover signed recommendations from people you choose. Review a node before contacting it.</p><a href="#client-services">Find a node <span aria-hidden="true">↗</span></a></article>
<article><span class="service-mark" aria-hidden="true">↔</span><h3>Pay the operator directly</h3><p>Review the allowance, term and refund policy. Supported operators accept Lightning or LNURLcash; Wildbloom holds no customer balance.</p><a href="#client-services">Explore storage offers <span aria-hidden="true">↗</span></a></article>
<article><span class="service-mark" aria-hidden="true">✓</span><h3>Check your file is there</h3><p>A fresh full-read audit verifies current retrievability. It cannot promise continuous custody or future availability.</p><a href="#client-retrieve">Recover and verify <span aria-hidden="true">↗</span></a></article>
</div>
</section>
<section id="install" class="marketing-section start-section" aria-labelledby="install-heading">
<div class="section-heading"><p class="section-kicker">05 / Make it yours</p><h2 id="install-heading">Start in a browser.<br />Put down your own roots.</h2><p>Wildbloom is the browser client. Wildbloom Node is the home for your encrypted bytes. Use them together, or bring an existing Blossom server.</p></div>
<div class="start-grid">
<article class="start-browser"><span class="start-label">01 / USE THE CLIENT</span><h3>No install.<br />No Wildbloom account.</h3><p>Bring a trusted storage node and Nostr signer. Source files up to 256 MiB. This website does not store your files.</p><a class="button-link" href="#client">Open the client <span aria-hidden="true">↗</span></a><a class="start-recover" href="#client-retrieve">Already have a receipt? Recover a file →</a></article>
<article><span class="start-label">02 / RUN A NODE</span><h3>A home for<br />encrypted bytes.</h3><p>A desktop tray app with storage, pool health and owner repair controls. Use your HTTPS setup or optional Tor.</p><a class="download-link" href="https://github.com/forgesworn/wildbloom-node/releases/tag/v0.3.5-preview.1" rel="noreferrer"><span>macOS <small>0.3.5 preview · signed & notarised</small></span><span aria-hidden="true">↗</span></a><a class="download-link" href="https://github.com/forgesworn/wildbloom-node/releases/tag/v0.3.3-preview.1" rel="noreferrer"><span>Windows & Linux <small>0.3.3 preview · Windows unsigned</small></span><span aria-hidden="true">↗</span></a></article>
</div>
<div class="archipelago-banner"><div><p class="section-kicker">Already running Archipelago?</p><h3>Your node. Both apps. One place.</h3><p>Install Wildbloom and Wildbloom Node with your existing node identities.</p></div><a class="button-link secondary" href="https://github.com/forgesworn/archipelago-apps" rel="noreferrer">Get the packages <span aria-hidden="true">↗</span></a></div>
<p class="release-note">Mac 0.3.5 includes optional checkout and storage audits; Windows and Linux downloads are the earlier 0.3.3 preview. Trusted automatic updates remain open. <a href="https://github.com/forgesworn/wildbloom-node#install-and-run" rel="noreferrer">Prefer to build from source? ↗</a></p>
</section>
<section id="questions" class="marketing-section faq-section" aria-labelledby="questions-heading">
<div><p class="section-kicker">A few things to know</p><h2 id="questions-heading">Clear expectations.<br />Better decisions.</h2><p class="faq-intro">A public preview for people who want more control over their files. Keep an independent backup of anything irreplaceable.</p></div>
<div class="faq-list">
<details><summary>Is Wildbloom ready for my only copy?</summary><p>Keep another backup. Encrypted storage, recovery and repair have automated acceptance coverage, and live one-Mac LNURLcash purchase, recovery and paired backup restore have passed. Independent security review, broader physical-device testing, hosted-operator and refund acceptance remain open.</p><a href="https://github.com/forgesworn/wildbloom/blob/main/docs/ACCEPTANCE.md" rel="noreferrer">Read the acceptance evidence ↗</a></details>
<details><summary>Can a storage node read my file?</summary><p>With encryption enabled, nodes receive encrypted content, filename and file type. Your separate recovery key unlocks the file. Connections still reveal metadata such as timing, byte counts and, in direct mode, IP addresses. Optional Tor reduces address exposure; it does not remove every clue.</p><a href="https://github.com/forgesworn/wildbloom/blob/main/docs/PRIVACY.md" rel="noreferrer">Understand the privacy boundary ↗</a></details>
<details><summary>Can I keep the whole file off every node?</summary><p>Choose erasure-coded sharding. Upload and repair send each storage node only its assigned part. Reconstruction happens in your browser or separate owner repair service. Encryption protects the contents; splitting alone does not prevent operators combining parts or fetching other parts if they obtain your receipt.</p></details>
<details><summary>Does repair happen automatically?</summary><p>You can explicitly enable a separate owner repair service in Wildbloom Node. It works on encrypted bytes without the recovery key, but needs enough surviving parts, an external signer and approved storage destinations. Repair authority expires and needs approval again after restarting the app. Free-capacity discovery, draining and cluster-wide rebalancing are not available.</p><a href="https://github.com/forgesworn/wildbloom-node/blob/main/docs/DESKTOP-POOLS.md" rel="noreferrer">Set up owner repair ↗</a></details>
<details><summary>What do I need to recover a file?</summary><p>Your signed file event or private pool receipt, the separate recovery key, and enough available verified bytes or parts. Save the record and key before closing the browser. Extra copies cannot replace a lost recovery key. Ordinary file recovery needs no signer.</p><a href="#client-retrieve">Open file recovery →</a></details>
</div>
</section>
<section class="closing-note" aria-labelledby="closing-heading"><p class="section-kicker">Files that outlive their host.</p><h2 id="closing-heading">Let your files<br /><em>put down roots.</em></h2><a class="button-link" href="#client">Try Wildbloom <span aria-hidden="true">↗</span></a><p>Open source · MIT licensed · Made by ForgeSworn</p></section>
</div>
<div id="client" hidden>
<header class="tool-intro">
<p class="section-kicker">Browser client</p>
<h1 id="client-heading" tabindex="-1">Publish or retrieve a file</h1>
<p class="byo-notice">
<strong>This site stores nothing.</strong> Files go from your browser
to storage you choose. Bring a trusted Blossom server or
<a href="https://github.com/forgesworn/wildbloom-node#install-and-run" rel="noreferrer">run Wildbloom Node</a>.
There are no default servers or relays.
</p>
<p class="boundary">
Files are encrypted locally by default. Signing keys stay in your
browser signer or external signer; never paste a private key here.
Connections and public events still reveal metadata. Each network action needs your go-ahead.
</p>
</header>
<nav class="workspace-nav" aria-label="Client tasks">
<a href="#client-setup"><span>01</span> Set up</a>
<a href="#client-publish"><span>02</span> Publish</a>
<a href="#client-retrieve"><span>03</span> Recover</a>
<a href="#client-services"><span>+</span> Node services</a>
</nav>
<div class="workspace-guide">
<p><strong>Publishing?</strong> Choose your storage, connect a signer, then prepare your file.</p>
<p><strong>Recovering?</strong> <a href="#client-retrieve">Start with your saved event or receipt.</a> Ordinary file recovery needs no signer.</p>
</div>
<section id="client-setup" class="panel" aria-labelledby="connection-heading">
<div class="panel-heading">
<span>01</span>
<div>
<h2 id="connection-heading" tabindex="-1">Choose your infrastructure</h2>
<p>No endorsed defaults. You decide which services learn about the file.</p>
</div>
</div>
<fieldset class="profile-picker">
<legend>Network profile</legend>
<label class="profile-option">
<input name="network-profile" type="radio" value="direct" checked />
<span><strong>Direct encrypted delivery</strong><small>Nostr and Blossom, with optional WebTorrent peers. Services and peers see your IP address.</small></span>
</label>
<label class="profile-option">
<input name="network-profile" type="radio" value="tor" />
<span><strong>Tor-only encrypted delivery</strong><small>Exact v3 onion Nostr and Blossom endpoints only. WebTorrent is disabled.</small></span>
</label>
</fieldset>
<p id="tor-boundary" class="privacy-boundary" hidden>
Use Tor Browser rather than SOCKS-proxying a normal browser. Wildbloom
cannot prove that this browser is using Tor; an ordinary browser lacks
Tor Browser's fingerprint protections and may not provide Web Crypto
on HTTP onion origins. Tor-only mode refuses clearnet endpoints and
disables WebRTC, but a NIP-07 add-on or reused Nostr key can still
fingerprint or identify you.
</p>
<label>
Storage layout
<select id="storage-mode" aria-describedby="storage-layout-summary">
<option value="single">One node: existing Blossom publishing</option>
<option value="replicas">Replicated pool: complete encrypted copies</option>
<option value="erasure">Split pool: recover from a threshold of parts</option>
</select>
</label>
<p id="storage-layout-summary" class="layout-summary" aria-live="polite">One node holds the encrypted file. Keep a separate backup: this layout has no redundancy.</p>
<div id="pool-settings" hidden>
<p class="privacy-boundary">Pool files are always encrypted. Split mode sends each node only one coded part; reconstruction and repair happen in your browser or an explicitly configured owner repair service. Operators may collude or fetch other parts if they learn their addresses. Encryption protects the contents. Keep the signed pool receipt privately alongside a separate recovery key; pool receipts are not published to relays or swarms.</p>
<label>Pool nodes <small>One URL, failure group and optional capacity weight per line. Nodes at the same site should share a group. Weights are relative allocations, not measured free space.</small>
<textarea id="pool-nodes" rows="5" maxlength="8192" placeholder="https://a.example site-a 1 https://b.example site-b 1" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
</label>
<div class="grid three">
<label id="pool-copies-field">Complete copies <input id="pool-copies" type="number" min="2" max="3" value="2" /></label>
<label id="pool-required-field">Parts needed to recover <input id="pool-required" type="number" min="2" max="15" value="2" /></label>
<label id="pool-total-field">Total coded parts <input id="pool-total" type="number" min="3" max="16" value="4" /></label>
</div>
<p id="pool-layout-help" class="hint">Inspect the file to validate placement. Extra failure groups provide spare destinations. A signed receipt describes intended placement; only verified reads count as stored parts. Keep the receipt even if an upload is interrupted.</p>
</div>
<div class="grid three">
<label>
Your Blossom server
<input id="blossom-server" type="url" aria-describedby="blossom-help" placeholder="https://cdn.example.com" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no" />
<small id="blossom-help">Needed to publish. Wildbloom provides none.</small>
</label>
<label>
Nostr relays <small>one per line</small>
<textarea id="relay-urls" rows="3" placeholder="wss://relay.example.com" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
</label>
<label id="tracker-field">
WebTorrent trackers <small>optional, one per line</small>
<textarea id="tracker-urls" rows="3" aria-describedby="tracker-help" placeholder="wss://tracker.example.com" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
<small id="tracker-help">Leave blank to publish and retrieve through Blossom without a torrent.</small>
</label>
</div>
<p id="ice-boundary" class="privacy-boundary">
Peer mode has no hidden public STUN or TURN default. That avoids an
undeclared third party, but peer connections may fail across networks
until an operator-controlled ICE policy is reviewed and configured.
</p>
<label id="tor-consent-field" class="check privacy-confirmation" hidden>
<input id="tor-consent" type="checkbox" />
<span>I have configured this entire browser through Tor. I understand Wildbloom cannot verify that claim.</span>
</label>
<fieldset class="profile-picker signer-picker">
<legend>Signing method</legend>
<label class="profile-option">
<input name="signing-method" type="radio" value="nip07" checked />
<span><strong>NIP-07 browser signer</strong><small>Convenient, but an added Tor Browser extension can alter your fingerprint.</small></span>
</label>
<label class="profile-option">
<input name="signing-method" type="radio" value="external" />
<span><strong>External signer handoff</strong><small>Copy exact unsigned event JSON to a separate signer and return only the signed event.</small></span>
</label>
</fieldset>
<div id="external-signer-identity" class="signer-identity" hidden>
<label>
External signer public key <small>64 lowercase hexadecimal characters. Public identity only, never a private key or nsec.</small>
<input id="external-signer-pubkey" type="text" inputmode="text" maxlength="64" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no" />
</label>
</div>
<div class="actions">
<button id="connect-signer" type="button">Connect NIP-07 signer</button>
<output id="signer-status" class="quiet">Signer not connected</output>
</div>
</section>
<section id="client-services" class="panel" aria-labelledby="node-services-heading">
<div class="panel-heading"><span>+</span><div><h2 id="node-services-heading" tabindex="-1">Find nodes, buy storage and verify storage</h2><p>Each action is separate. Discovery is a recommendation, payment buys an allowance, and a storage check verifies current retrievability.</p></div></div>
<details><summary>Discover recommended nodes</summary>
<label>Trusted public keys <small>One 64-character public key per line. Your chosen relays learn which server lists you request.</small><textarea id="discovery-keys" rows="3" maxlength="1100" autocomplete="off" autocapitalize="off" spellcheck="false"></textarea></label>
<div class="actions"><button id="discover-nodes" type="button">Find nodes on my relays</button></div>
<div id="discovery-results"></div>
<p>Results come from signed Blossom server lists published within 30 days. A recommendation does not prove ownership, capacity or independent failure domains. Nodes are contacted only after you choose an action.</p>
<label class="consent"><input id="list-public-consent" type="checkbox" /><span>I want to replace my public Blossom server list with the selected node. This permanently links its address to my public key.</span></label>
<button id="publish-server-list" type="button">Sign and publish my server list</button>
</details>
<details><summary>Buy storage directly from this node</summary>
<p>Uses the Blossom server selected above. Lightning and LNURLcash are paid directly to its operator. Checkout is currently available in direct mode only; external wallets have their own network behaviour.</p>
<button id="checkout-offers" type="button">Load this node’s offers</button>
<label>Storage plan<select id="checkout-plan" aria-label="Storage plan"></select></label>
<label>Payment method<select id="checkout-rail"><option value="lightning">Lightning</option><option value="lnurlcash">LNURLcash</option></select></label>
<label>LNURLcash issuer<select id="checkout-issuer" aria-label="LNURLcash issuer"></select></label>
<label>Renew allowance (optional)<input id="checkout-renews" maxlength="128" autocomplete="off" spellcheck="false" /></label>
<div id="checkout-offer-details"></div>
<button id="checkout-quote" type="button">Request a private quote</button>
<div id="checkout-quote-details"></div>
<div id="checkout-receipt-links"></div>
<label class="consent"><input id="checkout-consent" type="checkbox" /><span>I reviewed this operator, exact price, storage term, delivery and refund terms, and saved my order reference. Payment does not start an upload.</span></label>
<label>LNURLcash note (only for LNURLcash)<input id="checkout-note" type="password" maxlength="12000" autocomplete="off" autocapitalize="off" spellcheck="false" /></label>
<div class="actions"><button id="checkout-pay" type="button">Create invoice / submit note</button><button id="checkout-check" type="button">Check this payment once</button></div>
<div id="checkout-payment"></div>
<p>After a timeout or cancellation, check the same order. Do not pay a second time. An activated allowance is not proof that a file was uploaded or replicated.</p>
<label>Saved private order reference<textarea id="checkout-reference" rows="3" maxlength="4096" autocomplete="off" autocapitalize="off" spellcheck="false"></textarea></label>
<button id="checkout-recover" type="button">Recover order with its original signer</button>
</details>
<details><summary>Verify storage with a fresh challenge</summary>
<p>First resolve a signed file event or private pool receipt below. This reads every selected encrypted byte and independently downloads it for verification. It needs no decryption key. Large checks use bandwidth. Passing proves current retrievability, not continuous retention or a dedicated physical copy.</p>
<label class="consent"><input id="proof-consent" type="checkbox" /><span>Challenge the resolved file’s node, or each node in its pool receipt, and download every checked file or shard.</span></label>
<button id="storage-audit" type="button">Run full storage audit</button>
<div id="storage-audit-results"></div>
</details>
<div class="actions"><button id="cancel-node-service" type="button">Cancel current service action</button><output id="node-service-status" class="quiet" aria-live="polite">No service contacted</output></div>
</section>
<section id="client-publish" class="panel" aria-labelledby="publish-heading">
<div class="panel-heading">
<span>02</span>
<div>
<h2 id="publish-heading" tabindex="-1">Publish a file</h2>
<p>Inspect your file, save its recovery key, then approve the upload. Keep the signed file event or pool receipt for recovery.</p>
</div>
</div>
<label class="check protection-choice">
<input id="protect-file" type="checkbox" checked />
<span>Encrypt content, filename and MIME type locally before upload (recommended).</span>
</label>
<label class="file-picker">
File
<input id="publish-file" type="file" />
</label>
<div class="actions">
<button id="inspect-file" type="button">Inspect locally</button>
</div>
<dl id="file-facts" class="facts" aria-live="polite"></dl>
<div id="recovery-key-panel" class="key-panel" hidden>
<label>
Recovery key <small>Secret. Send it out of band, never in a public Nostr event.</small>
<input id="recovery-key-output" type="password" inputmode="text" readonly autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no" />
</label>
<button id="toggle-recovery-key" type="button">Reveal recovery key</button>
<div id="recovery-links" class="downloads"></div>
<label class="check">
<input id="key-saved-consent" type="checkbox" />
<span>I have saved the recovery key. Wildbloom cannot recover it.</span>
</label>
</div>
<section id="external-signing-panel" class="key-panel handoff-panel" aria-labelledby="external-signing-heading" hidden>
<h3 id="external-signing-heading">External signing handoff</h3>
<p id="external-signing-purpose"></p>
<p class="privacy-boundary">
The handoff exposes the intended service and metadata, and the returned event adds the public signing identity. Transfer it deliberately. Never paste a private key or recovery key here.
</p>
<label>
Exact unsigned event JSON <small>Read-only. Review it on both devices before signing.</small>
<textarea id="external-unsigned-event" rows="10" readonly autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
</label>
<div id="external-signing-links" class="downloads"></div>
<label>
Complete signed event JSON <small>Wildbloom rejects changed fields, the wrong author, malformed data and invalid signatures.</small>
<textarea id="external-signed-event" rows="10" maxlength="131072" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
</label>
<div class="inline-actions">
<button id="accept-external-signature" type="button">Accept exact signature</button>
<button id="cancel-external-signature" class="secondary" type="button">Cancel external signing</button>
</div>
</section>
<div class="gate">
<label class="check">
<input id="upload-consent" type="checkbox" />
<span id="upload-consent-copy">I understand this sends encrypted bytes and visible transfer metadata to the chosen Blossom server.</span>
</label>
<div class="inline-actions">
<button id="upload-file" type="button" disabled>Upload prepared payload</button>
<button id="cancel-upload" class="secondary" type="button" disabled>Cancel upload</button>
</div>
</div>
<div id="seed-gate" class="gate">
<p>Optional: configure trackers before uploading to make this file available to peers.</p>
<label class="check">
<input id="seed-consent" type="checkbox" />
<span>I understand trackers, peers and WebRTC connection candidates can expose network addresses and torrent activity.</span>
</label>
<div class="inline-actions">
<button id="start-seeding" type="button" disabled>Start peer seeding</button>
<button id="stop-seeding" class="secondary" type="button" disabled>Stop seeding</button>
</div>
</div>
<div class="gate">
<p id="sign-event-copy">Signing creates a NIP-94 file event locally. Configured trackers also add a NIP-35 torrent index.</p>
<button id="sign-events" type="button" disabled>Review and sign events</button>
<p>Save the signed file event to recover without a discovery relay. It contains public metadata, never the file or its recovery key. Keep the recovery key separately.</p>
<div id="signed-event-links" class="downloads"></div>
</div>
<div class="gate danger">
<label class="check">
<input id="publish-consent" type="checkbox" />
<span>I understand these signed events will be public and difficult to retract.</span>
</label>
<button id="publish-events" type="button" disabled>Publish signed events</button>
</div>
<output id="publish-status" class="status" aria-live="polite">Waiting for a file.</output>
<div id="publish-links" class="downloads"></div>
</section>
<section id="client-retrieve" class="panel" aria-labelledby="retrieve-heading">
<div class="panel-heading">
<span>03</span>
<div>
<h2 id="retrieve-heading" tabindex="-1">Retrieve and verify</h2>
<p>Start with your saved file event or pool receipt. Verify it locally, enter the recovery key when asked, then fetch and save the verified file. No signer is needed for ordinary recovery.</p>
</div>
</div>
<label>
Nostr event ID <small>optional for a saved event; when supplied, it must match</small>
<input id="event-id" type="text" inputmode="text" maxlength="64" placeholder="64-character hex event ID" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no" />
</label>
<label>
Another Blossom server (optional)
<input id="replica-server" type="url" aria-describedby="replica-help" placeholder="https://replica.example.com" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no" />
</label>
<p id="replica-help" class="hint">If the original server is unavailable, enter a server that already holds a copy before resolving the event. Leave blank to use the signed event's URL. A Blossom fetch contacts only the chosen server, which sees your connection and the file's hash. The signed size, hash and encryption checks still apply. This does not create a replica or prove ongoing storage.</p>
<label id="recovery-key-field" hidden>
Recovery key
<input id="recovery-key-input" type="password" inputmode="text" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no" placeholder="wbk1_…" />
</label>
<div class="actions">
<button id="resolve-event" type="button">Resolve signed event</button>
</div>
<details id="saved-recovery">
<summary>Use a saved file event or pool receipt</summary>
<p>Load the signed file event or pool receipt you saved, or paste its JSON below. You do not need to configure relays or a publishing layout for this. Verification checks its signature and file information locally. Check the author or retained event ID before fetching; a valid signature alone does not identify someone you trust.</p>
<label>
Saved event or pool receipt <small>JSON, at most 128 KiB</small>
<input id="saved-event-file" type="file" accept="application/json,.json" />
</label>
<label>
Complete signed file event or pool receipt JSON
<textarea id="saved-event-json" rows="6" maxlength="131072" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
</label>
<div class="actions">
<button id="verify-saved-event" type="button">Verify saved event locally</button>
</div>
</details>
<dl id="resolved-facts" class="facts" aria-live="polite"></dl>
<div id="resolved-event-links" class="downloads"></div>
<div id="pool-repair-panel" class="gate" hidden>
<p>Repair reconstructs ciphertext locally without a recovery key, then uploads only the intended parts to their approved nodes. Connect the receipt author’s signer first. The browser must remain open.</p>
<label>Replacement nodes (optional) <small>One part number (starting at 1), URL, failure group and optional weight per line. Adding nodes requires a new signed receipt; save it before closing the page. Existing nodes cannot be reassigned to a different part.</small>
<textarea id="pool-replacements" rows="3" maxlength="8192" placeholder="1 https://replacement.example new-site 1" autocomplete="off" autocapitalize="off" autocorrect="off" spellcheck="false" translate="no"></textarea>
</label>
<label class="check"><input id="pool-repair-consent" type="checkbox" /><span>I approve reading this receipt’s nodes, reconstructing ciphertext here, and signing uploads to restore its storage layout.</span></label>
<button id="repair-pool" type="button" disabled>Verify and repair pool</button>
</div>
<div class="actions split">
<button id="fetch-blossom" type="button" disabled>Fetch and verify from Blossom</button>
<label class="check compact">
<input id="download-swarm-consent" type="checkbox" />
<span>I accept the swarm IP-address disclosure.</span>
</label>
<button id="fetch-swarm" type="button" disabled>Join swarm and verify</button>
<button id="cancel-download" class="secondary" type="button" disabled>Cancel download</button>
</div>
<output id="retrieve-status" class="status" aria-live="polite">No event resolved.</output>
<div id="retrieve-links" class="downloads"></div>
</section>
<p class="text-links"><a href="#top">Back to the overview</a></p>
</div>
<footer>
<p>Privacy is a set of bounded controls, not a badge. Verify the threat model before using sensitive material.</p>
<p><a href="https://github.com/forgesworn/wildbloom" rel="noreferrer">Source</a> · <a href="https://github.com/forgesworn/wildbloom/blob/main/LICENSE" rel="noreferrer">MIT licence</a> · <a href="https://github.com/forgesworn/wildbloom/blob/main/docs/PRIVACY.md" rel="noreferrer">Privacy model</a> · <a href="https://github.com/forgesworn/wildbloom/blob/main/SUPPORT.md" rel="noreferrer">Support</a> · <a href="https://github.com/sponsors/TheCryptoDonkey" rel="noreferrer">Sponsor ForgeSworn</a> · <a href="https://github.com/forgesworn/wildbloom/security" rel="noreferrer">Security</a></p>
<p><a href="https://github.com/forgesworn/wildbloom/blob/main/docs/legal/terms-draft.md" rel="noreferrer">Terms</a> · <a href="https://github.com/forgesworn/wildbloom/blob/main/docs/legal/privacy-notice-draft.md" rel="noreferrer">Privacy notice</a> · <a href="https://github.com/forgesworn/wildbloom/blob/main/docs/legal/online-safety-position-draft.md" rel="noreferrer">Online safety position</a></p>
</footer>
</main>
<script type="module" src="/src/main.ts"></script>
</body>
</html>