Base64 Photograph Hosting, Too Opened Upwards Graph Code
Saturday, March 12, 2016
Edit
Some weblog owners brand photos an of import purpose of weblog content.
When sharing a post 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 nearly problems amongst photos installed using drag in addition to drop, in addition to post editor, for a few years. Drag in addition to Drop photos, inwards exactly about cases, are stored equally "Base64" content - amongst the photograph content hosted inwards the post, instead of Google Photos (or Picasa).
Photos added to posts inwards post editor, using "drag in addition to drop", convey been a occupation for many years.
Base64 hosted photos brand posts abnormally large.
Posts containing "Base64" encoded photos are abnormally large - in addition to volition drive problems amongst the index pages, in addition to motorcar pagination. That is a nuisance - but exactly that.
With posts shared to social media, such equally FaceBook in addition to Twitter, photos hosted using Base64 drib dead to a greater extent than than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to position primal post content - such equally 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 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, then it tin hold out shared using a URL - equally 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 only acquaint i to a greater extent than complication, when sharing posts to FaceBook, Twitter, in addition to other social services.
Some weblog owners discover posts that comprise photos added using drag in addition to drop. Some drag in addition to drib installs number inwards Base64 hosted photos - which must hold out converted to Google Photos hosted content, when shared to FaceBook or Twitter.
When sharing a post 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 nearly problems amongst photos installed using drag in addition to drop, in addition to post editor, for a few years. Drag in addition to Drop photos, inwards exactly about cases, are stored equally "Base64" content - amongst the photograph content hosted inwards the post, instead of Google Photos (or Picasa).
Photos added to posts inwards post editor, using "drag in addition to drop", convey been a occupation for many years.
Base64 hosted photos brand posts abnormally large.
Posts containing "Base64" encoded photos are abnormally large - in addition to volition drive problems amongst the index pages, in addition to motorcar pagination. That is a nuisance - but exactly that.
With posts shared to social media, such equally FaceBook in addition to Twitter, photos hosted using Base64 drib dead to a greater extent than than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to position primal post content - such equally 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 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 in addition to drop. Interestingly enough, it is non Base64. It is possible that Blogger no longer uses Base64 encoding - which would explicate why the occupation amongst OG code is rather irregular. |
When shared to FaceBook, the photograph must hold out converted to normal Google Photo hosted content, then it tin hold out shared using a URL - equally 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 only acquaint i to a greater extent than complication, when sharing posts to FaceBook, Twitter, in addition to other social services.
Some weblog owners discover posts that comprise photos added using drag in addition to drop. Some drag in addition to drib installs number inwards Base64 hosted photos - which must hold out converted to Google Photos hosted content, when shared to FaceBook or Twitter.
