Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify placeholder vs real profile pictures #667

Closed
dshanske opened this issue May 7, 2016 · 4 comments
Closed

Identify placeholder vs real profile pictures #667

dshanske opened this issue May 7, 2016 · 4 comments

Comments

@dshanske
Copy link

dshanske commented May 7, 2016

When there isn't an image set on Facebook, Twitter, etc....there is a stock image. Wondering if there is a way that Bridgy can either detect this and mark it up, or alternatively, decide this means there is no image and not pass it.

@snarfed
Copy link
Owner

snarfed commented May 7, 2016

interesting! i don't know if there's an existing mf2 property that means "this image is a placeholder," but agreed, we could definitely invent one, or just omit the image entirely.

most of the work would be finding the silo API fields or image URL regexes that tell us this. the changes would be entirely in granary. this isn't an itch for me personally, so feel free to dive in!

@snarfed snarfed changed the title Identify Lack of Image Identify placeholder vs real profile pictures Nov 26, 2016
@pabru
Copy link

pabru commented Aug 4, 2017

Perhaps they could be downloaded and SHA256-hashed, then the hash matched against a list of hashes for known placeholder images? That could work.

@snarfed
Copy link
Owner

snarfed commented Jan 27, 2020

hey @dshanske, do you still need this? did you have a concrete user-visible feature planned for distinguishing placeholder vs non-placeholder profile photos? and a concrete mf2 property? if not, i may close for lack of interest. haven't heard any other requests for it yet, or any user-visible feature in webmention receivers that would use it.

@snarfed
Copy link
Owner

snarfed commented Dec 5, 2020

tentatively closing this due to lack of use case and prior art. feel free to reopen!

@snarfed snarfed closed this as completed Dec 5, 2020
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

No branches or pull requests

3 participants