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
http://blog.stackoverflow.com/2014/01/stack-exchange-for-android-is-here/ uses https://developer.android.com/images/brand/en_generic_rgb_wo_60.png as the image for the Play store (near the top and again at the bottom of the post) and that link no longer works.
The archive.org version from 2014 shows that as a generic "Get It On Google Play" image:
https://web.archive.org/web/20141207160129/http://blog.stackexchange.com/2014/01/stack-exchange-for-android-is-here/
Not sure if we should just grab and re-host that image or if they have updated their branding/logo since 2014.
Assigning this to Kasra to fix/ignore as he sees fit :-P
The text was updated successfully, but these errors were encountered:
I'm gonna see what the new Google recommended icon is -- and host it on our imgur instance rather than hot link so this doesn't happen again.
Thanks for the heads up!
Sorry, something went wrong.
jc4p
No branches or pull requests
http://blog.stackoverflow.com/2014/01/stack-exchange-for-android-is-here/ uses https://developer.android.com/images/brand/en_generic_rgb_wo_60.png as the image for the Play store (near the top and again at the bottom of the post) and that link no longer works.
The archive.org version from 2014 shows that as a generic "Get It On Google Play" image:
https://web.archive.org/web/20141207160129/http://blog.stackexchange.com/2014/01/stack-exchange-for-android-is-here/
Not sure if we should just grab and re-host that image or if they have updated their branding/logo since 2014.
Assigning this to Kasra to fix/ignore as he sees fit :-P
The text was updated successfully, but these errors were encountered: