I did read the entire thread, the site developer offered two different solutions. But the other commenters seemed to dismiss both suggestions, preferring to fetch their pitchforks instead.
His “solution” would be to hack it to avoid that specific person's image, which is not really solving anything, other than the site author’s own problem.
The footer of uifaces still says _mockups_ and the FAQ/TOS haven’t been available for a while. This is clearly playing legal sword fighting and unethical.
I'm not sure I'd consider anything he suggested a good solution, though.
What he's done, and the aggressive/dismissive way he's handled a perfectly reasonable request afterwards, are what very expensive defamation lawsuits are made of. That is as it should be, IMHO, given that notwithstanding the developer's personal opinions about visitors understanding, the consequences of his actions demonstrably did reach someone close to the person whose photo was used and cause real distress and concern.
ricardobeat|8 years ago
The footer of uifaces still says _mockups_ and the FAQ/TOS haven’t been available for a while. This is clearly playing legal sword fighting and unethical.
Silhouette|8 years ago
What he's done, and the aggressive/dismissive way he's handled a perfectly reasonable request afterwards, are what very expensive defamation lawsuits are made of. That is as it should be, IMHO, given that notwithstanding the developer's personal opinions about visitors understanding, the consequences of his actions demonstrably did reach someone close to the person whose photo was used and cause real distress and concern.