How to Install Dark Theme for Facebook

This is one of the most important things for you.You know that Facebook is the most widely used social media network in the world.Although it is banned from various countries, most countries use it.So it's still not a dark theme.If you are using youtube, you can see the dark theme in the present.It's very important for the night.It is easier for the eye to see the theme than white theme in the night.

How to Install Dark Theme for Facebook

However, perhaps we hope you will see the facebook dark theme in the future.This is because many sites have provided this theme to users.So let's see how to install the dark theme to facebook.

This can be done under very simple steps.And we need an extension for this.Its name is Dark theme for Facebook.So if you want to use this extension, you must have a Google Chrome browser or Opera browser.However, this extension is available for chrome browsers, but we can also use to opera.

Install extension

If you are using the opera browser, you must first install the chrome extension installer addon to opera.Also read How to Install Google Chrome Extensions for Opera.The extensions for chrome can be used in the opera via the addon.

1. First go to Dark Theme for Facebook.
2. Next click the Add to opera button.
   
3. Now click Install button in the Extensions Manager.

Apply Theme to Facebook

You are now installing the extension.Next you can use it for facebook.The special feature is, to the dark theme, you can set the theme you like.You can change the facebook theme using the colors you prefer.

1. First go to facebook.com.
2. Then click on the moon badge on the top right side of the web browser.
3. Then you will see a number of themes.
4. Click on Create new theme button and customize your theme.
   

So you know about How to Install Dark Theme for Facebook, Hope you like the post, don’t forget to share it with your friends and leave a comment below if you are facing any problem at any step in the method discussed above.Thank you

Facebook Info Has Been Misused - Mark Zuckerberg Apologies from Facebook Users

A few days ago some Facebook users had a big problem.That is, some user data, without authorization, has been obtained.So this also affects other users.With this incident, Facebook had a big impact.Facebook founder, Mark Zuckerberg, has admitted that he has failed to protect users' data.So, this situation has a big impact on facebook users' data.

A political consulting firm, Cambridge analytica, has used Facebook accounts of 50 million.It is also said that their personal data has been obtained.So this has been reported in various media about this incident.So with this problem, the international media has paid attention to it.The Channel 4 channel broadcast a video by Cambridge Analytica Company.So they have used false propaganda and intimidation.That is to try to change the political process of different countries.This is confirmed by the video transmitted by Channel 4.So these facts have been revealed by A Channel 4.

A person influencing a country politics, Support has been requested from Cambridge Analytica.So this incident reveals, Using a fake man who influences the election campaign in Sri Lanka.So when Channel 4 was exposed by the incident, it was widely publicized.So the research director who retired from the company, has made a statement to the British newspaper Guardian Newspapers.He has said that using a computer application to get facebook account information.

The Guardian

In addition, these applications are said to allow access to account information.He also says that it will be possible to go into one account and get accounts information of other friends.For this reason, Facebook was affected.So the founder of Facebook, Mark Zuckerberg, Interviews with CNN News has been held.So he asks for apologies from facebook users.

READ:

• How to Secure Your Facebook Account
• How to recover facebook all data
• How To Unfriend All Facebook Friends At Once
• Youtube video play in facebook with vtofb

So you know about Facebook Info Has Been Misused - Mark Zuckerberg Apologies from Facebook Users, Hope you like the post, don’t forget to share it with your friends and leave a comment below if you are facing any problem at any step in the method discussed above.Thank you.

FaceBook Popularity, And URL Changes

Not every blog owner understands the effect of a Blogger URL change, in FaceBook - and the resulting popularity of the blog.

I am planning on changing my blog name and redirecting my blogger blog to a custom domain. Why would that affect my Facebook followers?

A Blogger URL change won't affect your FaceBook Followers directly. Your existing Followers can continue to Follow your blog, under the BlogSpot URL - and under the custom domain URL - as it is Liked, and shared, in FaceBook.

The Likes count affects the possibility of a share, of a post in your blog, to attract new Followers.

URL changes, as permitted and provided by Blogger and / or FaceBook, are easy enough to make.

If you change the URL of the blog, when it's later shared in FaceBook, you will have a different blog. If you redirect your Blogger blog to a properly setup custom domain, you will have a blog that is shared under a different URL - and you'll have a new Likes counter.

A Like will be counted against the URL of the post that is Liked.

If someone Likes your blog in FaceBook, the Like will be counted against the URL used to address the blog, in the FaceBook post being shared.

You can either count your Likes under the current BlogSpot URL - or the new URL. Just choose the URL that's used, when it's shared.



If you publicise the blog, in FaceBook, using the current BlogSpot URL, the Like will be applied against that URL. This will not contribute to popularity of the custom domain URL - and the new blog identity. The custom domain will get no Likes - and the blog will continue to be seen, in Facebook, under the BlogSpot URL.

If you publicise the blog, in FaceBook, using the custom domain URL, the Like will be applied against the custom domain URL. The blog will not benefit from popularity of the BlogSpot URL - and the current blog identity. The BlogSpot URL will get no Likes - and the blog will be seen, in Facebook, under the custom domain URL.

