Category: Uncategorized

Randi Zuckerberg, an Internet entrepreneur and sister of Facebook CEO Mark Zuckerberg, discussed about the things that user must not in Facebook during a conference in Australia. According to her, if you want to be a social media champion, you must avoid bragging your accomplishments, taking pictures of food, and posting pictures of your cats.

Also on the list is posting cheesy motivational posters, humble bragging, and depressing messages saying that you’re tired or sick. Otherwise, your network won’t grow.

So what are the things that you’re not suppose to do on Facebook?

Too Much Information (TMI)

While Facebook is designed to help you socialize with other people across the Web, that doesn’t mean that you can post about the intimate conversation between you and your significant other. Another pet peeve is telling your network that your kid just achieved potty training.

Promoting a Product or Service

Facebook is a social networking website. If you want to promote a product or service, make a marketing page. Spamming your friends news feed with a sales pitch will prompt them to un-friend you.

“Vaguebooking”

Vaguebooking is a portmanteau of vague and Facebooking. Posting hanging questions such as “Will it work?” and “Is it possible?” is like a cry for help so that someone from your friends will notice you.

Unsolicited Check-ins

Almost all of your friends on Facebook don’t care where you are at the moment, especially if you’re often there within a week. More importantly, you wouldn’t want to inform your boss and your stalker (if you have one) about your weeknight rendezvous

Humble Bragging

Saying that you wish you’re not that gorgeous is like saying you’re gorgeous and your friends are not. Humbling yourself just so you won’t look like bragging would just make your friends roll their eyes.

Vanity

Creating an Album and labeling it “Me, Myself and I” is a big no-no in social media. Other than socializing, Facebook is designed to share the special events in your life—not how vain you are.

Redundant Links

Another that you must not do in Facebook is posting redundant links. Imagine how it could be an eyesore for your friends if you mention the name of the link on top of the URL on top of the link attachment.

Twitter Sync

Facebook is not Twitter. So why use @mentions and hashtags? The social media giant has a unique way of tagging or mentioning your friends, so better use it.

Phantom Tagging

If your friends are not on the photo, don’t tag them. It won’t just annoy your friends; it would also make you look like pathetic because you’re trying to call attention for someone to notice your images.

Unnecessary Name Changing

The moment you change your name on Facebook, it may be hard for your friends and family to look for you. Hence, it will prevent your from expanding your network.

 

Source: Randi Zuckerberg at World Economic Forum 2012 | Wikipedia

The post The Don’ts of Social Media appeared first on About Social Media.

Twitter took the wraps off the upcoming changes coming with their API update version 1.1. This update could have a drastic impact to third-party clients, as the micro-blogging site becomes more stringent to those that mimic Twitter.

 What Changes to Expect

As posted on Twitter’s Developer Blog, the changes in the Twitter API 1.1 are designed to “foster a consistent Twitter experience.” The changes will include universal endpoint authentication, per-endpoint rate-limiting and a handful of changes to the “Developer Rules of the Road.”

Among the changes are transforming the Display Guidelines to Display Requirements. That’s because guidelines are something that a user can choose to work with or not, while rules are rules. Of course, those who won’t adhere to the rules could result to application key revocation. This could include overlooking the proper scaling per device, as well certifying the application by Twitter before the pre-installation.

The micro-blogging site may also be looking to limit the number of users for every third-party tools. It was also stated that developers who need large number of user tokens should work directly with Twitter to acquire them.

On the other hand, they acknowledged that a number of third-party clients already have a number of users more than what Twitter requires. Due to this, the micro-blogging site added that clients who exceed to 200 percent of their current size will need to get a nod from Twitter.

Shifting Developer Activity to Overall Ecosystem

With all of these changes, Twitter hopes that it will prompt third-party developers to refocus their activity on the micro-blogging site’s overall ecosystem.

Meanwhile, response from some of the major Twitter client shows uneasy calm. The social network has been threatening to have a more stringent stance against third-party clients for a year-and-a-half now. In relation to this, many developers are already operating under the assumption that Twitter will squeeze the knot around their neck tighter.

Moreover, the impact of these changes won’t be visible to users until it takes effect. However, it could also mean a different user experience. The new API version also leaves a hanging question: Will third-party developers, especially those who have helped shape the micro-blogging site, continue to invest in the platform?

As of the moment, it’s still early to tell of what lies ahead for Twitter app developer. Furthermore, the impact of these changes to their users remains to be seen.

Twitter developers who are still on API version 1.0 will have six months to migrate to version 1.1.

 

 

Source: Twitter Logo |Wikipedia

The post Twitter’s API Update, More Stringent to Third-party Clients appeared first on About Social Media.

Twitter took the wraps off the upcoming changes coming with their API update version 1.1. This update could have a drastic impact to third-party clients, as the micro-blogging site becomes more stringent to those that mimic Twitter.

 What Changes to Expect

As posted on Twitter’s Developer Blog, the changes in the Twitter API 1.1 are designed to “foster a consistent Twitter experience.” The changes will include universal endpoint authentication, per-endpoint rate-limiting and a handful of changes to the “Developer Rules of the Road.”

Among the changes are transforming the Display Guidelines to Display Requirements. That’s because guidelines are something that a user can choose to work with or not, while rules are rules. Of course, those who won’t adhere to the rules could result to application key revocation. This could include overlooking the proper scaling per device, as well certifying the application by Twitter before the pre-installation.

The micro-blogging site may also be looking to limit the number of users for every third-party tools. It was also stated that developers who need large number of user tokens should work directly with Twitter to acquire them.

On the other hand, they acknowledged that a number of third-party clients already have a number of users more than what Twitter requires. Due to this, the micro-blogging site added that clients who exceed to 200 percent of their current size will need to get a nod from Twitter.

Shifting Developer Activity to Overall Ecosystem

With all of these changes, Twitter hopes that it will prompt third-party developers to refocus their activity on the micro-blogging site’s overall ecosystem.

Meanwhile, response from some of the major Twitter client shows uneasy calm. The social network has been threatening to have a more stringent stance against third-party clients for a year-and-a-half now. In relation to this, many developers are already operating under the assumption that Twitter will squeeze the knot around their neck tighter.

Moreover, the impact of these changes won’t be visible to users until it takes effect. However, it could also mean a different user experience. The new API version also leaves a hanging question: Will third-party developers, especially those who have helped shape the micro-blogging site, continue to invest in the platform?

As of the moment, it’s still early to tell of what lies ahead for Twitter app developer. Furthermore, the impact of these changes to their users remains to be seen.

Twitter developers who are still on API version 1.0 will have six months to migrate to version 1.1.

 

 

Source: Twitter Logo |Wikipedia

The post Twitter’s API Update, More Stringent to Third-party Clients appeared first on About Social Media.