Showing posts with label Twitter. Show all posts
Showing posts with label Twitter. Show all posts
Saturday, April 7, 2018
How to Create Social Network Clone Like Twitter using PHP & MySQL
Its been along time :) , sorry for that.
Now in 2018 you can easily see that everything changes, back in a few years later most of the people not even know what blogging is. Either they don't even know how websites made eventually everything change technology grow so fast.
Making money from INTERNET it was a joke, but now it's a fact. It's all about skills in order to achieve your dream you
Friday, August 4, 2017
How to Add Cute Flying Twitter Bird to Blogger Blog?
Sunday, March 13, 2016
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.
Looking at my blog, and a FaceBook Debug log, for this post.
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.
So, what do we have?
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.
This makes the immediately previous advice unnecessary.
If one wishes to provide author information, that also becomes slightly simpler.
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.
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 -->
<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.
Saturday, March 12, 2016
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.
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.
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.
Friday, May 17, 2013
How to add Twitter Cards to Blogger
When you share a post to Facebook or Google+, they display a summary of the post and also a thumbnail if available. Twitter has also come up with a similar solution called Twitter Cards.Twitter has come up with different types of Cards and this tutorial will help you in adding a summary card to your Blogger posts. Blog Posts which have the summary card added will show a View Summary Option
Saturday, February 4, 2012
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.
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.
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.
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.
- Statusnet
- Hellotxt
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.
- I provided the URL of my Blogger post feed, unredirected.
- In a separate window, I logged in to FaceBook, using my normal FaceBook account.
- In the TwitterFeed window, I instructed TwitterFeed to publish to my FaceBook account.
- In the TwitterFeed window, I instructed FaceBook to trust TwitterFeed.
- 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.
Wednesday, August 18, 2010
How to Add Tweet Box to Blogger
It has been a long time since @Twitter released the @AnyWhere Developer Tool. AnyWhere allows you to seamlessly integrate Twitter into your site using a few lines of JavaScript. You can read more about it at @AnyWhere Developer Page. Tweet Box is one such @AnyWhere Application, which allows you to add a 140 char Tweet Box onto your blog.
Here is a screen shot of how the Tweet box appear on my Previous Post.
Continue ReadingSaturday, August 14, 2010
Tweet This - Text Link for Blogger
The Official Twitter Tweet Button has 3 default styles(2 of them with a counter and one without) . The Button works with JavaScript and is not fully Customizable.This post is for all those who want to customize, the tweet button and change it into a simple Text link. The output will be a simple HTML link with all the features if the Tweet Button(excluding the count)
Continue ReadingFriday, April 23, 2010
Blogger Commenting, And Social Networking Relationships
Every week, we see the anguish
With FaceBook, each person controls their own Wall, and their own neighbourhood. With Twitter, each person decides exactly who they wish to Follow, and sees tweets from only those folks that they follow. Neither FaceBook or Twitter encourages you to open up your neighbourhood to the world; both allow you to establish each contact, one by one, at your discretion.
With Blogger commenting, you are encouraged to allow anybody - or anybody with a required level of authentication - to comment on your blog. This encourages freedom of speech, and extends your neighbourhood far beyond the walls that you setup with FaceBook and Twitter. Some commenters, and other readers of your blogs, may later become part of your FaceBook and Twitter neighbourhoods - but at their discretion, as well as yours.
With both FaceBook and Twitter, any established account has some implied value, which is a function of the size of its neighbourhood. Nobody can use a FaceBook or Twitter account for persistent spam, because people control their own neighbourhoods. If offended, they can easily discontinue a FaceBook or Twitter contact. There is no real anonymity in either FaceBook or Twitter - each contact there is identified and validated, by its neighbourhood of contacts.
With Blogger, anybody can setup one or more Blogger accounts, for posting comments on any blog that permits comments. A Blogger account has no value, equivalent to a FaceBook or Twitter account. A Blogger account won't be identified, or validated, by its neighbourhood of contacts.
The owner of any blog has a few options, as to what level of anonymity may post comments.
Beyond those 5 choices, there is only the Blogger heuristic comment filter, which has to be persistently trained, by each blog owner. You, as the blog owner, moderate either actively or passively. You allow / disallow / tag as "spam" before publishing comments, or you delete / don't delete / tag as "spam" after comments are published. That's the choices that you have, as a blog owner.
You cannot negatively filter comments, by blocking specific individuals. If you were to add a filter for one individual, the owner of the filtered Blogger account could setup another account, and pester you from that account, with impunity. They could even use multiple different accounts, using botted computers, if they wished.
When you publish a Blogger blog and allow commenting on your Blogger blog, you open yourself to the world. For good, or for bad.
>> Top
How do I get user xxxxx blocked from commenting on my blog?because many people enjoy FaceBook and Twitter, where there is no spam, and no unwanted comments. They think that Blogger comments should be controlled, as social networking like FaceBook and Twitter are controlled.
With FaceBook, each person controls their own Wall, and their own neighbourhood. With Twitter, each person decides exactly who they wish to Follow, and sees tweets from only those folks that they follow. Neither FaceBook or Twitter encourages you to open up your neighbourhood to the world; both allow you to establish each contact, one by one, at your discretion.
With Blogger commenting, you are encouraged to allow anybody - or anybody with a required level of authentication - to comment on your blog. This encourages freedom of speech, and extends your neighbourhood far beyond the walls that you setup with FaceBook and Twitter. Some commenters, and other readers of your blogs, may later become part of your FaceBook and Twitter neighbourhoods - but at their discretion, as well as yours.
With both FaceBook and Twitter, any established account has some implied value, which is a function of the size of its neighbourhood. Nobody can use a FaceBook or Twitter account for persistent spam, because people control their own neighbourhoods. If offended, they can easily discontinue a FaceBook or Twitter contact. There is no real anonymity in either FaceBook or Twitter - each contact there is identified and validated, by its neighbourhood of contacts.
With Blogger, anybody can setup one or more Blogger accounts, for posting comments on any blog that permits comments. A Blogger account has no value, equivalent to a FaceBook or Twitter account. A Blogger account won't be identified, or validated, by its neighbourhood of contacts.
The owner of any blog has a few options, as to what level of anonymity may post comments.
Who Can Comment?
- Anyone - includes Anonymous Users
- Registered Users - includes OpenID
- Users with Google Accounts
- Only members of this blog
- (For private blogs) Only members and readers of the blog.
Beyond those 5 choices, there is only the Blogger heuristic comment filter, which has to be persistently trained, by each blog owner. You, as the blog owner, moderate either actively or passively. You allow / disallow / tag as "spam" before publishing comments, or you delete / don't delete / tag as "spam" after comments are published. That's the choices that you have, as a blog owner.
You cannot negatively filter comments, by blocking specific individuals. If you were to add a filter for one individual, the owner of the filtered Blogger account could setup another account, and pester you from that account, with impunity. They could even use multiple different accounts, using botted computers, if they wished.
When you publish a Blogger blog and allow commenting on your Blogger blog, you open yourself to the world. For good, or for bad.
>> Top
Subscribe to:
Posts (Atom)
