Skip to content

Plugins: the article, the vision, and a homepage card - #37

Merged
initcore0 merged 1 commit into
mainfrom
feat/plugins
Aug 4, 2026
Merged

Plugins: the article, the vision, and a homepage card#37
initcore0 merged 1 commit into
mainfrom
feat/plugins

Conversation

@initcore0

Copy link
Copy Markdown
Owner

The plugin system + voice-driven meme generator shipped (initcore0/openwhisp#244). This covers it on the site.

Changelog — nothing to do

initcore0/openwhisp#245 already added an August 2026 release (18 entries, 2685 tests). The vendored snapshot was already current, so /changelog picks it up automatically. This is the first time the page has two releases — verified it renders correctly: August above July, each with its own anchor, stat strip (18/9/2685 and 67/40/2009), and three category sections. No code changes needed.

Blog

New post — Plugins: a meme generator today, a local control plane for your voice tomorrow.

It opens with the fun (dictate "create a meme about code review taking three days"), then makes the argument you asked for: OpenWhisp already holds the microphone, on-device transcription, a local model, translation, and accessibility rights — so plugins turn it from a dictation app into a control plane where your voice drives local tools. The concrete framing is the paste problem: today, acting on a contract clause or a patient note means pasting it into some website under terms nobody read. A plugin does it on your machine, so there's no request to make a promise about.

It also covers why third parties are the point and the hard part, and is honest that this is deferred rather than solved.

Homepage

New "Plugins" feature card.

Accuracy

Grounded in #244 and docs/PLUGINS.md. It states plainly that plugins are in-repo and reviewed, that third-party install isn't supported yet, and presents the roadmap order (manifest/script → out-of-process → dylibs permanently ruled out) as the deliberate answer to trusting downloaded code beside microphone/accessibility/clipboard grants. Shipped guarantees described: off-until-enabled, external-is-listed-never-runnable, reviewed plugins win id collisions, clipboard gated before the read, networkHosts disclosed as a label (not a sandbox). Voice triggers quoted from the real manifest, including сделай мем.

Verified

Build + prerender pass (sitemap 20 → 21); article renders with 4 FAQ and the strict-matching note; all interlinks resolve; blog index lists it; homepage card present; two-release changelog verified in-browser; desktop + mobile clean; zero console errors; prod + mirror builds both correct.

🤖 Generated with Claude Code

The plugin system + voice-driven meme generator shipped (openwhisp #244),
and #245 already added the August 2026 changelog release — so the
/changelog page picks it up from the vendored snapshot with no changes
needed (verified: it renders both releases correctly, August above July,
each with its own stat strip).

- Blog: "Plugins: a meme generator today, a local control plane for your
  voice tomorrow". Leads with the fun (dictate "create a meme about…"),
  then makes the real argument: OpenWhisp already owns the mic, local
  transcription, a local model, and accessibility rights, so plugins turn
  it into a control plane where your voice drives local tools — instead
  of pasting a contract clause into some random website.
- Homepage: new "Plugins" feature card.

Honest about the current state throughout: plugins are in-repo and
reviewed, third-party install isn't supported yet, and the roadmap order
(manifest/script → out-of-process → never dylibs) is presented as the
deliberate answer to "what would it take to trust downloaded code next to
microphone and accessibility grants".

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@initcore0
initcore0 merged commit aef7e81 into main Aug 4, 2026
@initcore0
initcore0 deleted the feat/plugins branch August 4, 2026 03:46
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.

1 participant