Base64 Photograph Hosting, Together With Opened Upwards Graph Code
Friday, February 13, 2015
Edit
Some weblog owners brand photos an of import role of weblog content.
When sharing a post service to FaceBook, problems are seen amongst photograph content. In or together with then cases, this is because of how the photos were added into the post, when using Post Editor.
We've known close problems amongst photos installed using drag together with drop, together with post service editor, for a few years. Drag together with Drop photos, inwards or together with then cases, are stored every bit "Base64" content - amongst the photograph content hosted inwards the post, instead of Google Photos (or Picasa).
Photos added to posts inwards post service editor, using "drag together with drop", convey been a work for many years.
Base64 hosted photos brand posts abnormally large.
Posts containing "Base64" encoded photos are abnormally large - together with volition campaign problems amongst the index pages, together with automobile pagination. That is a nuisance - but precisely that.
With posts shared to social media, such every bit FaceBook together with Twitter, photos hosted using Base64 transcend away to a greater extent than than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to position substitution post service content - such every bit a photograph to accompany the shared post.
Open Graph code uses URLs to reference photos.
OG code uses HTML / XML tags, inwards template code - amongst a URL identifying a shared photo. Influenza A virus subtype H5N1 post service that contains Base64 hosted photos won't convey URLs identifying the photos - it volition convey the actual photograph content.
When shared to FaceBook, the photograph must hold out converted to normal Google Photo hosted content, together with then it tin hold out shared using a URL - every bit normal photos are shared, using OG code. If shared using Base64 content (if OG were to back upwardly Base64), the post, again, becomes abnormally large.
Base64 hosted photos but introduce 1 to a greater extent than complication, when sharing posts to FaceBook, Twitter, together with other social services.
Some weblog owners pose out posts that comprise photos added using drag together with drop. Some drag together with drib installs consequence inwards Base64 hosted photos - which must hold out converted to Google Photos hosted content, when shared to FaceBook or Twitter.
When sharing a post service to FaceBook, problems are seen amongst photograph content. In or together with then cases, this is because of how the photos were added into the post, when using Post Editor.
We've known close problems amongst photos installed using drag together with drop, together with post service editor, for a few years. Drag together with Drop photos, inwards or together with then cases, are stored every bit "Base64" content - amongst the photograph content hosted inwards the post, instead of Google Photos (or Picasa).
Photos added to posts inwards post service editor, using "drag together with drop", convey been a work for many years.
Base64 hosted photos brand posts abnormally large.
Posts containing "Base64" encoded photos are abnormally large - together with volition campaign problems amongst the index pages, together with automobile pagination. That is a nuisance - but precisely that.
With posts shared to social media, such every bit FaceBook together with Twitter, photos hosted using Base64 transcend away to a greater extent than than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to position substitution post service content - such every bit a photograph to accompany the shared post.
Open Graph code uses URLs to reference photos.
OG code uses HTML / XML tags, inwards template code - amongst a URL identifying a shared photo. Influenza A virus subtype H5N1 post service that contains Base64 hosted photos won't convey URLs identifying the photos - it volition convey the actual photograph content.
|
| This photograph was installed, using drag together with drop. Interestingly enough, it is non Base64. It is possible that Blogger no longer uses Base64 encoding - which would explicate why the work amongst OG code is rather irregular. |
When shared to FaceBook, the photograph must hold out converted to normal Google Photo hosted content, together with then it tin hold out shared using a URL - every bit normal photos are shared, using OG code. If shared using Base64 content (if OG were to back upwardly Base64), the post, again, becomes abnormally large.
Base64 hosted photos but introduce 1 to a greater extent than complication, when sharing posts to FaceBook, Twitter, together with other social services.
Some weblog owners pose out posts that comprise photos added using drag together with drop. Some drag together with drib installs consequence inwards Base64 hosted photos - which must hold out converted to Google Photos hosted content, when shared to FaceBook or Twitter.
