docs(features): People in Galleries — face recognition (#1074) - #9
Open
the-luap wants to merge 1 commit into
Open
docs(features): People in Galleries — face recognition (#1074)#9the-luap wants to merge 1 commit into
the-luap wants to merge 1 commit into
Conversation
Covers the optional picpeak-ml sidecar: what it needs, the two deliberate switches that turn it on, what guests see, managing and tuning the groups, and the privacy handling. Two things get stated plainly rather than buried, because both surprise people otherwise: - Face data is deliberately excluded from backups and .picpeak exports, so a restore re-scans — and any names assigned are NOT recovered. Anyone relying on names needs to know that before they rely on them. - Hidden photos stay hidden: guest-facing counts and face thumbnails are computed only from photos that guest may see, so someone appearing solely in hidden photos never surfaces in the guest's people row. Also notes why PicPeak ships FaceNet/YuNet rather than the InsightFace models comparable tools use — those weights are non-commercial-only, and PicPeak's users run businesses on it. Claude-Session: https://claude.ai/code/session_01Ra4hcsYiKuQLbbRsg6EjAc
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation for the face-recognition feature landing in picpeak#1074.
New page at
app/features/face-recognition, plus its nav entry inapp/features/_meta.js(after Video Support).What it covers
Setup (one extra opt-in container), the two deliberate switches that turn it on, what guests actually see, managing and tuning the groups, troubleshooting, and privacy handling.
Two things stated up front rather than buried
Both surprise people otherwise:
.picpeakexports, so a restore re-scans — and names assigned to people are not recovered. Anyone relying on names needs to know before they rely on them, so it gets its own callout.The GDPR position is a warning callout at the top rather than a footnote: detected faces are Art. 9 special-category data in the EU, and the photographer is the controller. We provide the switch, not the consent.
Note
The tuning section quotes the shipped default threshold (0.50) and its measured error rates — 1.0% wrong merges, 8.2% duplicate entries — from the LFW benchmark run through PicPeak's own pipeline. If that default changes before release, this page needs the same edit.
Unrelated, spotted while editing:
app/features/_meta.jshas a duplicatecrmkey; the second silently wins. Left alone.https://claude.ai/code/session_01Ra4hcsYiKuQLbbRsg6EjAc