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

Listen for nopin attribute #19

Open
JohnONolan opened this issue Jun 16, 2015 · 2 comments
Open

Listen for nopin attribute #19

JohnONolan opened this issue Jun 16, 2015 · 2 comments

Comments

@JohnONolan
Copy link

Hey guys, just a thought: It would be incredibly handy if the buffer extension would respect the "nopin" attribute when applying its "share image" overlay: https://help.pinterest.com/en/articles/prevent-pinning-your-site

Context: While the chrome-settings flag determines whether or not a Buffer-user wants to use the share feature -- This feature provides control to the web developer to determine which images should (and should not) be shared from their site.

Eg. In the Ghost admin area, we have an image uploader for your blog cover image:

image

Here I've just finished uploading a new cover image for my blog. Now, because this is an admin area of a web-app, it makes no sense for social sharing to occur here. In fact the hover buttons usually get away and interfere with the app UI. So in the source of Ghost admin I've set <meta name="pinterest" content="nopin" /> -- as you can see, the pinterest button does not appear.

This is good because as a Buffer and a Pinterest user I want the feature enabled on all sites I visit, but I also want it disabled in this specific context where it doesn't make sense.

It would be possible to add a nobuffer attribute that does the same thing, but I think it might be simpler just to have the Buffer extension listen for the nopin attribute -- making the relatively safe assumption that if a developer has already disabled the Pinterest hover button, they'll probably want to disable the buffer one too.

Is this something you would consider?

@nieldlr
Copy link
Contributor

nieldlr commented Jun 16, 2015

Hi @JohnONolan,

thanks for sharing this great suggestion! My initial hunch is that this is a great improvement. Really great idea! I'll chat with the team and get back to you on this one. :)

Stay tuned.

@unicolored
Copy link

Hi @nieldlr,

Any news about this nopin attribute ?

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