Archive for the ‘Support’ Category

Twitter Support’s Fantastic 4

January 23rd, 2009 by Jerell | No Comments | Filed in Support

Did you know that Twitter has a team of four dedicated to the support of its users?  Its true.  They are here to help you, “solve your problems and find answers to your questions.”  Very cool.

and the fantastic four are @Caroline   @Mark   @Del   @Crystal

twittertruth twitter support

…and best of all, they want you to follow them on twitter because they want to help, and can also be reached at Welcome to Twitter Support!

Share/Save/Bookmark

Tags: ,

When to RT or not to Retweet

January 22nd, 2009 by Jerell | 11 Comments | Filed in Support, Twitter

I love to retweet (RT) great items that I see on Twitter, and sometimes I am the 3rd or 4th person to RT the item.  But this also wastes our valuable 140 character acreage, but I wanted to know if this was really necessary to give credit to the original Tweeter, or just a polite thing to do. So I looked into it. Believe it or not Twitter actually has a policy on retweeting or as they like to call it: “Reposting others’ content without attribution”.

twittertruth RT 1

Twitters rules state that:

Reposting others’ content without attribution is against the Twitter rules

Re-posting another person’s updates without giving them credit and without their permission is a violation of Twitter’s rules.  Accounts re-posting others’ updates (with or without crediting the author)  may be immediately suspended because:

  1. Re-posting others’ updates, regardless of stating authorship, is a potential form of spam
  2. Re-posting others’ updates as one’s own without giving credit to the original author is tantamount to plagiarism

If an account is aggregating or re-posting others’ updates for a legitimate reason, such as collecting and re-posting all updates with the word “dream” into @dreamtweets profile, it’s ok as long as the original author is credited for their update.

http://twitter.zendesk.com/forums/26257/entries/16205

So if I understand this policy correctly, you must give credit to the original author of the tweet, however you do not need to give credit to all of the additional people who RT it before you see it.

twittertruth RT 2

Which makes sense since we only have 140 characters to work with. So we don’t have to include RT upon RT when we RT. .. but then again, it is the polite way to tweet.  

What is your personal policy on RT’s and ReTwittering?

 

UPDATE 22 JAN 2008

Thank you to @Kristie McNealy for catching the following line:

Re-posting another person’s updates without giving them credit and without their permission is a violation of Twitter’s rules.

Does this mean You have to asker permission to RT before you RT then? Lets find out.

Share/Save/Bookmark

Tags: , ,

Is Twitter’s API Blue Sky Falling? um NO!

January 21st, 2009 by Jerell | 2 Comments | Filed in Support, Twitter

I am amazed at how much attention Twitter’s new policy changes have received today.  From the sound of it, the blue sky is falling and all of our beloved Twitter applications will not longer be working in a few days. 

But this doesn’t seem to be the case.  When you go over to the actual Twitter Development Talk, you see the following posted (with my emphasis in BOLD)

**********************************************

 

From: “Alex Payne” <a@twitter.com>
Date: Tue, 20 Jan 2009 15:48:35 -0800
Local: Tues, Jan 20 2009 4:48 pm
Subject: Putting a ceiling on requests from users and IPs on the whitelist
Up until now we’ve allowed users and IPs on our whitelist an unlimited
number of requests per hour.  When our whitelist was in the tens and
low hundreds, this made sense. Now that we have more developers on the
whitelist than we can reasonably maintain close communication with, we
need to put a ceiling on the number of requests per hour whitelisted
accounts and IPs can make.
Starting later this week we’ll be limiting those on the whitelist to
20,000 requests per hour. Yes, you read that right: twenty THOUSAND
requests per hour. According to our logs, this accounts for all but
the very largest consumers of our API. This is essentially a
preventative measure to ensure that no one API client, even a
whitelisted account or IP, can consume an inordinate amount of our
resoures.

If you run one of the services that routinely exceed 20k
requests/hour, please get in contact with us (a
@twitter.com) as soon
as possible. Chances are good that you’ll simply need to slow your
crawl rates, implement more caching on your end, and limit requests to
only active accounts. We’re happy to work with you to find solutions.


Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

**********************************************

 and as @al3x just said on his Tweet

twittertruth API 2

 

and I wanted to double check…

twittertruth API 1

 

Share/Save/Bookmark

Tags: , ,