starred/immich

Fork 0

mirror of https://github.com/immich-app/immich.git synced 2026-03-02 22:57:45 -05:00

[Feature] Per user "minimum face count" #6512

New issue

Open

opened 2026-02-20 04:13:12 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 04:13:12 -05:00

Owner

Originally created by @jrasm91 on GitHub (Aug 25, 2025).

Each individual user should be able to specify a "minimum face count" that filters out people on the /people endpoint & associated page. This should be added as a user preference (probably at people.minimumFaces), and can be set to any number, with 0 implying that no people are filtered out of view.

Background

There is a server config option (machineLearning.facialRecognition.minFaces), that is used during the clustering process to determine at what threshold a Person is created. This same configuration setting is being used as a global cutoff for the /people endpoint, and has led to some confusion.

Originally created by @jrasm91 on GitHub (Aug 25, 2025). Each individual user should be able to specify a "minimum face count" that filters out people on the `/people` endpoint & associated page. This should be added as a user preference (probably at `people.minimumFaces`), and can be set to any number, with `0` implying that no people are filtered out of view. ## Background There is a server config option (`machineLearning.facialRecognition.minFaces`), that is used during the clustering process to determine at what threshold a Person is created. This same configuration setting is being used as a global cutoff for the `/people` endpoint, and has led to some confusion.

deekerman added the

good first issue

label

2026-02-20 04:13:12 -05:00

deekerman commented

2026-02-20 04:13:12 -05:00

Author

Owner

@Jtho28 commented on GitHub (Aug 26, 2025):

Does anyone have a branch open already for this? I'm thinking I will pick this up but don't want to step on anyone's toes.

@Jtho28 commented on GitHub (Aug 26, 2025): Does anyone have a branch open already for this? I'm thinking I will pick this up but don't want to step on anyone's toes.

deekerman commented

2026-02-20 04:13:12 -05:00

Author

Owner

@jrasm91 commented on GitHub (Aug 26, 2025):

Nope, feel free!

@jrasm91 commented on GitHub (Aug 26, 2025): Nope, feel free!

deekerman commented

2026-02-20 04:13:12 -05:00

Author

Owner

@Jtho28 commented on GitHub (Sep 4, 2025):

This is done, but I'm wondering if we really want to add a whole new 'people' key in the config. That is how I implemented it, but does anyone have a better idea?

I also considered adding it in the metadata section of the config, but I'm not sure it really fits there.

@Jtho28 commented on GitHub (Sep 4, 2025): This is done, but I'm wondering if we really want to add a whole new 'people' key in the config. That is how I implemented it, but does anyone have a better idea? I also considered adding it in the metadata section of the config, but I'm not sure it really fits there.

deekerman commented

2026-02-20 04:13:12 -05:00

Author

Owner

@tysoncung commented on GitHub (Dec 9, 2025):

I'm interested in working on this issue. Could you provide more context about what you're looking for? Any additional details about requirements or constraints would be helpful.

@tysoncung commented on GitHub (Dec 9, 2025): I'm interested in working on this issue. Could you provide more context about what you're looking for? Any additional details about requirements or constraints would be helpful.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/immich#6512

No description provided.

Rows
Columns