You are allowed to change the blog URL, by both Blogger and FaceBook.

You are allowed to change the URL of the blog, in Blogger. You can change the BlogSpot URL, to a different BlogSpot name. You can change the domain URL, to a custom domain. You can change both the BlogSpot and domain URLs, if you wish.

Either way you change the URL, you will end up with a different URL, when shared in FaceBook. And with your posts shared using a different URL, you will have Likes counted using a different counter. This isn't a question of what FaceBook lets you do - it's a question of how they count the Likes, that apply to your blog.

You will need to move forward, using your new custom domain URL, and starting with 0 Likes - or stay where you are, using the current BlogSpot URL, and continuing with the current Likes counter. FaceBook will let you do either. They just won't be able to help you do both, at the same time.

This is really just one more detail, in re indexing a blog, after a URL change.

---

If you change the URL of a #Blogger blog, #FaceBook popularity will be affected. You (or any reader) can share the blog using either the current or new URL - and any Likes received for a share will apply to the URL used.

The blog will appear under two (or more) different URLs - a known effect of republishing.

Social Sharing Popularity, And URL Changes

As both custom domain publishing, and social sharing networks, become normal with many blogs, we see anguish when blog owners change the URLs of their blogs, without planning for the effects of the change.

What happened to my Likes?

This blog owner - and many others - do not realise that FaceBook counts Likes, based on the URL, not the blog.

FaceBook Likes, and Google+ +1s, are counted by URL - and are not controlled by DNS redirection, or simple name changes. If you rename your blog, you get a new URL with a new popularity counter, in FaceBook and Google+.

Some social sharing services allow for URL changes.

BlogLovin lets you transfer Followers from one URL to another.

BlogLovin, for instance, provides for transfer of Followers, to a new URL - as long as the blog owner owns both the old and new URL.

First, make sure that you've claimed both of your blogs.

Once both blogs are claimed, navigate to "My blog" and select the "Edit Blog Info" option next to your original blog.

From the "Move Followers" dropdown menu, select the blog you'd like to move your followers to and click "Move". This will remove your original blog and move your followers to your new blog of choice.

Start from any BlogLovin page.

Select "Blog analytics" from the drop down menu.

Click "Edit blog info".

Select a blog, from the drop down blog menu, in the "Edit blog info" wizard - and click on "Move Followers".



Whether you have a blog with a new URL, or a blog with multiple feeds and groups of Followers, BlogLovin lets you consolidate / move Followers so you can address your Followers, conveniently.

Blogger Followers stay with the blog, automatically.

With a Blogger blog, and Blogger Following / Google Friend Connect, your Followers Follow the blog - not the URL. You can rename the blog, and change the URL - but as long as you don't change the BlogID, your Followers remain with your blog.

FaceBook and Google+ give you a new counter, for each URL.

Neither FaceBook or Google+ provide a similar option. To both FaceBook and Google+, if you change the URL of the blog, you have a new blog. Google+ Followers - unlike Blogger Followers - Follow the URL.

With custom domain publishing, and the BlogSpot to domain redirect, the attention of your Followers may end up on your redirected blog - but the +1 counter and Followers community, that was based on the BlogSpot URL, stays with the BlogSpot URL. With the blog published to the domain, your blog gets a counter and community for the domain URL - and starts over.

With a BlogSpot to BlogSpot URL change, and a domain to BlogSpot URL change, everything starts over.

FaceBook Likes are counted, within FaceBook - and Google+ +1s are counted, within Google+. Both are based on the URL of the blog which accrues the Likes and +1s. If you change the URL of the blog, you get a new counter - and a new Followers community.

A URL change is effective for different changes, to a Blogger blog.

• BlogSpot to BlogSpot name change.
• BlogSpot to custom domain republishing.
• Custom domain to custom domain change.
• Custom domain to BlogSpot republishing.

All of these are URL changes - and are treated as a different blog, for most social sharing services.

BlogLovin supports URL changes. Neither FaceBook, Google+, or LinkedIn provides this ability. You change the URL, you start over with +1 / Like count, Followers community, and sharing reputation.

---

With most social sharing services, if you change the URL of a #Blogger blog, you start over accumulating +1s, Followers, and Likes. BlogLovin appears to be alone, in letting you transfer Followers from one blog to another - if you create a new blog, or change the URL of an existing blog.

https://productforums.google.com/forum/#!category-topic/blogger/ZiozKZOS07Q

https://productforums.google.com/forum/#!category-topic/blogger/gkmBV6s03Ck

Cara Memasang Facebook Auto Like di Blog

Cara Memasang Facebook Auto Like Terbaru 2016 di Blog - Saat ini pengguna Facebook yang memliki fanpage semakin meningkat, namun acapkali jumlah like/suka terhadap fanpage yang kita miliki jauh lebih rendah dibandingkan jumlah pertemanan yang kita miliki.

Selain menggunakan cara manual dengan menginvite teman agar menyukai Fanpage yang kita miliki ada juga sacara lain yang lebih praktis dengan memasang script auto like fanpage. Syaratnya kamu harus mempunyai blog atau portal untuk menempatkan script autolike fanpage facebook ini. Mari kita ikuti langkah berikut ini :
Selengkapnya »

