Skip to content

Add blog post: speaker verification comes to OVOS#78

Open
JarbasAl wants to merge 1 commit into
masterfrom
add-speaker-verifier-post
Open

Add blog post: speaker verification comes to OVOS#78
JarbasAl wants to merge 1 commit into
masterfrom
add-speaker-verifier-post

Conversation

@JarbasAl

@JarbasAl JarbasAl commented Jun 16, 2026

Copy link
Copy Markdown
Member

Companion post for ovos-ww-verifier-plugin-speaker. Code-validated: HotWordVerifier framework (opm#341) + dinkum-listener loading (#191), voting semantics, TWO distinct fail-open behaviours (error vs enrolment), model-specific threshold with real score example, and the one-second wake-window reliability caveat. Preserves the original post's distinctive framing + attribution. No monetary values.

@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

A new blog post is added at _posts/2026-06-16-speaker-verifier.md introducing the OVOS Wake Word Verifier Plugin for speaker verification. It covers the verification concept, privacy design using local speaker embeddings and cosine similarity, installation/enrollment steps, mycroft.conf configuration, threshold tuning, and project attribution.

Changes

OVOS Speaker Verifier Blog Post

Layer / File(s) Summary
Front matter, concept narrative, and privacy design
_posts/2026-06-16-speaker-verifier.md
Post metadata is defined; the article describes the false-activation problem, the wake-word gating framework, speaker-embedding verification flow, and privacy-by-design properties (local-only, non-reversible numeric embeddings, no audio retention).
Setup, configuration, tuning, and attribution
_posts/2026-06-16-speaker-verifier.md
Installation and enrollment commands are shown alongside a mycroft.conf hotword/verifier configuration example; threshold tuning, per-profile thresholds, and fail_open semantics are explained; attribution, funding, and contribution prompts close the post.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A voice at the gate, a cosine to weigh,
No strangers shall trick my assistant today!
I enrolled every hop in my household with care,
With embeddings so local, no cloud in the air.
"Help build voice for all!" cries the rabbit with glee,
One blog post at a time — open, private, and free! 🎙️

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add blog post: speaker verification comes to OVOS' clearly and accurately summarizes the main change—adding a blog post announcing speaker verification capabilities for OpenVoiceOS.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-speaker-verifier-post

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@JarbasAl JarbasAl force-pushed the add-speaker-verifier-post branch 2 times, most recently from b5126b0 to 4dc31d4 Compare June 16, 2026 03:02
…pen behaviours, model-specific threshold, one-second-window caveat

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@JarbasAl JarbasAl force-pushed the add-speaker-verifier-post branch from 4dc31d4 to cf0076d Compare July 11, 2026 00: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