Closed jayvdb closed 6 years ago
meta property="og:image"
contains image url at a lot of times. check that out
Should we make this a backend only task to begin with? Then you can think about the UI a bit, and then create another task to do the UI?
Yes, that's what I had in mind. Backend will start passing avatar links and then we can figure out the frontend part
Is there a reason to rely on metadata only? Why not add proper image fetching for valid usernames as link templates to websites.yml(and use it)
Ex. FB provides images at https://graph.facebook.com/{userid}/picture?type=square , so we just fetch from that(without relying on og:image
.
@nalinbhardwaj they're not available for all websites, but yes if we can get them, they're a better option to handle image fetch.
Apart from this, in case of fb, we'll have to extract userid
from the profile source anyways to use this url.
Might be helpful: https://developer.twitter.com/en/docs/tweets/optimize-with-cards/overview/summary
Most of the websites have some sort of avatar which can be obtained and included in the results for 'Taken' names.
This will help to see whether a username has a consistent avatar across various platforms, which can be used as a proxy to guess that they are taken by the same person.