Add A FaceBook Gadget With FaceBook SDK Code

Some blog owners can't get their new FaceBook gadgets to work, on their blogs.

We see the occasional report, in Blogger Help Forum: Get Help with an Issue.

The blog won't accept the code that Facebook Developer generated for me.

Adding HTML gadgets - and HTML gadgets using FaceBook code - can be frustrating. But, it's possible.

Adding a FaceBook gadget, to your blog, is not difficult - but success is found, in the details.

• Add the gadget as a new HTML gadget.
• Add the FaceBook SDK code, to the first FaceBook gadget.

Add the gadget as a new HTML gadget.

Blog maintenance is far easier, with a FaceBook gadget - or any other HTML / JavaScript based accessory - added as content, in a new HTML gadget - far smarter than using Template Editor.

Add the FaceBook SDK code, to the first FaceBook gadget.

FaceBook instructs us to add SDK code to each page which will display a FaceBook gadget - but advises that we should only add the SDK code once / page.

Gadget code, as provided by FaceBook Developers:

<div class="fb-comments" data-href="http://ourladyofoutrage.blogspot.com/" data-numposts="5">
</div>

Gadget code, as added to a new HTML gadget:

<div id="fb-root">
</div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.5&appId=528167400699401";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

<div class="fb-comments" data-href="http://ourladyofoutrage.blogspot.com/" data-numposts="5">
</div>

A new FaceBook gadget, being added.



Just pay attention to the details, for best results.

---

Some #Blogger blog owners try to add accessories provided by FaceBook Developers, without success. They don't realise the importance of the details involved.

Blogger Resolves The FaceBook Photo Sharing Issue

Blogger Engineers recently added Blogger template code, to provide images in shares to FaceBook.

The added code is included in the standard template header. If you have a custom template, you may need to verify template header content.

If you have added the previously recommended Open Graph Code to your blog, to allow Open Graph based post / photo sharing - and you use the FaceBook Developers Debugger tool, you may see a new diagnostic suggestion.

Given newly added template code, blogs with added OG code may generate ominous warnings in the FaceBook Developers Debugger tool.

Looking at my blog, and the blog main page.

Object at URL 'http://blogging.nitecruzr.net/' of type 'article' is invalid because it specifies multiple 'og:url' values: http://blogging.nitecruzr.net/, http://blogging.nitecruzr.net/.

Looking at my blog, and a FaceBook Debug log, for this post.

Object at URL 'http://blogging.nitecruzr.net/2016/03/blogger-resolves-facebook-photo-sharing.html' of type 'article' is invalid because it specifies multiple 'og:url' values: http://blogging.nitecruzr.net/2016/03/blogger-resolves-facebook-photo-sharing.html, http://blogging.nitecruzr.net/2016/03/blogger-resolves-facebook-photo-sharing.html.

With Blogger now providing a properly resized image, automatically, from each post, the image provided in the previously suggested Open Graph code is now redundant - and causes duplication.

The browser source listing, for this post.

The FaceBook Debugger log, for this post.



Here's what I see now, in the standard template header.

<meta content='Blogger recently added template code, to properly share content to FaceBook. Learn how this affects your blog.' name='description'/>
<meta content='http://blogging.nitecruzr.net/2016/03/blogger-resolves-facebook-photo-sharing.html' property='og:url'/>
<meta content='https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEinBb17rkStDcQMf4ySxb5DdvxHQM51ZwDHKE1fpfLBsh4uYuz2XEKgs6Do0mySLXLrQB7j1N-GiquUrzKWMNo3I4GRL-KR79KB0HxBisfjUkYSNW9hSytOiTR3rJmGTOo1c1Hl0j6XjtWv/w1200-h630-p-nu/Screenshot+2016-03-13+at+14.35.32.png' property='og:image'/>

So, what do we have?

<meta content='https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEinBb17rkStDcQMf4ySxb5DdvxHQM51ZwDHKE1fpfLBsh4uYuz2XEKgs6Do0mySLXLrQB7j1N-GiquUrzKWMNo3I4GRL-KR79KB0HxBisfjUkYSNW9hSytOiTR3rJmGTOo1c1Hl0j6XjtWv/w1200-h630-p-nu/Screenshot%2B2016-03-13%2Bat%2B14.35.32.png' property='og:image'/>

The chosen image - resized to 1200 x 630, to suit the FaceBook recommended 1.9 aspect ratio - and large, to suit the FaceBook recommended size.

Now, 3 data elements (2 Open Graph) may be redundant.

• description
• og:image
• og:url

This makes the immediately previous advice unnecessary.

If one wishes to provide author information, that also becomes slightly simpler.

<!-- BEGIN Open Graph tags -->
<meta expr:content='data:blog.metaDescription' name='description' property='og:description'/>
<meta expr:content='data:blog.pageTitle' name='keywords'/>
<b:if cond='data:blog.pageType == "item"'>
<meta content='article' property='og:type'/>
<meta content='https://plus.google.com/nnnnnnnnnnnnnnnnnnnnn/about' property='article:author'/>
<meta expr:content='data:blog.pageName' property='og:title'/>
<b:else/>
<meta expr:content='data:blog.title' property='og:title'/>
<meta content='blog' property='og:type'/>
</b:if>
<meta expr:content='"en_US"' property='og:locale'/>
<!-- END Open Graph tags -->

If you truly want to share author details, you still have some work to do - but photos should now be shared, automatically, if your blog has a template with a standard header.

---

Recently, Blogger Engineering added OG code to the standard template header, to allow us to share posts with images to FaceBook, without having to add special code. This should help, for owners of blogs which have standard headers.

Base64 Photo Hosting, And Open Graph Code

Some blog owners make photos an important part of blog content.

When sharing a post to FaceBook, problems are seen with photo content. In some cases, this is because of how the photos were added into the post, when using Post Editor.

We've known about problems with photos installed using drag and drop, and post editor, for a few years. Drag and Drop photos, in some cases, are stored as "Base64" content - with the photo content hosted in the post, instead of Google Photos (or Picasa).

Photos added to posts in post editor, using "drag and drop", have been a problem for many years.

Base64 hosted photos make posts abnormally large.

Posts containing "Base64" encoded photos are abnormally large - and will cause problems with the index pages, and auto pagination. That is a nuisance - but just that.

With posts shared to social media, such as FaceBook and Twitter, photos hosted using Base64 become more than a nuisance. When normal posts are shared to FaceBook, OpenGraph code is used to identify key post content - such as a photo to accompany the shared post.

Open Graph code uses URLs to reference photos.

OG code uses HTML / XML tags, in template code - with a URL identifying a shared photo. A post that contains Base64 hosted photos won't have URLs identifying the photos - it will have the actual photo content.

This photo was installed, using drag and drop. Interestingly enough, it is not Base64. It is possible that Blogger no longer uses Base64 encoding - which would explain why the problem with OG code is rather irregular.

When shared to FaceBook, the photo must be converted to normal Google Photo hosted content, so it can be shared using a URL - as normal photos are shared, using OG code. If shared using Base64 content (if OG were to support Base64), the post, again, becomes abnormally large.

Base64 hosted photos simply present one more complication, when sharing posts to FaceBook, Twitter, and other social services.

---

Some blog owners publish posts that contain photos added using drag and drop. Some drag and drop installs result in Base64 hosted photos - which must be converted to Google Photos hosted content, when shared to FaceBook or Twitter.

Using The Meta Search Description In Your Blog

There is some confusion, about including "search description" meta content, in blog template code, to provide source for data shares to social sharing sites.

In various topics in Blogger Help Forum: Get Help with an Issue, I've seen references to "data:post.metaDescription", "data:post.snippet", and "data:post.pageTitle" used, in providing the blog post source for the FaceBook "og:description" tag. As far as I can tell, none of these exist.

The Layout data tag "data:blog.metaDescription", which provides "og:description", does exist - though it seems to be referenced, ambiguously.

Some FaceBook Open Graph content references different Blogger tags, depending upon page type. The FaceBook "og:title" references "data:blog.pageName" with an "item" (post) page, and "data:blog.title"; with other pages.

"og:description", on the other hand, only references one Blogger tag - "data:blog.metaDescription". The latter appears to change its source, depending upon whether the main page, or a post page, is being viewed.

• In main page mode, the per blog "Description", from Settings - Search preferences, is referenced.
• In post page mode, the per post "Search Description", from the Post Editor "Post settings", is referenced.

Source listing for this blog, in main page view.

"What Blogger won't (or can't) tell you. Blogger features and problems explained, using real life examples."

Source listing for this post, in post page view.

"Blogger provides the meta tag "data:blog.metaDescription", which seems to vary in source. Learn how it varies."



There is no mention of "data:blog.metaDescription", in the reference Blogger Help: Layouts Data Tags - as either a per blog, or per post, data element.

In my earlier post, my reference to "'data:blog.metaDescription' name='description'" was simple. But simplicity can lead to confusion.

<meta expr:content='data:blog.metaDescription' name='description' property='og:description'/>

Some tags are universal, others vary depending upon page type ("item" being post page).

<!-- BEGIN Open Graph tags -->
<meta expr:content='data:blog.metaDescription' name='description'' property='og:description'/>
<meta expr:content='data:blog.pageTitle' name='keywords'/>
<b:if cond='data:blog.pageType == "item"'>
<meta content='article' property='og:type'/>
<meta content='https://plus.google.com/nnnnnnnnnnnnnnnnnnnnn/about' property='article:author'/>
<meta expr:content='data:blog.canonicalUrl' property='og:url'/>
<meta expr:content='data:blog.pageName' property='og:title'/>
<b:if cond='data:blog.postImageUrl'>
<meta expr:content='data:blog.postImageUrl' property='og:image'/>
<b:else/>
<meta content='http://xxxxxxxxxxxxxxxxx/xxxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/S1600-R/yyyyyyyyyyyyy.gif' property='og:image'/>
</b:if>
<b:else/>
<meta expr:content='data:blog.title' property='og:title'/>
<meta expr:content='data:blog.canonicalHomepageUrl' property='og:url'/>
<meta content='blog' property='og:type'/>
<meta content='http://xxxxxxxxxxxxxxxxx/xxxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/S1600-R/yyyyyyyyyyyyy.gif' property='og:image'/>
</b:if>
<meta expr:content='"en_US"' property='og:locale'/>
<!-- END Open Graph tags -->

'data:blog.metaDescription' name='description' is referenced once, in the template code - and the source is apparently determined, based on the context.

If you find this confusing, I have to agree with you.

---

#Blogger provides the Layout data tag "data:blog.metaDescription", which is used for the FaceBook meta ag "og:description" - for both blog main page, and post pages, when shared. This is in contrast to the FaceBook meta tag "og:title" and others, which use different Blogger data tags for the main page and post pages.

This variation has caused some confusion - and attempted use of different non existent Blogger data tags.

Blogger Blog Readers Unable To Comment, Using OpenID Accounts Hosted By WordPress

We're seeing a scattered collection of reports, mentioning problems publishing comments, using OpenID authentication.

This problem appears to be related to the Blogger rollout of SSL support, for our blogs, which is currently in progress. SSL, or Secure Socket Layer, represents the next step in blog / website security - a step which the Internet community has been taking, for many years.

Blogger has been using SSL (aka "HTTPS" login), in their dashboard, for several years.

https://www.blogger.com

That's a secure Blogger login. The problem with Blogger using SSL in our blogs is that moving to SSL requires care, to avoid confusing our readers. Lack of care will subject our readers to the well known "mixed mode" warnings.

This site has insecure content.

Only secure content is displayed.

Firefox has blocked content that isn't secure.

These are several examples of what were normal, years ago, on many websites. Blogger does not want our readers subject to needless confusion, from these warnings.

Blogger blog owners have been asking, for years, that Blogger support SSL in BlogSpot (and our custom domains).

FaceBook upgraded to SSL, in 2013 - and saw problems with Blogger content.

Last year, FaceBook upgraded to SSL. Blogger blog owners, who were also FaceBook members, watched their Walls, which contained HTTP links to their Blogger blogs, show the "mixed mode" warnings.

The real issues begin to arise, however, when your application must include assets served by servers which also do not support SSL.

...

We’ve all experienced “mixed mode” warnings, with some browsers being much more annoying about them than others. "Mixed mode" means you requested a page over SSL, but some of the resources needed to fully render that page are only available over unencrypted HTTP.

Blogger is offering the option for us to upgrade our blogs, this year.

Now, Blogger is upgrading, so our blogs may (optionally) support the SSL protocol - and not confuse FaceBook members, who post links to our blogs. To avoid the "mixed mode" warnings, which would confuse our readers, they are upgrading all Blogger processes, including OpenID authentication, to support SSL.

The Blogger upgrade has exposed a WordPress inconsistency.

Just as FaceBook upgrading to SSL helped to cause Blogger to upgrade, so is Blogger upgrading to SSL exposing an inconsistency in WordPress use of SSL, for OpenID authentication.

The problem in my case (and maybe in others as well) seems to be that https://yourblog.wordpress.com is send for verification to the OpenId server. This is what I could figure out from the URL. If you than manually replace HTTPS with HTTP, it works.

This comment suggests that WordPress, which in general is using SSL security, has an OpenID server that has not been upgraded.

WordPress needs to check their OpenID servers.

So now, Blogger has to wait for WordPress to fall into step, consistently. Until WordPress upgrades their OpenID server, people who want to use a WordPress OpenID account, to comment on our blogs, will have to select "OpenID", instead of "WordPress" - then enter the WordPress OpenID URL, as

HTTP://whatever.wordpress.com

And wait for WordPress to upgrade their server.

FaceBook Is Aggregating BlogSpot CC Aliases

We're seeing a few questions recently, in Blogger Help Forum: Something Is Broken, about FaceBook, and their treatment of Blogger URLs that are subject to local country domain redirection.

When I share a post on FaceBook, the URL used for my blog ends with "blogspot.in" instead of "blogspot.com".

Some people in Europe observe a variation.

When I share a post on FaceBook, the URL used for my blog ends with "blogspot.nl" instead of "blogspot.com".

We've been observing, for a long time, that FaceBook and other Internet services should start using the canonical tag - and aggregate BlogSpot URLs, that are subject to local country domain redirection.

With aggregation done properly, all BlogSpot URLs would be listed as "blogspot.com" - and all Likes, and similar references to a given Blogger blog, would be later counted under the proper "blogspot.com" URL - regardless where a given blog reader gets Internet access.

Apparently, FaceBook is now aggregating BlogSpot URLs - but they are not successfully using the canonical URL, as provided by the tag in the blog header. FaceBook now uses "blogspot.in" - or maybe "blogspot.nl" or "blogspot.pe" - as the final URL for some Blogger blogs, when shared.

If you share your blog to FaceBook and observe this problem, try using the FaceBook Sharing Debugger. Select "Scrape Again", when you see "blogspot.pe", or another alias, in the debugger log.

Selecting "Scrape Again", enough times, may lead to the Debugger displaying "blogspot.com" - and your actual canonical blog URL will be cached. This will provide a work around until FaceBook corrects their sharing feature.

When Blogger first started using local country domain redirection, only Google services such as Google Search would reliably aggregate all local country domain references, to "blogspot.com".

Many non Google services did not use canonical aggregation, immediately. Like every other newly developed Internet feature, it takes time for every web service to update their code.

With only Google using canonical aggregation, every Blogger URL subject to country code alias redirection would be shared using the country domain, as seen by the person doing the sharing. People in France might share a Blogger URL as "blogspot.fr", people in India as "blogspot.in", and so on.

People in the USA, of course, would share a Blogger URL as "blogspot.com". The USA, and various other countries, is not subject to country code alias redirection.

FaceBook is now aggregating BlogSpot URLs - but they are not using the canonical tag, in the blog header. They are aggregating to "blogspot.in", "blogspot.nl", or "blogspot.pe" for some or all BlogSpot URLs, shared to their service.

Maybe, FaceBook is resolving "blogspot.com" from various countries that are subject to local country domain redirection - and generates the redirection themselves?



Right now, for some blog owners who share a BlogSpot URL to FaceBook, the URL will be modified, to "blogspot.in", "blogspot.nl", or "blogspot.pe". Every Like, and similar activity against that URL, will then be counted under the "blogspot.in", "blogspot.nl", or "blogspot.pe" alias. This is probably slightly better than having every different URL shared by country code alias - but only slightly better.

Blogger blogs published to custom domains are not subject to URL modification, because custom domain URLs are not subject to local country domain redirection.

Some Blogger blogs will continue to appear to have at 3 URLs - "blogspot.com", "blogspot.in", "blogspot.nl", or "blogspot.pe", and any others under which FaceBook was sharing, originally. The search engines may index blog content, accessed from FaceBook shares, as "blogspot.com", "blogspot.in", "blogspot.nl", or "blogspot.pe".

If this is not acceptable, you may need to report this to FaceBook Support. Please, resist the temptation to install malicious code on your blog, that will later leave you asking for advice on having the blog unlocked, cleaned and reviewed.

---

https://productforums.google.com/d/topic/blogger/2UXBv3Q21YY/discussion

Blogger Blogs Displaying Mysterious Transparent Boxes, Covering Blog Content

We're seeing a steady flood of problem reports about various Blogger blogs that have developed a mysterious transparent box, covering some portion of the blog surface when displayed. Some blogs display the box for all views, others for main page view only, and still others for specific individual posts. The box may be visible at the top of the page or in the middle - and may scroll with the screen, or may remain fixed relative to the display. In many cases, it blocks important blog content, and / or prevents clicking on crucial links.

Initial observations, during the immediately previous 2 - 3 days. referred to a "FaceBook or similar Social Networking gadget". Digging deeper, and looking closely at reported cases, we can look for the problem itself.

After repeated examination of multiple cases, we're seeing a more specific pattern, in the problem source code. Using a text browser tool, we find the following code (with gratuitous line breaks added for readability), which appears to be the kernel of the problem.

<div id="fb-root"></div><script>
(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = "//connect.facebook.net/en_US/all.js#xfbml=1";
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));
</script><br />
<div class="fb-like"
data-href="https://www.facebook.com/xxxxxxxxxxx"
data-send="false" data-show-faces="true" 
data-width="450"></div>

(Note that "xxxxxxxxxxx" will be the FaceBook user name, providing the proper addressing to the account where the "Like" transaction is targeted).

The problem appears to involve the FaceBook Like accessory. It's possible that FaceBook Support can provide a better diagnosis - but for right now, I'll simply suggest removal of the above code. In the cases where the code was installed into an empty HTML / JavaScript gadget (and with no other accessories installed there also), I'll advise removal of the gadget containing the code.

If you can identify the problem gadget in your blog, you can edit the gadget, and Remove it.

As an alternate solution, you may add CSS which will hide the boxes. Only time will tell, if this is a better alternative for many blog owners. Using the "Add CSS" wizard in the Template Designer Advanced menu, add the following:

#fb_xdm_frame_http, #fb_xdm_frame_https
{
 display:none !important;
}

Depending upon your level of technical comfort and expertise, you may elect any one of three solutions.

1. Remove the entire HTML gadget.
2. Remove the specific problem code.
3. Add CSS to hide the problem.

It's your blog, and your accessories.

Note that after you add or remove the code in question, and save the changes, you will need to clear browser cache and restart the browser, to accurately test success in resolving the problem.

>> Top

Problems With FaceBook Code Are The Responsibility Of FaceBook Support

As we add social networking accessories and gadgets to our blogs, we need to appreciate the nature of the connections, which we are adding.

Some Blogger blog owners fail to understand the relationships between the different Internet services, such as Blogger / Google, FaceBook, and Twitter.

