mirror of
https://github.com/PR0M3TH3AN/bitgate.git
synced 2026-10-27 16:41:03 +00:00
thePR0M3TH3AN
adeba151b8
Renames the project and makes it as easy to adopt as BitLogin, which was the stated bar and which it did not previously meet. Rename (ADR 0005): @nostr-governance/* -> @bitgate/*, governance-* elements -> bitgate-*, createGovernanceRuntime -> createBitGate. "Governance" reads as DAO voting to this audience and named a category rather than a product; BitGate names the benefit and joins the bit- family that BitVid and BitRoad compose with. Domain types keep their names — the product is BitGate, the subject matter is still governance. The migration plan is left as written; this ADR records the change rather than rewriting history. Drop-in distribution (ADR 0006): adopting BitGate meant supplying a transport, authoring a policy, and wiring every element in JavaScript. Now: - createRelayTransport(urls) — WebSocket transport with reconnection, backoff, subscription replay, and cross-relay dedupe - policy presets (social, commerce, admin-only) addressable by name; the engine still carries no thresholds of its own - <bitgate-provider> — configuration in markup, with descendants finding the runtime through a bubbling context event rather than DOM walking, which breaks across shadow boundaries - npm run build:widget — a self-contained dist/bitgate.js That last one came from running it in a browser rather than from a test. Bare specifiers resolve in Node and vitest but not in a browser, so the widget source worked everywhere except a plain static page — the one place it exists to serve. The bundle is not committed: consumers build from reviewed source. Also found by running it: the provider's ready event fires during element upgrade, before a page that defines elements after parsing can attach a listener, so it now exposes `ready` as a promise too. Four bugs fixed along the way, three found by new tests and one by the browser: admin state stayed silent when a roster change altered capabilities but no denials; the relay transport sent every subscription twice on connect; the commerce preset computed a meaningless visibility verdict at checkout and could hide a listing from its own seller; <bitgate-status> threw on an unusable decision. 759 tests; lint, typecheck, and both builds clean.
61 lines
2.7 KiB
HTML
61 lines
2.7 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<title>BitGate drop-in</title>
|
|
</head>
|
|
<body>
|
|
<h1>Drop-in test</h1>
|
|
|
|
<!-- Everything below is configured in markup. No setup JavaScript. -->
|
|
<bitgate-provider relays="wss://relay.example" root="a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a1" policy="social">
|
|
<bitgate-veil profile="feed" target-user="d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4">
|
|
<p id="content">This content is governed.</p>
|
|
</bitgate-veil>
|
|
<bitgate-status profile="playback" target-user="d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4"></bitgate-status>
|
|
</bitgate-provider>
|
|
|
|
<pre id="result">running…</pre>
|
|
|
|
<script type="module">
|
|
import { defineBitGateElements } from "../packages/widget/dist/bitgate.js";
|
|
defineBitGateElements();
|
|
|
|
const out = [];
|
|
const provider = document.querySelector("bitgate-provider");
|
|
const veil = document.querySelector("bitgate-veil");
|
|
|
|
// Awaiting the promise avoids racing the ready event, which fires during
|
|
// element upgrade — before this script could attach a listener.
|
|
provider.ready.then(() => {
|
|
out.push("provider ready: " + Boolean(provider.runtime));
|
|
out.push("veil adopted runtime: " + (veil.runtime === provider.runtime));
|
|
out.push("policy: " + provider.runtime.policies.policy.id);
|
|
out.push("target from attribute: " + JSON.stringify(veil.target));
|
|
|
|
// Deny the creator and confirm the veil reacts with no further wiring.
|
|
provider.runtime.admin.setRoles({
|
|
root: "a1".repeat(32),
|
|
actors: { ["a1".repeat(32)]: ["super_admin"] },
|
|
});
|
|
provider.runtime.admin.upsertContribution({
|
|
actor: "a1".repeat(32),
|
|
kind: "user-deny",
|
|
targets: [{ type: "user", pubkey: "d4".repeat(32) }],
|
|
createdAt: 1,
|
|
});
|
|
|
|
// The social preset's feed profile caps a hide at "restrict", so the
|
|
// veil blurs rather than hides. Playback enforces the full decision.
|
|
const feed = provider.runtime.evaluate(veil.target, { profile: "feed" });
|
|
const playback = provider.runtime.evaluate(veil.target, { profile: "playback" });
|
|
out.push("feed visibility: " + feed.visibility.effect + " (blurred, not hidden)");
|
|
out.push("playback visibility: " + playback.visibility.effect);
|
|
out.push("reasons: " + feed.reasons.map((r) => r.id).join(", "));
|
|
out.push("veil is blurred: " + Boolean(veil.shadowRoot.querySelector(".blurred")));
|
|
document.getElementById("result").textContent = out.join("\n");
|
|
});
|
|
</script>
|
|
</body>
|
|
</html>
|