TPThelen Thank you for sharing screen shots.
I think I know what the problem is, but to explain it I will need to go into some technical details here.
Originally (or, it is better to say, at some point of its evolution, but quite a while ago) Tonfotos classification algorithm was relying not only on user input to consider face as confirmed, but also on its confidence. And when this confidence was above certain threshold, it would not even propose face for confirmation, but would consider it confirmed from the start (but still would track in the database that decision was not made by user).
However, this approach was not ideal, and even though threshold was pretty high, sometimes it still would accept false positives without asking. I got lots of negative feedback from users, since users can’t really see how much time this approach saved them, they saw only mistakes it made. So couple of moths or so ago I decided that it is better to turn off this automatic confirmation and not irritate people.
You are with us for a long time already, and thank you very much for that. However, that means some of the faces in your library were accepted automatically, back then when this function was there. And since logic has evolved a bit sine then, you experience this oddities.
Those faces were indeed not confirmed by you, that is why program is still asking you to confirm. But they were confirmed automatically, so they are displayed as confirmed. This is definitely a bug on my side, but this case is quite rare that is why it slipped thru the cracks. I will plan fixing these oddities, but you don’t have to wait and can use quick workaround right now. To fix this, all you need to do is to finally confirm all those semi-confirmed faces. You can do that just with few clicks:
- select all faces for for a person (with context menu)
- then do “confirm”.
That is it. This will just mark all semi-confirmed faces for that person as fully confirmed and problem will go away.
Hope that makes sense to you.