Why do I have to solve a CAPTCHA when I post on my Wall?

and

Why does my "Share to FaceBook" wizard not let me include a snippet or thumbnail from my blog?

These are typical questions, seen recently in Blogger Help Forum: Something Is Broken. The people, asking these questions, probably do not understand that services like FaceBook are not part of Blogger or of Google.

We have been combining our Blogger blogs, and our Blogger blogs and our non Blogger web sites, for a while.

Similarly, we can combine our Blogger blog posts with our FaceBook Wall, and with our Twitter Stream. As we combine these various Google and non Google services, we need to observe the support responsibilities for these services.

The "Share to FaceBook" button, added to our blog, contains code written by FaceBook staff - and problems with the "Share to FaceBook" wizard are, generally, the responsibility of FaceBook.

Blogger / Google wants to prevent bogus and malicious Blogger blog content, and FaceBook wants to prevent bogus / malicious FaceBook Wall content. Anything that you attempt to post in FaceBook - including links to, or photos or snippets from, your Blogger blog - is subject to FaceBook security decisions. If FaceBook wants you to solve a CAPTCHA when you post, or simply blocks you from posting, that is their decision.

Blogger / Google gives some us tools from FaceBook and Twitter. Other tools are provided by third parties. We may use any tools provided, as part of our blogs - but our use of these tools is subject to actions of the people who create them.

Report a FaceBook Problem
To report a problem with FaceBook, you start from the "Gear" icon at the top right of any FaceBook display. Select "Help", "Report a Problem", and "Report a Problem" again. That gives you the "Report a Problem" wizard. This procedure, too, may change as FaceBook changes their website.

>> Top

Publicising Updates To Your Blog, Using FaceBook And Twitter

If you publish a public Blogger blog, and have a FaceBook and / or Twitter account, then you have an audience for your blog updates, waiting to read your blog posts.

Any Blogger feed (which eliminates private blogs) can automatically post, to FaceBook and / or Twitter.

Until recently, you could publish your Blogger post feed directly to your FaceBook wall.

Right now, you can use FeedBurner to publish your Blogger post feed to your Twitter feed. Alternately, using the third party TwitterFeed service, you can publish any suitable newsfeed - Blogger or other - to any of 5 online services.

• Twitter
• Statusnet
• Hellotxt
• Facebook
• Linkedin

I setup a new TwitterFeed account, today, in a single screen transaction.

Having setup my TwitterFeed account, setting up a Blogger to FeedBurner feed was similarly quick and painless.

1. I provided the URL of my Blogger post feed, unredirected.
2. In a separate window, I logged in to FaceBook, using my normal FaceBook account.
3. In the TwitterFeed window, I instructed TwitterFeed to publish to my FaceBook account.
4. In the TwitterFeed window, I instructed FaceBook to trust TwitterFeed.
5. That's it.

Now, we see when this post publishes to my FaceBook Wall.

Next, I'll get back to work publishing blog posts. And, enjoy the convenience of automated publishing to additional blog services.

Fix: Wrong Description and Image on sharing posts to Facebook

When you share a post on Facebook, it will display a thumbnail picked from the post page along with a short description of the post. But in many cases Facebook fails to  identify the correct image and description that it should use. This leads to irrelevant images and description coming up in Facebook when you or your readers share the post. This is totally annoying, and I had got many queries regarding this on our Facebook page and via email. So for those who are trying to figure a way out of this, here is the solution :)

 

Continue Reading

Publishing Your Blogger Blog Post To FaceBook Fails, With Open Refusal By FaceBook

Late last year, Blogger blog owners seeking to publicise their blog posts using their FaceBook Wall, were denied that possibility, silently. That problem was recently resolved, though still in silence.

Recently, Blogger blog owners started reporting a new symptom of problems with FaceBook.

I try to share my blog address on FaceBook, and I receive this message

The content you're trying to share includes a link that's been blocked for being spammy or unsafe:

Now what do I do?

This symptom is most likely a problem which the individual blog owners will need to discuss, with FaceBook Support.

Each Internet service has the right, and the responsibility, to block and interfere with spammy or unsafe content, on its service - to protect the legitimate users of its service.

Blogger has been blocking and interfering with spammy and unsafe content for several years - not always well received, but they are doing their best. FaceBook has the same right, and the same responsibility.

This problem appears to involve blog posts that contain pictures hosted on "2.bp.blogspot.com". I'll note that I posted, yesterday, a FaceBook Wall post referencing a Blogger blog post which contains a picture hosted on "4.bp.blogspot.com", with no problem. You can find my test post on my Wall - but you'll have to hunt for it on my FaceBook Wall, since I have not yet learned the technique to extracting and sharing, FaceBook Wall posts, outside FaceBook.

If you, a Blogger blog owner, believe that this is an unjust decision, you need to complain to FaceBook Support. FaceBook Support issues, like Blogger Support issues, are best solved with collaboration. You, and millions of other Blogger blog owners, seeking to publicise your blogs on your FaceBook Wall, can change this recent decision by FaceBook - if and only if everybody affected complains.

But you must complain to FaceBook Support. Not Blogger Support.

>> Top

The Problem, With Publishing Our Blog Posts To FaceBook, Does Not Apparently Have A Simple Cause

The problem of publishing our blog posts to FaceBook, initially observed several days ago, has generated some controversy - and much confusion, in Blogger Help Forum: Something Is Broken. Suggestions about its base cause are numerous - and variant.

• Initially and at first glance, it appeared to involved posts containing lots of pictures.
• Some folks have suggested that it involves use of the New GUI Post Editor.
• Other folks insist that it's the result of a FaceBook decision, that may have targeted Blogger as a spam host.
• Still others insist that it results from use of the Share button in the blog, vs the "Update Status" wizard in FaceBook itself.
• One blog owner gave a very interesting explanation involving FaceBook, and Open Graph.

The problem has been reported to Blogger Support - though no response, to my report, has yet been seen. My asking, a few times, whether anybody has successfully reported the problem to FaceBook Support, has either been ignored or vigourously rejected, by all involved in the arguments.

The one sure thing, that I've observed so far about this problem, is that there is not apparently one sure thing causing this problem. I've done several tests, and published a few posts into my FaceBook Wall, successfully - using both the Share button, and "Update Status". Perversely, I was able to reproduce the problem reported by one blog owner.

My immediately previous post - Choose Your Registrar, When Buying A Domain - was composed using the New GUI Post Editor, contains pictures, and was published to my Wall using "Share to Facebook", with no problem. I just published this post, using The New Blogger GUI Post Editor and "Update Status", onto my Wall. If you examine my Wall, you'll see earlier posts, composed using the Classic GUI Post Editor, also.

I will continue to keep my rollup discussion open, for reporting diagnostic details - and respectfully request that only diagnostic details be posted there. Until either Blogger Support and / or FaceBook Support take ownership of the problem, and promise a resolution, no objectively provided diagnostic detail is unnecessary. Your observations, whenever provided, could provide the final, necessary clues, and lead to the diagnosis of the problem.

If anybody would like to discuss my diagnostic efforts to date - and especially if there are any FaceBook Support personnel reading this, I have a second discussion in progress, with one helpful blog owner.

Please, be objective. Observe both the etiology of Blogger problems, and the epidemiology of forum discussions.

---

(Update 2012/01/94): It appears that most people are now able to post to FaceBook. Some people are now reporting a new annoyance

You are attempting to post a link that has been marked as abusive and/or spammy.

---

(Update 2012/01/02): Blogger Support was aware of the problem last week, tried to contact FaceBook then, and has heard nothing in return. Their analysis of the problem, made last week, is that the problem is outside their control.

---

>> Top

Publishing Your Blogger Blog Post To FaceBook Fails

During the past weekend, we started seeing a number of reports in Blogger Help Forum: Something Is Broken, from blog owners who participate in FaceBook, and who can't publish their blog posts to their FaceBook Wall. The problem appears to be common to both publishing using the "Share to FaceBook" button in the blog post (within Blogger), as well as the Wall posting wizard (within FaceBook).

We have a problem rollup in Blogger Help Forum: Something Is Broken, where we are collecting details from the blog owners reporting.

1. What's the URL of your Blogger blog?
2. What's the URL of your FaceBook Wall?
3. Were you posting from your blog post (using the "Share to Facebook" button), or directly to your Wall (within FaceBook)?
4. Is the email address associated with your Blogger account GMail, or non GMail?
5. Is the email address associated with your FaceBook account GMail, or non GMail?
6. Is the email address associated with your Blogger account the same as the email address associated with your FaceBook account?
7. Were you logged in, as the blog owner, to Blogger?
8. Were you logged in, as the Wall owner, to FaceBook?
9. What post did you try posting, to FaceBook?
10. How recently were you able to, successfully, post to FaceBook?
11. Does your Blogger account use a Blogger profile, a Google profile, or a Google+ profile?
12. If you were posting to your Wall, did you solve the CAPTCHA successfully?
13. What browser (name, and version) are you using?

If you are observing this problem, with your Blogger / FaceBook accounts, providing as many details as possible may help Blogger / FaceBook Support staff to focus on your problem, by identifying a pattern.

---

(Update 2012/01/94): It appears that most people are now able to post to FaceBook. Some people are now reporting a new annoyance

You are attempting to post a link that has been marked as abusive and/or spammy.

---

(Update 2012/01/01): After having examined the many diagnostic reports provided in the rollup discussion, and having done some testing, I am suspecting that the problem does not have a simple cause, that's solely the responsibility of Blogger. Blogger Support appears to support this conclusion.

---

>> Top

Facebook Comments For Blogger

Facebook Comments can bring better interactivity into your Blog. These comments will work like a Facebook Wall.This tutorial will help you to easily setup Facebook Commenting on your Blogger Blog.

Continue Reading

Facebook send button for Blogger

It had been some time since Facebook released their new Send Button.The Send button is a social plugin that websites can use to let people send a link to a friend through Facebook Messages, post it to a Group, or email it to an individual. Follow this tutorial to add it to your Blogger Blog.

Continue Reading