We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are content warnings for the social favicons - probably should be served up by us.
Ignoring API Gravatars as they will be updated soon, that is the last https error I can see.
The text was updated successfully, but these errors were encountered:
sounds good, it's probably worth just reusing the icons off the homepage anyway
@RichardBarrett what do you think
Sorry, something went wrong.
What is this discussion about?
On 26 November 2012 11:20, Thomas Davis notifications@github.com wrote:
sounds good, it's probably worth just reusing the icons off the homepage anyway @RichardBarrett https://github.com/RichardBarrett what do you think — Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-10701709.
@RichardBarrett https://github.com/RichardBarrett what do you think
— Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-10701709.
On the profile page, we are bringing the favicons directly from the websites. We are getting content warnings, I could try protocol relative links.
But does it make sense that maybe we should just reuse the social icon set on the home page, for social icons on a users profile.
No branches or pull requests
There are content warnings for the social favicons - probably should be served up by us.
Ignoring API Gravatars as they will be updated soon, that is the last https error I can see.
The text was updated successfully, but these errors were encountered: