Sharing on Social Media

Is it possible to share a post on Facebook without it randomly selecting an image from some other video on the Sift for the preview image?

Because that's exactly what happens to me, no matter how I go about trying to share from here to Facebook: random image, every time.

Example: https://www.screencast.com/t/dfJM7tH4i

It makes sharing any VideoSift content basically impossible.
dag says...

Comment hidden because you are ignoring dag. (show it anyway)

That's not entirely true that you heard nothing back. I responded to you on your profile the first time you mentioned it. We know it's a problem and we've been discussing it. If it was an easy fix that we knew how to fix ... it would be fixed. I find it annoying too.

We had to go to SSL because of browser changes that Google made to Chrome - this is an unfortunate side-effect. We've tried a few things to fix it to no avail ... but we'll get there.

eric3579 said:

I addressed this issue privatley with the powers that be a week ago and have heard nothing back regarding a possible resolution. @lucky760 @dag

Any sifter out there have an idea for a potential fix of this issue? Possibly has something to do with SSL as it seems to have coincided with its implimintation https://videosift.com/talk/SSL-Now-Enforced-Site-Wide

mxxcon says...

Fecesbook has open graph testing tool where you can see exactly what they see https://developers.facebook.com/tools/debug
I don't use fecesbook, so this is simply speculation on my part.
Perhaps this is an issue with og:image and og:image:secure_url open graph tags?
Since VideoSift is now SSL, maybe it makes sense to remove og:image:secure_url tag and only use og:image with https:// url? If people go to the site using http://, they can still access https:// links.
I checked https://videosift.com/video/elia-the-worlds-most-frustrating-work-of-art using http://iframely.com and http://opengraphcheck.com/ and both show correct thumbnails.

I'd also like to point out that guys are not gzip'ing CSS and JS resources.

eric3579 says...

My apologies. I get easily wound up sometimes...most all the time. Yes, you did acknowledge the issue, and Im sorry if I came off as if you didn't respond at all. My bad.

dag said:

Quote hidden because you are ignoring dag. (show it anyway)

That's not entirely true that you heard nothing back. I responded to you on your profile the first time you mentioned it. We know it's a problem and we've been discussing it. If it was an easy fix that we knew how to fix ... it would be fixed. I find it annoying too.

dag says...

Comment hidden because you are ignoring dag. (show it anyway)

No apology required. I know it comes from a good place - just don't want people to think we don't care about this. We've tried a few things. The last thing we tried was this. http://stackoverflow.com/questions/8855361/fb-opengraph-ogimage-not-pulling-images-possibly-https but it didn't work. :-(

eric3579 said:

My apologies. I get easily wound up sometimes...most all the time. Yes, you did acknowledge the issue, and Im sorry if I came off as if you didn't respond at all. My bad.

dag says...

Comment hidden because you are ignoring dag. (show it anyway)

Thanks mxxcon - we have been using that tool and it's been some help. We think it's something with og:image and ssl.

mxxcon said:

Fecesbook has open graph testing tool where you can see exactly what they see https://developers.facebook.com/tools/debug
I don't use fecesbook, so this is simply speculation on my part.
Perhaps this is an issue with og:image and og:image:secure_url open graph tags?
Since VideoSift is now SSL, maybe it makes sense to remove og:image:secure_url tag and only use og:image with https:// url? If people go to the site using http://, they can still access https:// links.
I checked https://videosift.com/video/elia-the-worlds-most-frustrating-work-of-art using http://iframely.com and http://opengraphcheck.com/ and both show correct thumbnails.

I'd also like to point out that guys are not gzip'ing CSS and JS resources.

lucky760 says...

Thanks for pointing this out. CSS actually was already being gzipped, but a config discrepancy caused some JS not to be, but it is now.

mxxcon said:

I'd also like to point out that guys are not gzip'ing CSS and JS resources.

Send this Article to a Friend



Separate multiple emails with a comma (,); limit 5 recipients






Your email has been sent successfully!

Manage this Video in Your Playlists

New Blog Posts from All Members