Base64 Photograph Hosting, Too Opened Upward Graph Code
Saturday, June 15, 2013
Edit
Some spider web log owners brand photos an of import business office of spider web log content.
When sharing a post service to FaceBook, problems are seen amongst photograph content. In exactly about cases, this is because of how the photos were added into the post, when using Post Editor.
We've known well-nigh problems amongst photos installed using drag as well as drop, as well as post service editor, for a few years. Drag as well as Drop photos, inwards exactly about 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 as well as drop", bring been a work for many years.
Base64 hosted photos brand posts abnormally large.
Posts containing "Base64" encoded photos are abnormally large - as well as volition campaign problems amongst the index pages, as well as machine pagination. That is a nuisance - but exactly that.
With posts shared to social media, such every bit FaceBook as well as Twitter, photos hosted using Base64 larn to a greater extent than than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to position cardinal 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. H5N1 post service that contains Base64 hosted photos won't bring URLs identifying the photos - it volition bring the actual photograph content.
When shared to FaceBook, the photograph must live on converted to normal Google Photo hosted content, as well as then it tin live on 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 ane to a greater extent than complication, when sharing posts to FaceBook, Twitter, as well as other social services.
Some spider web log owners set out posts that comprise photos added using drag as well as drop. Some drag as well as drib installs effect inwards Base64 hosted photos - which must live on 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 exactly about cases, this is because of how the photos were added into the post, when using Post Editor.
We've known well-nigh problems amongst photos installed using drag as well as drop, as well as post service editor, for a few years. Drag as well as Drop photos, inwards exactly about 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 as well as drop", bring been a work for many years.
Base64 hosted photos brand posts abnormally large.
Posts containing "Base64" encoded photos are abnormally large - as well as volition campaign problems amongst the index pages, as well as machine pagination. That is a nuisance - but exactly that.
With posts shared to social media, such every bit FaceBook as well as Twitter, photos hosted using Base64 larn to a greater extent than than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to position cardinal 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. H5N1 post service that contains Base64 hosted photos won't bring URLs identifying the photos - it volition bring the actual photograph content.
|
| This photograph was installed, using drag as well as 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 live on converted to normal Google Photo hosted content, as well as then it tin live on 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 ane to a greater extent than complication, when sharing posts to FaceBook, Twitter, as well as other social services.
Some spider web log owners set out posts that comprise photos added using drag as well as drop. Some drag as well as drib installs effect inwards Base64 hosted photos - which must live on converted to Google Photos hosted content, when shared to FaceBook or Twitter.
