Skip to content

chore(browser-extension): remove abandoned Chrome extension#32

Merged
sanity merged 1 commit intomainfrom
remove-browser-extension
Apr 13, 2026
Merged

chore(browser-extension): remove abandoned Chrome extension#32
sanity merged 1 commit intomainfrom
remove-browser-extension

Conversation

@sanity
Copy link
Copy Markdown
Contributor

@sanity sanity commented Apr 13, 2026

Problem

rust/browser-extension/ contained a Chrome extension that was never finished and is superseded by the Ghostkey Vault delegate (freenet/ghostkeys). The delegate runs inside any Freenet node, is reachable from every Freenet webapp via the message API, doesn't require a browser-specific install, and benefits from the same cryptographic sandboxing as the rest of the runtime.

Leaving the WIP extension in the tree is actively misleading. It also contains a latent bug — the signing-key PEM label mismatch tracked in #30 — which would surface if anyone tried to import a real ghost key.

Approach

Delete rather than fix. The directory is self-contained:

  • Not a member of rust/Cargo.toml's workspace.
  • No Makefile.toml task references it.
  • No CI workflow in .github/workflows/ builds it.

Fixes

Closes #30.

[AI-assisted - Claude]

The `rust/browser-extension/` directory contained a Chrome extension
that was never finished and is superseded by the Ghostkey Vault
delegate (`freenet/ghostkeys`), which runs inside any Freenet node
and is reachable from every Freenet webapp via the message API. The
delegate is strictly better: it doesn't require a browser-specific
install, works on any host that runs Freenet, and benefits from the
same cryptographic sandboxing as the rest of the runtime.

Leaving the WIP extension in the tree is actively misleading — it
also contains a latent bug (signing-key PEM label mismatch,
#30) that would surface if anyone tried to import a real
ghost key. Delete it rather than fix it.

The Rust workspace at `rust/Cargo.toml` does not include
`browser-extension`, no Makefile.toml task references it, and no CI
workflow builds it, so the removal is self-contained.

Closes #30.

[AI-assisted - Claude]
@sanity sanity merged commit 3cd0c6f into main Apr 13, 2026
1 check passed
@sanity sanity deleted the remove-browser-extension branch April 13, 2026 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Browser extension: signing-key PEM label mismatch (SIGNING_KEY_V1 vs ED25519_SIGNING_KEY_V1)

1 participant