from:"Adam"

First of all, I honestly believe that Twitter HQ values developers and
appreciates their contribution. That is why I decided to devote myself
to this area a couple of years ago. I was amazed that when a dev
reported a problem the engineer responsible replied here and tried to
solve it. That is better than any big product I know of today. That is
why you have so many developers putting in all this work.

I also believe that the last few announcements from Ryan and others
have been the worst examples of third party developer management I
have seen in 30 years in this business. I can see what Ryan wanted to
accomplish in his latest message. He wanted to provide guidance. He
ended up telling us that Twitter no longer wanted anyone to build
clients, didn't explain clearly what a client meant to him, and
pointed out that hundreds of apps that fail to meet his undefined
high bar were cut off every week. Not good. Sorry, Ryan. You are
right. You are not good at communicating with third party developers.
At least not in written form. You look like a very cool guy with a lot
of personal charm. Maybe it works better in person. You should spend
some time talking directly to developers in small groups. It might
help you develop some canned responses that work.

Here is a simple way this could have been prevented. If you had a
developer relations person with experience and skills in dealing with
third party developers, who have completely different motivations from
in-house coders, he or she could have quietly passed around a draft of
what you wanted to say. This would have gotten very strong negative
reactions. You would have been able to reformulate it to strip out the
implied threats and turn it into a positive roadmap. It could have
been framed as Here are some areas we promise to leave open for
developers. If you work here, we will give you all kinds of extra
support and promotion.

Here is another simple way this could have been prevented. Create an
advisory board of developers. Rotate people through it every 6-12
months. Let them vet announcements in advance. Let them respond to the
questions. It works in every other company I have worked with.

Here is what could be done instead of these repeated bombs you keep
dropping on the community. Give people a present. Announce that you
will use some of your precious ad space to promote third party apps,
and not just the ones with millions of dollars of VC who happen to
work in your building. Find new ways to rev share with developers.
Offer all expense paid trips to select developers to visit your office
for a day to hang out. HOLD A DEVELOPERS CONFERENCE.

There are many other things a good developer relations person could
do. Talk to Guy. That is how he started for Apple.

One last thing. Give this developer relations person a seat at the
table when big decisions are made. I can read lots of signals, like
this high bar nonsense, that there are negative attitudes inside
Twitter towards developers. They are a pain in the ass. Yes. But they
do hundreds of millions of dollars in development and promotion for
you for free. Hire someone good for $100K+. Give them a million dollar
budget to really take care of developers and run conferences and get
togethers around the world. It will pay off many times over.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Please hire a developer relations manager

Matt and Taylor do a great job of answering technical questions and being a
liason with engineers on developers behalf. That is a technical task. They
do it well.

A developer relations manager's job is to create and manage programs that
reach out to developers, make sure real docs are produced, provide business
support (ads, trips, rev share, etc.), and run small and large events that
help build a community of passionate developers around a product. It is a
completely different job from what Matt and Taylor do. I hate to use the P
word with this group, but it is really public relations aimed at developers.
it is not just business relations, because many developers aren't
businesses, but they contribute greatly to Twitter's growth. A developer
relations manager would talk to devs constantly and bring back this feedback
to be applied against future communications.

Objectively, based on the results here and in the tech press, nobody  could
claim this last communication was a success. Right? Whatever was meant and
said, it was a disaster. A developer relations manager who was given a real
budget and some say in communications would have avoided this.

On Mon, Mar 14, 2011 at 10:13 AM, Tom van der Woerdt i...@tvdw.eu wrote:

 Isn't what you are describing the task of a developer advocate, Taylor
 Singletary and Matt Harris (and others?)?

 Tom



 On 3/14/11 2:44 PM, Adam Green wrote:

 First of all, I honestly believe that Twitter HQ values developers and
 appreciates their contribution. That is why I decided to devote myself
 to this area a couple of years ago. I was amazed that when a dev
 reported a problem the engineer responsible replied here and tried to
 solve it. That is better than any big product I know of today. That is
 why you have so many developers putting in all this work.

 I also believe that the last few announcements from Ryan and others
 have been the worst examples of third party developer management I
 have seen in 30 years in this business. I can see what Ryan wanted to
 accomplish in his latest message. He wanted to provide guidance. He
 ended up telling us that Twitter no longer wanted anyone to build
 clients, didn't explain clearly what a client meant to him, and
 pointed out that hundreds of apps that fail to meet his undefined
 high bar were cut off every week. Not good. Sorry, Ryan. You are
 right. You are not good at communicating with third party developers.
 At least not in written form. You look like a very cool guy with a lot
 of personal charm. Maybe it works better in person. You should spend
 some time talking directly to developers in small groups. It might
 help you develop some canned responses that work.

 Here is a simple way this could have been prevented. If you had a
 developer relations person with experience and skills in dealing with
 third party developers, who have completely different motivations from
 in-house coders, he or she could have quietly passed around a draft of
 what you wanted to say. This would have gotten very strong negative
 reactions. You would have been able to reformulate it to strip out the
 implied threats and turn it into a positive roadmap. It could have
 been framed as Here are some areas we promise to leave open for
 developers. If you work here, we will give you all kinds of extra
 support and promotion.

 Here is another simple way this could have been prevented. Create an
 advisory board of developers. Rotate people through it every 6-12
 months. Let them vet announcements in advance. Let them respond to the
 questions. It works in every other company I have worked with.

 Here is what could be done instead of these repeated bombs you keep
 dropping on the community. Give people a present. Announce that you
 will use some of your precious ad space to promote third party apps,
 and not just the ones with millions of dollars of VC who happen to
 work in your building. Find new ways to rev share with developers.
 Offer all expense paid trips to select developers to visit your office
 for a day to hang out. HOLD A DEVELOPERS CONFERENCE.

 There are many other things a good developer relations person could
 do. Talk to Guy. That is how he started for Apple.

 One last thing. Give this developer relations person a seat at the
 table when big decisions are made. I can read lots of signals, like
 this high bar nonsense, that there are negative attitudes inside
 Twitter towards developers. They are a pain in the ass. Yes. But they
 do hundreds of millions of dollars in development and promotion for
 you for free. Hire someone good for $100K+. Give them a million dollar
 budget to really take care of developers and run conferences and get
 togethers around the world. It will pay off many times over.


 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership

Re: [twitter-dev] Re: consistency and ecosystem opportunities

But you will allow it, right? Even if it is thinking small, it will not be
blocked? That is our problem. We can't separate business advice from a
warning to prepare to be cut off. We can't help watching the hand that holds
the kill switch. It makes it hard to hear what you say. Have patience, and
keep explaining please. If something will not cause a ban, then say this
explicitly to us. Don't just think it was implied.

On Mon, Mar 14, 2011 at 11:20 AM, Raffi Krikorian ra...@twitter.com wrote:

 my statement here was not providing small on the size of the company, but
 rather, small on the size of the idea. to re-iterate, making a piece of
 software that simply renders home_timeline is thinking too small.


 On Sun, Mar 13, 2011 at 6:21 PM, Lil Peck lilp...@gmail.com wrote:

 On Sun, Mar 13, 2011 at 7:45 PM, @siculars sicul...@gmail.com wrote:
  @raffi @rsarver, I wrote up my two cents earlier,
  http://siculars.posterous.com/twitter-monoculture. I just don't
  appreciate the direction you all are going in. @raffi, I spoke with
  you at the CU recruiting event a few weeks back and I got to tell you
  that if I were asked I would tell those kids to reconsider working at
  twitter and possibly consider a Twitter competitor. you say building
  clients is ... Thinking too small I would say your policy change is
  thinking small and alienating your ardent supporters.
 

 To which I would add, what is Twitter to arbitrate that which is and
 is not too small? Has Twitter subscribed to the fallacious bigger
 is always better philosophy?

 How small is too small?

 Less than $25 million in startup funds?

 OR

 One creative, fun loving person and their sweat equity?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




 --
 Raffi Krikorian
 Twitter, Application Services
 http://twitter.com/raffi


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Please hire a developer relations manager

I've been getting emails saying that this message was a request to replace
Ryan. That was not my intent. I am suggesting that he be given someone to
help with developer communications. His job title implies that he does much
beside sending out these cheery notes to developers. He should have a
full-time person to do this and much else to improve developer relations
instead.

If this was seen as an attack on Ryan, I apologize. I recognize the irony of
my critique of his message as an attack on us being seen as an attack on
him. It was meant to be a suggestion for a better way to work together.


On Mon, Mar 14, 2011 at 9:44 AM, Adam Green 140...@gmail.com wrote:

 First of all, I honestly believe that Twitter HQ values developers and
 appreciates their contribution. That is why I decided to devote myself
 to this area a couple of years ago. I was amazed that when a dev
 reported a problem the engineer responsible replied here and tried to
 solve it. That is better than any big product I know of today. That is
 why you have so many developers putting in all this work.

 I also believe that the last few announcements from Ryan and others
 have been the worst examples of third party developer management I
 have seen in 30 years in this business. I can see what Ryan wanted to
 accomplish in his latest message. He wanted to provide guidance. He
 ended up telling us that Twitter no longer wanted anyone to build
 clients, didn't explain clearly what a client meant to him, and
 pointed out that hundreds of apps that fail to meet his undefined
 high bar were cut off every week. Not good. Sorry, Ryan. You are
 right. You are not good at communicating with third party developers.
 At least not in written form. You look like a very cool guy with a lot
 of personal charm. Maybe it works better in person. You should spend
 some time talking directly to developers in small groups. It might
 help you develop some canned responses that work.

 Here is a simple way this could have been prevented. If you had a
 developer relations person with experience and skills in dealing with
 third party developers, who have completely different motivations from
 in-house coders, he or she could have quietly passed around a draft of
 what you wanted to say. This would have gotten very strong negative
 reactions. You would have been able to reformulate it to strip out the
 implied threats and turn it into a positive roadmap. It could have
 been framed as Here are some areas we promise to leave open for
 developers. If you work here, we will give you all kinds of extra
 support and promotion.

 Here is another simple way this could have been prevented. Create an
 advisory board of developers. Rotate people through it every 6-12
 months. Let them vet announcements in advance. Let them respond to the
 questions. It works in every other company I have worked with.

 Here is what could be done instead of these repeated bombs you keep
 dropping on the community. Give people a present. Announce that you
 will use some of your precious ad space to promote third party apps,
 and not just the ones with millions of dollars of VC who happen to
 work in your building. Find new ways to rev share with developers.
 Offer all expense paid trips to select developers to visit your office
 for a day to hang out. HOLD A DEVELOPERS CONFERENCE.

 There are many other things a good developer relations person could
 do. Talk to Guy. That is how he started for Apple.

 One last thing. Give this developer relations person a seat at the
 table when big decisions are made. I can read lots of signals, like
 this high bar nonsense, that there are negative attitudes inside
 Twitter towards developers. They are a pain in the ass. Yes. But they
 do hundreds of millions of dollars in development and promotion for
 you for free. Hire someone good for $100K+. Give them a million dollar
 budget to really take care of developers and run conferences and get
 togethers around the world. It will pay off many times over.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

2011-03-13 Thread Adam Green

Yes! Transparency!  That is what we are really craving. That is the subtext
for every developer responding to this thread. What we all want is
transparency about being shut down. Why does Twitter revoke literally
hundreds of API tokens / apps a week as Ryan said? Is it for something
obvious, like pumping out thousand of spam tweets or abusive follows, or is
it for something innocent, like not putting the right text on a tweet
button? I have never seen a description of an app that was blocked, except
for a few loons like Edward H. What if you told us about apps that get
blocked as examples, and explain what they did wrong? You don't even have to
identify them by name. Just explain exactly what type of transgressions are
causing rejection. That could calm people down.

Who doesn't meet the high bar and why? I know high bar has a lot of
meaning to you Twitter guys, since you all use the same term (a real example
of groupthink, BTW), but it means nothing to us. Tell us where this high bar
is exactly, by showing examples of not reaching it. Then we can learn and
improve, rather than guessing at what you mean.

Nobody here would bitch and moan if they didn't really want to learn
something. Please, help us by giving us examples.

On Mon, Mar 14, 2011 at 12:07 AM, Matt Harris mhar...@twitter.com wrote:

 Innovation and development with the APIs are not being prevented. There
 have always been guidelines, and rules of the road so we all know what is
 and isn't allowed.

 If you build a client you are touching the majority of Twitter features.
 The APIs allow you to do this, and Twitter and your users trust you to use
 them in the way the terms or service allow. The high bar covers your use of
 these methods, and how you present information back to the user. The ToS
 covers this but there are always situations where the application of them
 isn't clear. — Let's have those discussions with your use cases applied for
 the benefit of everyone.

 The direction, and motivation here is transparency. You asked us what it
 looks like from the inside out. It can be uncomfortable, sure, but I believe
 it's better we all know how it looks on both sides.

 Without us saying how we see it, how can we have these discussions?

 @themattharris


 On Mar 13, 2011, at 20:21, Lil Peck lilp...@gmail.com wrote:

  On Sun, Mar 13, 2011 at 7:45 PM, @siculars sicul...@gmail.com wrote:
  @raffi @rsarver, I wrote up my two cents earlier,
  http://siculars.posterous.com/twitter-monoculture. I just don't
  appreciate the direction you all are going in. @raffi, I spoke with
  you at the CU recruiting event a few weeks back and I got to tell you
  that if I were asked I would tell those kids to reconsider working at
  twitter and possibly consider a Twitter competitor. you say building
  clients is ... Thinking too small I would say your policy change is
  thinking small and alienating your ardent supporters.
 
 
  To which I would add, what is Twitter to arbitrate that which is and
  is not too small? Has Twitter subscribed to the fallacious bigger
  is always better philosophy?
 
  How small is too small?
 
  Less than $25 million in startup funds?
 
  OR
 
  One creative, fun loving person and their sweat equity?
 
  --
  Twitter developer documentation and resources:
 http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

Interesting that neither Ryan or anyone else from Twitter has replied once
to any of the questions here, (way to go on showing your interest in the
developer community, Ryan),  so I'll address this question to everyone else
in the group. I don't read Ryan's message as demanding that apps are no
longer allowed to send tweets on behalf of users. Is that supposed to be
what he said? I think he is saying that apps should be more than *just*
clients that let you read and post tweets. How to tell the difference, I
have no idea, but I think in Ryan's mind there is a difference.

I'll ask it as clearly as I can. Is it still allowed for an app to accept a
tweet from a user and post it into their account?

Is the /statuses/update api call still allowed in an app?

Let's not wait for Twitter to respond, since they clearly don't want to any
longer. Let's try and figure this out ourselves. What does everyone think?
Can apps still send tweets?

If yes, there is still a market for Twitter API developers. If not, the
Twitter API is over. It is that simple.

Maybe Ryan or anyone from Twitter can also find the time to answer this.

On Sat, Mar 12, 2011 at 6:45 PM, Duane Roelands duane.roela...@gmail.comwrote:

 Wow.  Thanks for getting so many people interested in Twitter.  Now
 get lost.

 This is appalling.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] consistency and ecosystem opportunities

I agree, Scott. Ryan didn't say you can't post tweets, but everyone heard
that. Every tech blog repeated it. Ryan should take a minute and explain
that it isn't true. That much would help a lot. He led by saying don't build
a client. That is where people stopped reading.

I don't think he meant to tell people that apps can't tweet, but he did give
that impression. Now he should come back and say, Sorry guys. I gave you
the wrong impression. Here are specifically the things you can still do.
Don't just point to companies with $10M in VC funds each and say No
problem, just be like them.

These are API developers. Say it in terms of the API. Exactly which API
calls are still allowed. If he says statuses/update is still allowed, then
that answers the question. There is no ambiguity.

As for Twitter being free. Yes. The API is, but denying the value that
products like Tweetdeck gave Twitter *for free* is denying the reality of
how Twitter got to where it is. It is called a partnership. They give us raw
materials, we add value to them. We all benefit.

On Sat, Mar 12, 2011 at 7:28 PM, Scott Wilcox sc...@dor.ky wrote:

 Hello,

 For a few days now I've read what people have said in reply to the update
 from Ryan. There are some crazy reactions and responses to what Ryan has
 said. In essence, the entire reaction is my opinion is completely overblown.

 Not in any sense what-so-ever have Twitter said that you can no longer post
 updates on behalf of users. Its ludicrous to suggest so. What they have have
 said (and in my opinion - quite clearly) is that it is better to direct your
 time and effort into a product that is not just a simple client and does
 more than just provide viewing and posting of tweets. There are so many
 half-arsed clients out there that do little more than just show and post
 tweets. If by chance a user was to use these low grade applications as their
 first experience of Twitter, it would probably put them off using it in the
 long term.

 I do fully believe that is why they have released their own branded clients
 for iOS, Macs and other devices. It provides a consistent experience for the
 end-users.

 The other thing that people seem to completely overlook is that Twitter are
 providing a freely accessible API at no charge to developers. It pains me to
 see so many developers standing the moral high ground. If you were paying
 for access to a service or product and it changes, you have a very valid
 reason to complain. To complain about a service provided free of charge for
 you to use at the end of the day frustrates me to no end. No single
 developer has a god given right to have access to the API, perhaps that
 should be remembered.

 Scott.

 On 13 Mar 2011, at 00:16, Adam Green wrote:

 Interesting that neither Ryan or anyone else from Twitter has replied once
 to any of the questions here, (way to go on showing your interest in the
 developer community, Ryan),  so I'll address this question to everyone else
 in the group. I don't read Ryan's message as demanding that apps are no
 longer allowed to send tweets on behalf of users. Is that supposed to be
 what he said? I think he is saying that apps should be more than *just*
 clients that let you read and post tweets. How to tell the difference, I
 have no idea, but I think in Ryan's mind there is a difference.

 I'll ask it as clearly as I can. Is it still allowed for an app to accept a
 tweet from a user and post it into their account?

 Is the /statuses/update api call still allowed in an app?

 Let's not wait for Twitter to respond, since they clearly don't want to any
 longer. Let's try and figure this out ourselves. What does everyone think?
 Can apps still send tweets?

 If yes, there is still a market for Twitter API developers. If not, the
 Twitter API is over. It is that simple.

 Maybe Ryan or anyone from Twitter can also find the time to answer this.

 On Sat, Mar 12, 2011 at 6:45 PM, Duane Roelands 
 duane.roela...@gmail.comwrote:

 Wow.  Thanks for getting so many people interested in Twitter.  Now
 get lost.

 This is appalling.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




 --
 Adam Green
 Twitter API Consultant and Trainer
 http://140dev.com
 @140dev

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p

Re: [twitter-dev] Re: consistency and ecosystem opportunities

Thanks, Ryan. That helps a lot, and we should all repeat that to anyone who
asks or says otherwise. So we have one answer. Tweeting in apps is still
good.

Now, can you explain what you mean by  It's apps that render a user their
timeline. Please answer this. Is displaying a list of tweets forbidden or
allowed?

If yes, is displaying a list of tweets *and* also providing functionality
that lets the user post their own tweets allowed in the same app?

That is really all we need to know.

I won't ask you to explain why this isn't a client. :)



On Sat, Mar 12, 2011 at 7:47 PM, Ryan Sarver rsar...@twitter.com wrote:

 Mike, a client is one that recreates the twitter experience, or in your
 words the primary experience. So I don't consider Instagram or Foursquare
 in that group. It's apps that render a user their timeline.

 Apps that post into Twitter are great and explicitly called out at the
 bottom of the email.

 Hope that helps clarify.

 Best, Ryan
 --
 Ryan Sarver
 @rsarver http://twitter.com/rsarver



 On Fri, Mar 11, 2011 at 9:09 PM, Mike Champion mike.champ...@gmail.comwrote:

 Thanks for the clarification Ryan. Two questions:

 1) Do you have a clear definition of what counts as a Twitter client?
 Is it any app/service that posts updates to Twitter, including apps
 like twitterfeed and Instapaper? Or is it only those apps that are
 primarily clients? I'm certainly familiar with the challenge of
 classifying apps ;) but wanted to know who will be covered by the ToS
 Section 1.5 and how you think about clients given Twitter's updated
 stance.

 2) In section 1.5.A of the ToS it says:

 Your Client must use the Twitter API as the sole source for features
 that are substantially similar to functionality offered by Twitter.
 Some examples include trending topics, who to follow, and suggested
 user lists.

 Is the Who to follow functionality available via API from Twitter
 for clients that want to offer this? I wasn't aware that it been
 released as API but may have missed it on dev.twitter.com.

 Thanks,

 -mike

 On Mar 11, 3:47 pm, Eric Mill kproject...@gmail.com wrote:
  More specifically, developers ask us if they should build client apps
 that
  mimic or reproduce the mainstream Twitter consumer client experience.
  The
  answer is no.
 
  We need to ensure users can interact with Twitter the same way
 everywhere.
 
  I'm not sure you can say these things and simultaneously try to say you
 have
  a welcoming developer environment. All third party Twitter developers,
 no
  matter what they make, are now walking on eggshells, constantly at risk
 of
  offending Twitter's ideas of how users should interact with Twitter.
 
  You may feel you need this consistency, but you don't. You want it,
 and
  are willing to make tradeoffs to get it. I just hope you realize how big
  those tradeoffs are, and how chilling it is for Twitter to decide that
 only
  certain kinds of innovation on the Twitter API are welcome.
 
  -- Eric

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] consistency and ecosystem opportunities

They should insert ads into the stream, and say we can't remove them. That
would be great. I have no problem with that, providing they treat us with
respect. Give us an appeal process with warning if they don't like what we
build. I have no problem with them wanting to make money from things I
build. I want to make money from things they give me. I want everyone to
make money.

Developers are not the problem. They are the solution. I can't help thinking
there are people at high levels who sit around saying How do we shake off
these damned parasites? If I'm wrong, maybe we can see a message from
management that says Here is a new initiative or dev program that will help
you make money with the API. We love what you guys do so much we want to
reward you. We want you to be part of a partnership.

That would be refreshing.

On Sat, Mar 12, 2011 at 7:59 PM, Ellsass cpa...@gmail.com wrote:

 Scott, I don't think it's ludicrous to think that Twitter may
 eventually pull the plug on, say, statuses/home_timeline, effectively
 eliminating clients.

 If Twitter's concern is ad revenue, all they'd need to do is add a
 clause to their TOS specifying that all third-party clients must show
 in-line ads or the quickbar or whatever else Twitter uses to generate
 revenue. Then the issue is very clear for developers -- either
 integrate Twitter's revenue-producing content into your client, or
 don't make a client at all.

 The fact that they seem to be going about this a different way, and
 being a bit unclear as to what might happen to a client-only app,
 leaves open the possibility that they simply want to close down the
 market so the only access to one's timeline is via a first-party app.



 Scott Wilcox wrote:
  Hello,
 
  For a few days now I've read what people have said in reply to the update
 from Ryan. There are some crazy reactions and responses to what Ryan has
 said. In essence, the entire reaction is my opinion is completely overblown.
 
  Not in any sense what-so-ever have Twitter said that you can no longer
 post updates on behalf of users. Its ludicrous to suggest so. What they have
 have said (and in my opinion - quite clearly) is that it is better to direct
 your time and effort into a product that is not just a simple client and
 does more than just provide viewing and posting of tweets. There are so many
 half-arsed clients out there that do little more than just show and post
 tweets. If by chance a user was to use these low grade applications as their
 first experience of Twitter, it would probably put them off using it in the
 long term.
 
  I do fully believe that is why they have released their own branded
 clients for iOS, Macs and other devices. It provides a consistent experience
 for the end-users.
 
  The other thing that people seem to completely overlook is that Twitter
 are providing a freely accessible API at no charge to developers. It pains
 me to see so many developers standing the moral high ground. If you were
 paying for access to a service or product and it changes, you have a very
 valid reason to complain. To complain about a service provided free of
 charge for you to use at the end of the day frustrates me to no end. No
 single developer has a god given right to have access to the API, perhaps
 that should be remembered.
 
  Scott.
 
  On 13 Mar 2011, at 00:16, Adam Green wrote:
 
   Interesting that neither Ryan or anyone else from Twitter has replied
 once to any of the questions here, (way to go on showing your interest in
 the developer community, Ryan),  so I'll address this question to everyone
 else in the group. I don't read Ryan's message as demanding that apps are no
 longer allowed to send tweets on behalf of users. Is that supposed to be
 what he said? I think he is saying that apps should be more than *just*
 clients that let you read and post tweets. How to tell the difference, I
 have no idea, but I think in Ryan's mind there is a difference.
  
   I'll ask it as clearly as I can. Is it still allowed for an app to
 accept a tweet from a user and post it into their account?
  
   Is the /statuses/update api call still allowed in an app?
  
   Let's not wait for Twitter to respond, since they clearly don't want to
 any longer. Let's try and figure this out ourselves. What does everyone
 think? Can apps still send tweets?
  
   If yes, there is still a market for Twitter API developers. If not, the
 Twitter API is over. It is that simple.
  
   Maybe Ryan or anyone from Twitter can also find the time to answer
 this.
  
   On Sat, Mar 12, 2011 at 6:45 PM, Duane Roelands 
 duane.roela...@gmail.com wrote:
   Wow.  Thanks for getting so many people interested in Twitter.  Now
   get lost.
  
   This is appalling.
  
   --
   Twitter developer documentation and resources:
 http://dev.twitter.com/doc
   API updates via Twitter: http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
   Change your membership

Re: [twitter-dev] Re: consistency and ecosystem opportunities

Raffi, do you really think a statement that insisted that all developers
make sure that every single app presents tweets in exactly the same way, and
that reminded those developers that Twitter shuts down hundreds of apps a
day that fail to conform to the required presentation style, and that
pointed to a TOS that went from 30 days warning to instant shutdown without
any warning, would be read as Twitter urging everyone to innovate?

On Sat, Mar 12, 2011 at 9:39 PM, Raffi Krikorian ra...@twitter.com wrote:

 in reading your blog post, i think you're misunderstanding what 
 @*rsarver*wrote.

 the API is open -- i personally love seeing all the innovation around
 getting content into twitter (/1/status/update).  there is a cafe in
 france who's oven tweets whenever its done baking.  that uses the platform
 to get content in there.  there was a NYU project that enabled your plants
 to tweet when they needed water.  that uses the platform to get content into
 twitter.   then there are people who match tweets to context.  seeing
 twitter in action with a television show, or a newspaper article, or a
 conference, or a band -- that's how people really understand and get
 twitter.  they see it through the lens of what's happening in the world.

 what @*rsarver* said, effectively, was building a business around 
 *simply*rendering
 /1/statuses/home_timeline was probably-not-the-best-thing-to-do.  please
 go still innovate.  just don't bet money on simply making an API call to
 grabbing a user's home_timeline and rendering it.  that's thinking too
 small, and @*rsarver* is telling you that.

 On Sat, Mar 12, 2011 at 4:29 PM, Shannon Whitley 
 shannon.whit...@gmail.com wrote:

 I was hoping that Ryan was just a few weeks early for his April Fools'
 post.

 Don't build clients?  It sounds like a bad joke.

 I wrote a letter to Ryan on my blog in response to this post:


 http://www.voiceoftech.com/swhitley/index.php/2011/03/a-letter-to-ryan-sarver/

 I know you guys can't be serious about this.  Stage a mutiny if you
 have to, but don't let this boneheaded decision stand.


 --
 Raffi Krikorian
 Twitter, Application Services
 http://twitter.com/raffi


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: consistency and ecosystem opportunities

Can we get a definition of client? This seems to be where we are talking
across each other.

1.  Twitter HQ sees a client as an app that displays *only* a user's home
time line and allows the user to tweet, retweet, follow, etc.

2.  Developers see a client as an app that displays tweets from any source,
including the home timeline *and* those that are curated by editors and
algorithms, and allows the user to tweet, retweet, follow, etc.

I think to Twitter HQ, these are two very different things. I believe that
this is what Ryan was trying to say. I believe that Ryan was trying to say,
don't build apps that *only* do 1. You will have more luck with 2.
Developers heard don't build apps that do 2 or you will be instantly shut
down.

If Ryan hadn't combined his message with things that inadvertently also were
perceived as a threat of instant shutdown as a result of an innocent
misunderstanding of the rules, his statement would have been taken as
advice, rather than a threat. I believe he meant well. He failed. He should
keep trying until everyone understands. That is his job. Or it should at
least be someone's job. Collectively the developers are worth the effort.

Hey, why not hold a conference, put everyone together, and talk until this
is clear? You can afford it. We all need it.

Your future IPO investors aren't stupid. Well, at least not all of them. It
is not just your revenue numbers they will see. It is lots of either happy
or unhappy developers. We will raise your valuation. Keep saying that to
Dick and the Board. They need to understand that.

On Sat, Mar 12, 2011 at 10:26 PM, Raffi Krikorian ra...@twitter.com wrote:

 is the twitter client what's the most useful thing there?  i would think
 the algorithms and system to match tweets to that content is the most
 fruitful place for entrepreneurship?


 On Sat, Mar 12, 2011 at 7:22 PM, Shannon Whitley 
 shannon.whit...@gmail.com wrote:

 Thanks, Raffi, but obviously I'm not the only one reaching these
 conclusions.  If our interpretation is incorrect, then the policy
 isn't clear.

 Television shows, newspaper articles, and band pages are perfect
 examples of places where a Twitter client might be useful.  I could
 build a full-featured Twitter client around a single news site and
 that might be the perfect solution for that set of users.  Under the
 new guidelines, it sounds like I'd be shutdown.


 On Mar 12, 6:39 pm, Raffi Krikorian ra...@twitter.com wrote:
  in reading your blog post, i think you're misunderstanding what
  @*rsarver*wrote.
 
  the API is open -- i personally love seeing all the innovation around
  getting content into twitter (/1/status/update).  there is a cafe in
 france
  who's oven tweets whenever its done baking.  that uses the platform to
 get
  content in there.  there was a NYU project that enabled your plants to
 tweet
  when they needed water.  that uses the platform to get content into
 twitter.
then there are people who match tweets to context.  seeing twitter in
  action with a television show, or a newspaper article, or a conference,
 or a
  band -- that's how people really understand and get twitter.  they see
 it
  through the lens of what's happening in the world.
 
  what @*rsarver* said, effectively, was building a business around
  *simply*rendering
  /1/statuses/home_timeline was probably-not-the-best-thing-to-do.  please
 go
  still innovate.  just don't bet money on simply making an API call to
  grabbing a user's home_timeline and rendering it.  that's thinking too
  small, and @*rsarver* is telling you that.
 
  On Sat, Mar 12, 2011 at 4:29 PM, Shannon Whitley
  shannon.whit...@gmail.comwrote:
 
   I was hoping that Ryan was just a few weeks early for his April Fools'
   post.
 
   Don't build clients?  It sounds like a bad joke.
 
   I wrote a letter to Ryan on my blog in response to this post:
 
  http://www.voiceoftech.com/swhitley/index.php/2011/03/a-letter-to-rya.
 ..
 
   I know you guys can't be serious about this.  Stage a mutiny if you
   have to, but don't let this boneheaded decision stand.
 
  --
  Raffi Krikorian
  Twitter, Application Serviceshttp://twitter.com/raffi

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




 --
 Raffi Krikorian
 Twitter, Application Services
 http://twitter.com/raffi


  --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation

[twitter-dev] Re: Twitter OAuth 401 Unauthorized

2011-03-11 Thread Adam Duke

This code helped me understand the OAuth flow and it written in PHP
with no libraries. https://github.com/joechung/oauth_twitter
See the authors blog post about it here 
http://nullinfo.wordpress.com/oauth-twitter/

On Mar 10, 5:55 am, Tudor Claudiu Florea
tudor.claudiu.flo...@gmail.com wrote:
 Hello,
 I am trying to build an application for twitter and in order to do
 that i need to build functions that post all requests to twitter only
 with pure PHP. no OAuth libraries or other user build libraries.

 problem is i always get the 401 unauthorized header.
 I have done twitter tutorial about this with theyr values(keys) and
 got same signature base and signature and everything else but when i
 input my data(secret key and stuff) all i get is 401 unauthorized

 This is a sample of my sent/received headers

 POST /oauth/request_token HTTP/1.1
 Host:api.twitter.com:443
 Content-Type: application/x-www-form-urlencoded
 Authorization:OAuth oauth_callback=http%3A%2F%2Fadme.ro
 %2Ftwitter_request.php,oauth_consumer_key=xxx..xxx,oauth_nonce=12997527 
 12,oauth_signature_method=HMAC-
 SHA1,oauth_timestamp=1299752712,oauth_version=1.0,signature=Mv2IRkcgC 
 p3BNocBKFq8FJNN1OE
 %3D

 HTTP/1.1 401 Unauthorized
 Date: Thu, 10 Mar 2011 10:25:18 GMT
 Server: hi
 Status: 401 Unauthorized
 X-Transaction: 1299752718-94070-29343
 Last-Modified: Thu, 10 Mar 2011 10:25:18 GMT
 X-Runtime: 0.00653
 Content-Type: text/html; charset=utf-8
 Content-Length: 44
 Pragma: no-cache
 X-Revision: DEV
 Expires: Tue, 31 Mar 1981 05:00:00 GMT
 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
 check=0
 Set-Cookie: k=93.114.42.59.1299752718223070; path=/; expires=Thu, 17-
 Mar-11 10:25:18 GMT; domain=.twitter.com
 Set-Cookie: guest_id=129975271823092185; path=/; expires=Sat, 09 Apr
 2011 10:25:18 GMT
 Set-Cookie:
 _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCJePTJ8uAToHaWQiJTYwOGViZTRmYjYzY2Rm
 %250AYTI5NjM3NDRmZTNkODIwODg3IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy
 %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--
 c237f0c52f06bd5e58f547db67136857e092fa2f; domain=.twitter.com; path=/;
 HttpOnly
 Vary: Accept-Encoding
 Connection: close

 Failed to validate oauth signature and token

 Can someone help me with this? i ran out of ideeas ...

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: wait time for Site Streams whitelist ?

2011-03-02 Thread Adam Green

There are lots of ways to create website apps without using site
streams. If you describe the type of things you want to do here, you
will get plenty of advice. You don't have to reveal any secret plans.
Just describe the type of data you need from Twitter and the type of
changes you need to make to user accounts.

On Wed, Mar 2, 2011 at 10:37 AM, hank777 hank...@gmail.com wrote:
 I just registered for site streams this morning because I did not
 realize that this was the only authorized way of building a website
 that uses twitter. We are trying to demo something at SXSW, and launch
 a few weeks after, and I am wondering if I cant use the other APIs
 because of rate limits or connection limits, and I cant use site
 streams because you are not accepting new developers, how do we move
 forward, or does this really mean no one should be developing new web
 site based applications right now if they are not in the beta program?

 Thanks,
 Hank

 On Feb 1, 10:36 am, Taylor Singletary taylorsinglet...@twitter.com
 wrote:
 We still have a number of tasks to accomplish before we can move to the next
 stage of the beta. Pending applications will be reviewed once they are
 actionable.

 Thanks for your patience.

 Taylor







 On Mon, Jan 31, 2011 at 7:20 PM, Jan Paricka jpari...@gmail.com wrote:
  Weeks upon weeks upon weeks.  No joking.

  Jan

  On Tue, Feb 1, 2011 at 4:14 AM, paloalto sungh...@gmail.com wrote:

  How long does it take to get whitelisted for Site Streams API?
  I submitted a form to be whitelisted and have not received any
  confirmation e-mail.
  I am in the dark with no clue as to how long I should expect to wait.

  Sungho

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

   --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limit

2011-02-28 Thread Adam Green

If you are logging every tag ever found in your search results, and
then trying to search for them continuously, you need to change your
model. Twitter will no longer allow that type of access. They have
made this clear through words and actions. You should focus on
tracking the tags that are used most often. It is a power curve. In
every set of words I have studied, 100-200 tags get 80% of the
traffic. Streaming allows you to track 400 words. Limit yourself to
400 of the most used tags. Any other expectation is unreasonable.

On Mon, Feb 28, 2011 at 12:43 AM, manaf pm manaf...@gmail.com wrote:
 I have a website which grabs tweets from twitter.com within 20 minutes
 interval per day. I h ave stored thousands of hashtags in my database
 and search is occurring against these hash tags and user names. Right
 now there I need around 65000 search requests to be happened per day.
 Here comes the rate limit problem. As a result I am not getting
 desired search results for a long time. How can I over come this? Any
 replies are welcome and will be helpful to me.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Rate limiting for streaming API

2011-02-19 Thread Adam Green

On Sat, Feb 19, 2011 at 7:52 AM, Tom van der Woerdt i...@tvdw.eu wrote:
 On 2/19/11 1:49 PM, Paresh Nakhe wrote:

 Hi,
  From what i understand, there is no concept of rate limiting for
 streaming api. Actually it does make sense because if anyone is to use
 'statuses/sample' method (say) the limit will soon be crossed.  We are
 working on something that will heavily use the streaming api, so if rate
 limiting is imposed in future it could create some problems.  Are there
 any chances of such a restriction being imposed?

 There's no limit on the amount of tweets you can receive, but there's a
 limit on the amount of searches you can do, and the amount of connections
 you can have open.

Responses here from Twitter staff and notes in the docs say that the
sample (default) level of delivery is limited to 1% of all tweets. As
long as your total flow is less than 1% of the firehose (all tweets)
you are supposed to receive every tweet that matches your search
terms. From my experience, you only receive about 95% of the tweets
that match a set of search terms. I've never used a set of search
terms that delivered anywhere near 1% of the total flow.

Here are some numbers:
- The total flow of all tweets is in the order of magnitude of
100,000,000 per day.
- The sample stream should thus receive up to 1,000,000 tweets per day.
- When I collect tweets based on search words that deliver about
10,000 tweets a day, I don't receive about 5% of the tweets that do
match these terms.

If getting *every* tweet that matches these terms is essential, I
recommend combining streaming with backfilling. By backfilling I mean
using the search API or timeline calls in the REST API to collect
tweets that may have been missed by the streaming API. The result is
real-time delivery of 95% of the tweets you need and eventual delivery
of the remainder.

Don't bother asking about future restrictions. That question will not
be answered by Twitter HQ.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Streaming API vs. Search API: no API returns 95% of intented tweets

2011-02-15 Thread Adam Green

I don't get that big a discrepancy, but I do get different results
from search and streaming. I use streaming for real-time delivery, and
then either search or user timelines to backfill missing tweets. As
long as the flow makes this possible within rate limits this gets me
the greatest number of results, but still not 100%. I accept that 100%
ain't gonna happen. You should get within your desired 95% though.
That is a realistic goal.

On Tue, Feb 15, 2011 at 6:36 AM, Karussell tableyourt...@googlemail.com wrote:
Hi,

this problem was already posted to the twitter4j mailing list [1]. Not
sure if it is an issue with my code, twitter4j or an API issue... user
reported similar problems in the past [2].

First:

I'm doing a 100 tweet search (without paging) every 5 minutes e.g.
against 'twitter search'. I get a set of tweets A - excluding the
duplicates, of course. I get approx 5 new tweets for every 5 minutes,
so 100 tweets as pageSize should be perfectly sufficient to get all
tweets.

Second:
When I'm doing a streaming filter request for the same terms 'twitter
search' then I'm getting a set of tweets B.

The problem is: combining A and B ('C=A v B') gives me a set C where
the count of C is more than 10% larger then A or B, which means that
neither with search nor streaming API I can catch a nearly complete
set of tweets.

E.g. doing this for 3 hours I'm getting 254 tweets (A) for the search
and 257 tweets (B) for the streaming but the combined set C has 337
tweets!

Is this a bug in my code or could this be an API issue?

BTW: I don't assume 100% correctness, I only want something above
90% :) especially for such relatively infrequent terms, where users
can, should and have noticed it.

Regards,
Peter.

[1]
http://groups.google.com/group/twitter4j/msg/d959e6257ceb452f

[2]
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/71ab5cc666113c9e

http://blog.tweetsmarter.com/twitter-downtime/twitters-dirty-secret-they-dont-show-you-all-tweets/

http://jetwick.com Twitter Search without Noise

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk

--
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

[twitter-dev] Freedom's just another word for nothing left to lose

The behavior on this group has changed significantly since Ryan
finally admitted that Whitelisting no longer exists. I've never seen
anyone discuss methods of getting around TOS before, well there was
Edward H., and we saw what happened to him. Now there are free flowing
discussions of MTurk and other tricks to go way beyond the rate
limits. I think this is great. Frankly, Twitter has done a good job of
offering free resources to devs, which I thank them for, but there was
way too much fear before. Now there are no extra benefits that can be
given and withdrawn on a case by case basis. Boy do I hate that
phrase. Of course, they can ban people from this list, but maybe the
irony of Twitter blocking free speech on their own forum may restrain
that urge in the future.

Personally, I've treated Whitelisting like Social Security. It ain't
going to be there when I need it. That has turned out to be a winning
strategy. I don't really violate TOS, since I'm not as spammer, but I
have never tried building anything that would fail if Twitter didn't
give me Whitelisting after it got into production, which BTW was the
most disrespectful thing I've seen from a platform vendor. Everyone
should assume that you need to use what is there by default, and
always be ready with a workaround if that gets taken away. My gut
tells me that things will get worse before they get better. Twitter HQ
will be under huge pressure to make money before the IPO, and we are
likely to get some of the cuts. The inevitable they are parasites
leeching off of us will surface. Anyone here old enough to remember
Ed Esber? But in the long run, I've never seen a global phenomenon
like Twitter, so I'm in it for the next 10 years at least. Then I can
retire.

Let's keep the discussion open guys. They've already taken away the
most important thing you wanted. Now we can build with our eyes open.
And don't be afraid to speak up. This is Twitter. Revolutions happen
here.

Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: DM rate limit

Confirming limits is not Twitter HQ's strength. I can see why. They
want to keep their options open. Instead of asking for approval, why
not start a petition to get what you need?

Put up a message here stating a case for more DMs. Explain why you
want it. Ask other devs to sign on with a confirming response. When
you get no reaction, repost the same request the following week, and
again, and again, until Twitter makes the change or comes up with a
useful alternative. What can they do to you? Cut off your
whitelisting? Believe me, grandfathered whitelisting is just a way of
keeping established devs quiet, and is unfair on its face. All
whitelisting will go away. Anyone want to bet against that?

Devs are Twitter's partners, not users to be controlled. Dev's make
money for Twitter. Let's help them make more money by getting them
more serious, business oriented users, not just more Beiber fans. We
can do this for Twitter. Twitter needs to help us do it.

Ok, Trevor?

On Sun, Feb 13, 2011 at 10:49 AM, Trevor Dean trevord...@gmail.com wrote:
 I appreciate the feedback but the issue is that our clients send DM's to 
 their customers and the customer base could and has grown beyond 250 users. 
 We have whitelisted the clients that needed increased rate limits so we are 
 ok for now but this could effect how we deal with future clients.  There has 
 been a lot of activity from this group and it's been hard to keep track of 
 all of the information but I did read that you can still request increased DM 
 rate limits which is all we need but I don't know if this has been confirmed 
 by someone from twitter.

 Trevor Dean | Director
 big time design  communication Inc.
 647 234 8198

 Visit http://www.bigtimedesign.ca for more information

 On 2011-02-12, at 6:59 PM, Xristofer Obbit dixt...@dixtort.net wrote:

 Why not have each client register a notification account with your app
 that sends a DM to their main account.  That gives every client 250
 DMs.  Better yet, make it a private account and push notifications as
 status updates giving you 1000/day while keeping privacy.

 Sent from my iPhone

 On Feb 12, 2011, at 5:17 PM, M. Edward (Ed) Borasky
 zn...@borasky-research.net wrote:

 On Sat, 12 Feb 2011 17:07:36 -0500, Trevor Dean trevord...@gmail.com 
 wrote:
 I agree, don't be so quick to judge.  We have an opt-in based service
 and out clients have thousands of customers that explicitly say yes
 send me direct messages.  The information we send is requested by the
 end user and is not spam.  So you can imagine that a client with a
 large user base could quickly go beyond the 250 dm/day limit.  It's
 unfortunate that the spammers take advantage and ultimately ruin
 things for legitimate services.

 Trevor Dean | Director
 big time design  communication Inc.
 647 234 8198

 Visit http://www.bigtimedesign.ca for more information

 Speaking of spam, there's a great article at the New York Times on J.C. 
 Penney, black hat SEO and Google:

 http://www.nytimes.com/2011/02/13/business/13search.html

 Many thanks to Twitter's spam fighters for keeping it as clean as it is, 
 under the circumstances.

 --
 http://twitter.com/znmeb http://borasky-research.net

 A mathematician is a device for turning coffee into theorems. -- Paul 
 Erdős

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: 
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Twitter Development platform - A Rant

 I'm guessing that was invite-only. You can always ask - as a
 business negotiating a partnership with another business.

 We'll have to wait and see about the Promoted products. Advertising sales is
 a fiercely competitive business and it's not something I personally want to
 deal with at the moment.

 Annotations? That was definitely a case where Twitter's reach seems to have
 exceeded its grasp. The story I've heard is that there are people in Twitter
 hacking away on it but the priorities do get adjusted according to the
 demands of the marketplace. If it could be a breakthrough spam killer, I
 think they'd push it front and center in a big hurry. ;-)

 --
 http://twitter.com/znmeb http://borasky-research.net

 A mathematician is a device for turning coffee into theorems. -- Paul
 Erdős

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Twitter Development platform - A Rant

 Well, I'm old enough but I was doing something radically different from
 Ashton-Tate at the time. This whole thread is starting to sound eerily
 similar to last year, when Fred Wilson made the infamous filling holes
 blog post, followed by Twitter buying Tweetie, followed by Chirp. I'd be
 surprised if the *Twitter* ecosystem could support 10,000 independent
 developers - they'd self-organize into businesses with some sort of power
 law size distribution, where the largest such business is Twitter itself.

 I don't know that Twitter wants to be embedded into the infrastructure of
 corporations. It seems to me that Twitter is unique and not at all suited
 to intra-enterprise communications. Besides, there are dozens of enterprise
 software platforms that can do everything Twitter can do except talk to the
 hundreds of millions of Twitter users in real-time. ;-)

 Maybe I am thinking too small, but then again, people aren't coming to *me*
 with problems big enough to require whitelisting, or for that matter
 Cassandra, or MapReduce, or sending thousands of DMs a day. Even if they
 did, there's no way I could compete with Twitter. I really should save this
 for my blog - it's been a while since I wrote a post about Twitter, and
 that's what my search analytics tell me people read there. ;-)

Good points. I think the basic confusion is the definition of
developer. It could mean someone who builds a web or mobile app and
tries to monetize it. That would be limited. I think it also means all
the consultants and in-house programmers who integrate Twitter into
existing websites and businesses. As I started responding CNN ran a
big button on the screen telling people to try their Twitter
integration on their website. I think that was built by a developer,
not Twitter HQ. Multiply that by every TV show, radio program,
newspaper, magazine, movie, real estate office, hospital, retailer,
you get the point. There are way more than 10,000 programmers who work
on websites and mobile apps around the world. They are all possible
Twitter developers, among other tasks they did. Too big an idea?
Maybe, but with the right assistance from Twitter, there would be
enough developers that when a competitor comes along Twitter would
have a base that would make it hard to switch. That is what we offer
them.

I have an idea. Why doesn't Twitter hire a developer relations person?
Not a support person. Matt and Taylor do a good job of technical
support. I appreciate what they do. I mean someone who could run a
developer program. I haven't seen someone like that yet. Could some of
the $200 million pay that salary?

I look forward to your blog post on this, Edward.



-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Whitelisting is still in the docs. Please remove this.

2011-02-12 Thread Adam Green

http://dev.twitter.com/pages/rate-limiting#whitelisting

Ryan, Taylor, Matt, I know changing mistakes in the docs has been
impossible in the past. My guess is that someone lost the password for
these pages. But leaving the whitelisting statement in the docs and
the whitelisting form online is a sign of complete disrespect for your
developers. New devs will see this and still think they can get
whitelisting. Even worse they will waste their time building apps that
need whitelisting, since the request form says:
Whitelisting is only available to developers and to applications in
production

How would you feel if you started building an app today, spent months
on it, got it into production, and then waited months for approval,
since the docs say you won't get a response until approval is done?

Not removing this shows that developers don't really matter to
Twitter. Removing it right away shows that they do. Please don't say
that you are too busy to make that change, and that it will be done
some time in the future. Nobody is that busy.

Please remove it. Thanks.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Whitelisting is still in the docs. Please remove this.

2011-02-12 Thread Adam Green

Damn! I had 120 days in the pool. :)

Thanks, Taylor.

On Sat, Feb 12, 2011 at 11:29 AM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
 Sorry Adam, missed this document among the many -- it's fixed now. The form
 itself and its text are immutable at the moment.

 On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote:

 http://dev.twitter.com/pages/rate-limiting#whitelisting

 Ryan, Taylor, Matt, I know changing mistakes in the docs has been
 impossible in the past. My guess is that someone lost the password for
 these pages. But leaving the whitelisting statement in the docs and
 the whitelisting form online is a sign of complete disrespect for your
 developers. New devs will see this and still think they can get
 whitelisting. Even worse they will waste their time building apps that
 need whitelisting, since the request form says:
 Whitelisting is only available to developers and to applications in
 production

 How would you feel if you started building an app today, spent months
 on it, got it into production, and then waited months for approval,
 since the docs say you won't get a response until approval is done?

 Not removing this shows that developers don't really matter to
 Twitter. Removing it right away shows that they do. Please don't say
 that you are too busy to make that change, and that it will be done
 some time in the future. Nobody is that busy.

 Please remove it. Thanks.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Is includes_rts=true for statuses/mentions broken?

2011-02-11 Thread Adam Duke

I figured out why I was not seeing native retweets being included in
my results.
I was calling api.twitter.com/statuses/user_timeline, but should have
been calling api.twitter.com/1/statuses/user_timeline.
Adding the 1/ for the api version made the difference.
Perhaps that is the cause of Anil's problem as well.


On Feb 10, 2:06 am, Abraham Williams 4bra...@gmail.com wrote:
 I think you have the wrong idea of what include_rts does. Include_rts is
 designed to include native retweets in timelines where default inclusion
 would break. For example /statuses/user_timeline expects all tweets to be
 from a user A. But if that user A has retweeted user B then user Bs tweets
 can be included user As user_timeline with include_rts. Include_rts has no
 effect on /statuses/mentions because the original tweet is already included
 due to the fact it is a mention.

 Abraham
 -
 Abraham Williams | Hacker Advocate | abrah.am
 @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am
 This email is: [ ] shareable [x] ask first [ ] private.On Wed, Feb 9, 2011 at 
 21:00, Adam Duke adam.v.d...@gmail.com wrote:
  I've seen the same behavior with the include_rts parameter. I have
  tried passing the values 'true', 't', and '1' with no success.

  On Feb 8, 7:15 pm, Anil Chawla ani...@gmail.com wrote:
   It's been a while but I want to follow up on this because we still
   have the issue. Is anyone able to pull native retweets when calling
   the statuses/mentions endpoint?

   An indication that includes_rts either works for you or doesn't work
   would be great. Thanks,

   -Anil

   On Dec 14 2010, 11:44 am, Anil Chawla ani...@gmail.com wrote:

I've also been facing this issue for quite a long time. I've told
myself that this can't be a problem with the API (since nobody else is
complaining) but I can't see what is wrong on our end. For example, I
have the following status that was retweeted a few times:

   http://twitter.com/#!/anilchawla/status/14437959797313536

This is the request URL that is generated when I request my mentions
using count=200, include_rts=true, and since_id = 13978625736970241
(OAuth tokens omitted):
 https://api.twitter.com/1/statuses/mentions.json?count=200include_rt...

The four mentions of the above status are not present in the response
even though those retweets and the original status have an ID greater
than since_id. Omitting count and since_id does not make a
difference. As a work-around, we have to pull both statuses/mentions
and statuses/retweets_of_me and merge them together. It's hard to
believe that everyone else has been doing the same and ignoring this
API parameter. Any idea what the issue is?

-Anil

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: user stream api

2011-02-11 Thread Adam Green

Be aware that the streaming API does not deliver everything you are
tracking. In theory it delivers everything up to 1% of the total flow
of tweets. In practice, I find that it delivers about 95% of the
tweets that match your keywords or users. This is fine when sampling,
which is what I generally use it for, but will cause much anguish if
you assume you will get everything sent by people you are following. I
have to admit that I have only found this issue with the streaming
API, but I'm betting that the user streams are based on the same
underlying code.

My solution to the missing values from the streaming API is to collect
everything I can from streaming, then use the REST API to backfill
data I might not have received. If you run the backfill every hour,
you only have to go back to the last set of good tweets, adding
anything you missed.

On Fri, Feb 11, 2011 at 1:10 PM, DaveH d...@idreia.com wrote:
 I too am still worried about the DM limits.

 If I understand the User API correctly.
 - The user stream means that an unlimited number of DMs can be
 received as there is no rate limit on receiving (consuming) of data.
 - The application would send DMs via the REST API and therefore is
 limited to sending 250 DMs per day.

 For my application this is still a problem as my target is social
 learning and part of that is DMs to send/receive responses to test
 questions and such--things that need to be private. Conversations
 between learners are tweeted.

 So the design changes we need to make are:
 - Consuming information (Tweets, retweets, and DMs) is done via the
 user stream API
 - Sending tweets and DMs is still done by the REST API.

 It is going to take some time to get my head wrapped around this.
 Until the announcement yesterday I was not paying attention to the
 streams as they did not fit all that well with my application. Now I
 see that it is important to create an application that uses both as
 the app is both the consumer of users activity (DMs) and originator
 (DMs and tweets).

 On Feb 11, 8:31 am, Trevor Dean trevord...@gmail.com wrote:
 Thanks Taylor.  I posted a question to the group yesterday but it might have
 gotten lost amongst all the other posts about not whitelisting anymore.
  With our service we rely on sending DM's and we will most likely require to
 have more of our clients whitelisted.  What is will be the future of DM
 limits and going about getting those rates increased?

 Trevor.

 On Fri, Feb 11, 2011 at 11:11 AM, Taylor Singletary 







 taylorsinglet...@twitter.com wrote:
  Hi Trevor,

  Write operations in the Twitter API are always done via the REST API. The
  Streaming APIs are for consumption of data.

  @episod http://twitter.com/episod - Taylor Singletary - Twitter
  Developer Advocate

  On Fri, Feb 11, 2011 at 7:52 AM, Trevor Dean trevord...@gmail.com wrote:

  I can't seem to find any documentation that shows how to go about sending
  a DM using the new user stream api.  I have been through all of the
  documentation on dev.twitter.com.  Can someone point me in the right
  direction?

  Thanks,

  Trevor

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

   --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Update on Whitelisting

2011-02-10 Thread Adam Green

/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: Is includes_rts=true for statuses/mentions broken?

2011-02-09 Thread Adam Duke

I've seen the same behavior with the include_rts parameter. I have
tried passing the values 'true', 't', and '1' with no success.

On Feb 8, 7:15 pm, Anil Chawla ani...@gmail.com wrote:
 It's been a while but I want to follow up on this because we still
 have the issue. Is anyone able to pull native retweets when calling
 the statuses/mentions endpoint?

 An indication that includes_rts either works for you or doesn't work
 would be great. Thanks,

 -Anil

 On Dec 14 2010, 11:44 am, Anil Chawla ani...@gmail.com wrote:



  I've also been facing this issue for quite a long time. I've told
  myself that this can't be a problem with the API (since nobody else is
  complaining) but I can't see what is wrong on our end. For example, I
  have the following status that was retweeted a few times:

 http://twitter.com/#!/anilchawla/status/14437959797313536

  This is the request URL that is generated when I request my mentions
  using count=200, include_rts=true, and since_id = 13978625736970241
  (OAuth tokens 
  omitted):https://api.twitter.com/1/statuses/mentions.json?count=200include_rt...

  The four mentions of the above status are not present in the response
  even though those retweets and the original status have an ID greater
  than since_id. Omitting count and since_id does not make a
  difference. As a work-around, we have to pull both statuses/mentions
  and statuses/retweets_of_me and merge them together. It's hard to
  believe that everyone else has been doing the same and ignoring this
  API parameter. Any idea what the issue is?

  -Anil

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] High number of 502 errors in REST API

2011-02-04 Thread Adam Green

Good suggestion, Taylor. I was using a count of 200 to reduce the
number of calls, and stay under the rate limit. I just tried a count
of 100 and had fewer errors. I need to backfill test from 32 accounts
with a total of 20,000 tweets. I will rewrite this to use a lower
count, perhaps 50, and then spread the testing out over the whole day,
instead of doing it in one run every 24 hours. Thanks.

On Thu, Feb 3, 2011 at 11:51 PM, Taylor Singletary
taylorsinglet...@twitter.com wrote:
 What kind of count values are you using? When we're at capacity,
 higher count values' processing time can exceed our timeout filters. I
 would recommend lowering count values as a response to this error and
 retrying.

 Taylor

 On Thursday, February 3, 2011, Jan Paricka jpari...@gmail.com wrote:
 Adam, I noticed the same - 502 502 502 502 a lot lately!
 Jan

 On Fri, Feb 4, 2011 at 5:14 AM, Adam Green 140...@gmail.com wrote:
 I'm using 1/statuses/user_timeline to verify that I am receiving all
 the tweets for a set of users I am following with the streaming API.
 Once per day I try to collect all the tweets for these users using
 this API call. The total process takes about 100 calls to the API. For
 the last week I have been receiving a very high level of 502 error
 responses, about 1 for every 2 to 3 calls. Is this just due to very
 high traffic related to Egypt, or is something else going on?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk





 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk


 --
 @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer
 Advocate

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] High number of 502 errors in REST API

2011-02-03 Thread Adam Green

I'm using 1/statuses/user_timeline to verify that I am receiving all
the tweets for a set of users I am following with the streaming API.
Once per day I try to collect all the tweets for these users using
this API call. The total process takes about 100 calls to the API. For
the last week I have been receiving a very high level of 502 error
responses, about 1 for every 2 to 3 calls. Is this just due to very
high traffic related to Egypt, or is something else going on?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Missing tweets or invalid statuses_count

2011-02-02 Thread Adam Green

I'm collecting all the tweets for potential 2012 presidential
candidates, and I'm finding that /statuses/user_timeline returns much
fewer tweets than listed as the total in an account. The docs say that
this API call is limited to 3,200 tweets, but this is happening with
accounts that have fewer than that number. For example:

@barackobama - Statuses_count from API and tweet count listed on
profile is 2,467, but /statuses/user_timeline only delivers 1,033
tweets.
@GovChristie - Statuses_count is 1,062, but API only delivers 1,038.

This problem occurs in about 20% of the accounts I've checked. So
either the tweets are no longer available, or the statuses_count is
just wrong a lot of the time. This problem has persisted through 2
weeks of testing.

Anyone else seeing the same problem?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Missing tweets or invalid statuses_count

2011-02-02 Thread Adam Green

I'm using your OAuth library for this. I tried:
  $connection-request('GET', $connection-url('1/statuses/user_timeline'),
array('screen_name' = 'barackobama',
  'include_entities' = 't',
  'include_rts' = 't',
  'count' = 200,
  'page' = $page));

I get the same set of tweets I do without  'include_rts' = 't'. I'm
sure I'm missing something completely obvious, although probably
undocumented. Are there any examples of a response in the docs that
does include a new style RT that I can look at? I assume they are kept
in a part of the JSON I'm not used to looking for.

On Wed, Feb 2, 2011 at 5:44 PM, Matt Harris thematthar...@twitter.com wrote:
 Hey Adam,
 Do you include the parameter include_rts=1 ? Be default
 statuses/user_timeline doesn't include retweets so you have to add this
 parameter to retrieve a full timeline.
 Best
 @themattharris
 Developer Advocate, Twitter
 http://twitter.com/themattharris


 On Wed, Feb 2, 2011 at 2:28 PM, Adam Green 140...@gmail.com wrote:

 I'm collecting all the tweets for potential 2012 presidential
 candidates, and I'm finding that /statuses/user_timeline returns much
 fewer tweets than listed as the total in an account. The docs say that
 this API call is limited to 3,200 tweets, but this is happening with
 accounts that have fewer than that number. For example:

 @barackobama - Statuses_count from API and tweet count listed on
 profile is 2,467, but /statuses/user_timeline only delivers 1,033
 tweets.
 @GovChristie - Statuses_count is 1,062, but API only delivers 1,038.

 This problem occurs in about 20% of the accounts I've checked. So
 either the tweets are no longer available, or the statuses_count is
 just wrong a lot of the time. This problem has persisted through 2
 weeks of testing.

 Anyone else seeing the same problem?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Retweet_count value is returning odd values

2011-02-02 Thread Adam Green

It looks like the retweet_count value is invalid. Here is what I do
for 32 possible 2012 candidates:
1. Each hour I get all tweets from statuses/user_timeline. They each
fit within the 3,200 limit.
2. Collect the value of retweet_count for all tweets for each
candidate.
3. Sum these values to get the total retweets of the candidate's
tweets.
4. Compare this to the previous hour to see how many retweets they
got.

The whole thing takes about 32 API calls, so its lightweight.

The total retweet count for @barackobama's tweets has been jumping
back and forth between 79,730 and 80,648 since 5:00pm ET. I have to
believe this is broken.

Now that I really understand the new RTs, I will be getting these
values myself from the streaming API, which I use anyway for these
accounts. I can keep my own counts and not max out at 100 RTs per
tweet.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] email address and phone number for friends

2011-01-31 Thread Adam Green

Email addresses and phone numbers are not available from the Twitter API.

On Mon, Jan 31, 2011 at 9:02 AM, AressAmol aress.a...@gmail.com wrote:
 Using the Twitter API is it possable to fetch the email address and
 phone number of friends?

 I am trying to fetch the friends details with the twitter API, but
 unable to get the friends email Id and phone number.

 Please let me know the answer for the same. thanks in advance

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Upgrading from Read to Read / Write access for OAuth API Key

2011-01-30 Thread Adam Green

So if a user authorizes an app for read access, the app can switch to
read/write at any time without asking the users permission? Is this
true? Anyone from Twitter have any input on this?

On Sun, Jan 30, 2011 at 11:04 AM, Patrick Kennedy kenned...@gmail.com wrote:
 Tim -

 1.  Changing from read to read/write won't change you API consumer
 keys or tokens.

 2.  Your application's users don't authorized for read or read/write;
 they merely use your application, which you offer as read or
 read/write to the world.  That is to say, if it's read, your
 application can only read its tweets, and if read/write, it can both
 read its own tweet and post to the world.

 I'd say go ahead and switch to read/write, given the fact that you now
 want that functionality.

 ~Patrick

 On Sat, Jan 29, 2011 at 10:24 PM, Tim Bull tim.b...@binaryplex.com wrote:
 We must be about the only developers in the universe that requested
 users grant only read access when we first got people to connect
 http://trunk.ly to Twitter (I think of the 40 or so apps authorized on
 my account, Trunk.ly is the only one that asks for Read only).  Never
 ask for more access than you need is my philosophy.

 Doh!

 Of course now, we want to add some Tweet out functions which require
 users grant us Write access.

 A couple of questions for the Twitter people.

 1. If we change the access in the application from read to read/write
 does this reset the API key, or will it stay the same (hoping it stays
 the same).
 2. How can I work out if existing users have authorised us for read/
 write?  I looked at 
 http://developer.twitter.com/doc/get/account/verify_credentials
 but it doesn't show me what access they have.  Do I have to write,
 fail, force them to step through OAuth then post? Or is there a way of
 knowing before hand it will fail and asking them to upgrade?

 Thanks,

 Tim

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk


 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: in_reply_to_status_id

2011-01-28 Thread Adam Duke

I was working with this api method today as well. What I found was
that if your update's text does not contain an @reply to the user who
created the status you are sending a reply to, Twitter seems to ignore
the in_reply_to_status_id. I hope that helps.

-Adam

On Jan 28, 10:11 am, Rocker shadab.empo...@gmail.com wrote:
 Hi all,

 I am trying to achieve the reply functionality of the twitter to a
 particular tweet(status) using 
 thehttp://api.twitter.com/version/statuses/update.formaturl.
 In this i am passing in_reply_to_status_id parameter and
 include_entities=true to replay to a tweet.
 The status got updated but the response xml doesn't contain any data
 in the in_reply_to_status_id node.
 Even though the status got posted, it isn't displayed as a reply.

 Am i on the wrong track?
 What could be the possible reason. I am using OAuth for the whole
 scenario.

 Thanks
 Rocker

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Does whitelisting still exist?

2011-01-25 Thread Adam Green

I'm beginning to get suspicious about the whitelisting program. We've
gone from it being relatively easy to get whitelisted, to it being
harder but at least Brian Sutorius or someone else apologized, to it
being much harder and Taylor saying they can't even reply with a
denial, to no response at all to whitelisting questions.

There is no excuse about being too busy that justifies this total lack
of response. It would be great if Brian Sutorius or Ryan Sarver made a
clear statement about whether there is still a whitelisting program at
all. I understand everyone can't be whitelisted, but can anyone be
whitelisted?

I earn my living from the Twitter API. I want it to succeed. This is
not meant as an attack. It is a warning that hiding from this issue is
hurting the Twitter ecosystem. If there is no whitelisting, let us
know so we can construct apps that will always live within the default
limits. That is possible, but we must be able to warn clients about
this, otherwise we are lying to them. I don't know about Twitter HQ,
but I am old enough to know that lying doesn't work. It always catches
up with you. So please tell us the truth about this.

I doubt if any of the other API developers want to stick their necks
out, but if *anyone* has gotten whitelisted in the last few months, it
would be great to hear it.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Sending Tweets using 0Auth - beginner question

2011-01-21 Thread Adam Green

If you only need to send tweets to a single Twitter account, you can try
this PHP code, which uses Matt Harris's OAuth library:
http://140dev.com/twitter-api-programming-tutorials/hello-twitter-oauth-php/

If you need a more advanced solution that tweets to multiple accounts where
the users log into your site first, you can take a look at Abraham's
library:
https://github.com/abraham/twitteroauth


On Fri, Jan 21, 2011 at 10:16 AM, shamm shaena...@gmail.com wrote:

 Hi,

 I am an absolute beginner here. I need to send tweets through a PHP
 web interface. It seems in the new twitter we should use 0Auth for
 authentication, i Googled and got loads of articles that explains
 these. yet i am still unclear to code this. Is there any easy to
 understand sample code (that could at least only send Tweets), so i
 could read and understand what's going on.

 Please help !

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Re: Sending Tweets using 0Auth - beginner question

2011-01-21 Thread Adam Green

Check the application details in your Dev.twitter.com account. The app needs
to be set to read and write access.

On Fri, Jan 21, 2011 at 11:57 AM, shamm shaena...@gmail.com wrote:

 Thank you for your post, i have a question,

 Why does Posting... Response code: 401  get displayed even after i
 display the correct information asked in the post_tweet.php page;

  $connection = new tmhOAuth(array(
'consumer_key' = 'xg',
'consumer_secret' = 'x',
'user_token' = '2x-
 SYx',
'user_secret' = 'xWiVkvBJcGA',
  ));

 Any idea why this is hapenning ?

 On Jan 21, 8:28 pm, Adam Green 140...@gmail.com wrote:
  If you only need to send tweets to a single Twitter account, you can try
  this PHP code, which uses Matt Harris's OAuth library:
 http://140dev.com/twitter-api-programming-tutorials/hello-twitter-oau...
 
  If you need a more advanced solution that tweets to multiple accounts
 where
  the users log into your site first, you can take a look at Abraham's
  library:https://github.com/abraham/twitteroauth
 
 
 
 
 
 
 
 
 
  On Fri, Jan 21, 2011 at 10:16 AM, shamm shaena...@gmail.com wrote:
   Hi,
 
   I am an absolute beginner here. I need to send tweets through a PHP
   web interface. It seems in the new twitter we should use 0Auth for
   authentication, i Googled and got loads of articles that explains
   these. yet i am still unclear to code this. Is there any easy to
   understand sample code (that could at least only send Tweets), so i
   could read and understand what's going on.
 
   Please help !
 
   --
   Twitter developer documentation and resources:
 http://dev.twitter.com/doc
   API updates via Twitter:http://twitter.com/twitterapi
   Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
   Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 
  --
  Adam Green
  Twitter API Consultant and Trainerhttp://140dev.com
  @140dev

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] is streaming API read-only?

2011-01-18 Thread Adam Green

For making changes to user accounts and posting tweets you need to use the
REST API.
http://dev.twitter.com/doc

On Mon, Jan 17, 2011 at 3:19 PM, Gary Ma gang...@gmail.com wrote:

 Hi,

 I have an impression that streaming API (for example, user stream API) is
 read-only. I can obtain statuses but I won't be able to update, such as add
 follows to a user account. Is it correct?

 Thanks,
 Gary

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Twitter feed for corporate website/portal

2011-01-11 Thread Adam Green

You can use the /statuses/user_timeline API call instead of the feed if you
want. This doesn't require authentication, so there is no need to create an
app, if you use this call:
http://dev.twitter.com/doc/get/statuses/user_timeline

But  no matter how you get the data, rate limiting will still be the same.
There are three ways to address rate limiting:
1. Get the feed or /statuses/user_timeline without authentication at a rate
up to 150 times per hour and store the tweets in a database. Then serve
tweets to your web page from the database.
2. Create an app that uses OAuth to get the feed or /statuses/user_timeline
at a rate up to 350 times per hour. Store and serve from DB as in 1.
3. Use the Streaming API to follow the user account. This uses Basic Auth,
so no app is needed. Get the data, store and serve from DB. The streaming
API has the advantage of delivering the data in real time with no rate
limiting.

The point here is that each page load should not call Twitter for data. It
should call for your copy of the data.

If you decide to use 2, you do need an app to do OAuth. From my experience,
the app registration page needs a properly formatted URL, not a valid URL
that you own. This means anything that follows the format of
http://domain.com will work. You can even use http://twitter.com.
-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

On Tue, Jan 11, 2011 at 7:43 PM, TehOne ele...@gmail.com wrote:

 I have a corporate website/portal that I want to pull in tweets to,
 but i'm getting a rate limit using the http feed. So I need to explore
 other options. Do I need to use an authenticated method to get the
 tweets?

 Do I really have to register an application to do this, even though
 it's not really an application and my users will never be entering or
 changing the twitter account info. It will be a single twitter account
 that I will be pulling the feed from.

 Also, my corporate site doesn't have a public address, and registering
 an application through twitter appears to require a public url. So how
 can I get around this? Do I have to create a fake application with a
 public url, just to generate my keys?

 Thanks for any help on this.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk


-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] API fails when tweeting with single asterisk

2011-01-07 Thread Adam Green

Matt:

Is it a related issue that a leading or trailing asterisk is invisible
to the search API?  None of these searches return any results, even
though they do appear in a timeline API call or the streaming API:
**test
test**
**
*test
test*

Yet the search API can find:
test**test


On Tue, Jan 4, 2011 at 8:57 PM, Matt Harris thematthar...@twitter.com wrote:
 Hi Adam,
 That's correct, a tweet cannot be just a * or a * word. Something like
 ** or * html { would be fine though.
 Best,
 @themattharris
 Developer Advocate, Twitter
 http://twitter.com/themattharris


 On Tue, Jan 4, 2011 at 5:29 PM, Adam Green 140...@gmail.com wrote:

 So I can assume that * and * word will remain unavailable for normal
 tweeting?

 On Tue, Jan 4, 2011 at 7:22 PM, Matt Harris thematthar...@twitter.com
 wrote:
  Hey Adam,
  The status update you are sending is part of the SMS command set.
      http://support.twitter.com/articles/14020-about-twitter-sms-commands
  It corresponds to the FAV command and is the alias for it. It used to be
  documented but for some reason isn't there at the moment. I've asked the
  support team to make sure it is added.
  Best,
  @themattharris
  Developer Advocate, Twitter
  http://twitter.com/themattharris
 
 
  On Tue, Jan 4, 2011 at 4:09 PM, Adam Green 140...@gmail.com wrote:
 
  There are some very strange behaviors when using the statuses/update
  API call to send a tweet with a single asterisk.
 
  1. If you send a tweet with just a single asterisk:
  *
 
  The API returns 200 and the response string contains the previous good
  tweet in the timeline. No new tweet with an asterisk appears in the
  timeline. Repeating this API call results in the same behavior.
 
  2. If you send a statuses/update with a single asterisk followed by a
  single word:
  * test
 
  The first time you do this, the API returns 200 and the response
  string contains the previous good tweet in the timeline. No new tweet
  with the string sent to the API appears in the timeline. If you repeat
  the same API call, the API returns 500 and the response string has an
  HTML page that something strange happened:
  h2Something is technically wrong./h2
  pThanks for noticing we're going to fix it up and have things back
  to normal soon./p
 
  No other use of the asterisk has a problem that I can find. These bad
  tweet strings cause similar problems on Twitter.com.
 
  --
  Twitter developer documentation and resources:
  http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 
  --
  Twitter developer documentation and resources:
  http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 



 --
 Adam Green
 Twitter API Consultant and Trainer
 http://140dev.com
 @140dev

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] user page (viewed in old twitter) is stale by 7 hours

2011-01-06 Thread Adam Covati

We have a problem where some one was worried that their posts weren't
making it from our application to twitter. After looking deeper I've
found that a twitter page for a user is very different if you are
logged in or not.

Please note: Below I refer to the page you see when not logged in as
the 'public page', this is an 'old twitter' page, as opposed to the
'new twitter' view I see when logged in.

It appears the public page for one of our client's twitter accounts is
cached right now and is currently 7 ours behind - this is not just on
one computer, we've seen several computers loading the 'old' page. By
7 hours behind, I mean that a tweet time shows as '1 hour ago' on the
page, but then shows as '8 hours ago' if you log in and view the page
or if you click through on the time and view the actual status' page.
Also a tweet that was posted about 3 hours ago doesn't show up at all
the public page.

Might this be due to page caching or load balancing that is done on
twitter's end for 'old twitter' but not done for 'new twitter'?

I can provide details or screenshots taken within seconds of each
other if that helps, but if anyone else has seen this at all, or knows
of this being normal that'd be helpful.

Thanks

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Re: user page (viewed in old twitter) is stale by 7 hours

2011-01-06 Thread Adam Covati

Matt,

It appears that the timeline does not contain all the content. It is
still missing the most recent tweet.

As an example, this tweet 23043372398673920 is shown in new twitter,
but not in the website view.

Thanks for the info though,
Adam

On Jan 6, 2:48 pm, Matt Harris thematthar...@twitter.com wrote:
 Hey Adam,

 Thanks for raising this. The website isn't part of the API so we're not in a
 position to fix or address the issue. That being said I have checked with
 our user support team and know that they are tracking this very issue with
 the engineering teams.

 From what i've been told the timeline should contain all the content, it's
 just the timestamps are wrong. Does that match with your observation?
 Best,
 @themattharris
 Developer Advocate, Twitterhttp://twitter.com/themattharris







 On Thu, Jan 6, 2011 at 11:08 AM, Adam Covati cov...@gmail.com wrote:
  We have a problem where some one was worried that their posts weren't
  making it from our application to twitter. After looking deeper I've
  found that a twitter page for a user is very different if you are
  logged in or not.

  Please note: Below I refer to the page you see when not logged in as
  the 'public page', this is an 'old twitter' page, as opposed to the
  'new twitter' view I see when logged in.

  It appears the public page for one of our client's twitter accounts is
  cached right now and is currently 7 ours behind - this is not just on
  one computer, we've seen several computers loading the 'old' page. By
  7 hours behind, I mean that a tweet time shows as '1 hour ago' on the
  page, but then shows as '8 hours ago' if you log in and view the page
  or if you click through on the time and view the actual status' page.
  Also a tweet that was posted about 3 hours ago doesn't show up at all
  the public page.

  Might this be due to page caching or load balancing that is done on
  twitter's end for 'old twitter' but not done for 'new twitter'?

  I can provide details or screenshots taken within seconds of each
  other if that helps, but if anyone else has seen this at all, or knows
  of this being normal that'd be helpful.

  Thanks

  --
  Twitter developer documentation and resources:http://dev.twitter.com/doc
  API updates via Twitter:http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Transferring a suspended account to the proper owner

2011-01-06 Thread Adam Green

I have a client who owns a .com domain name and has applied for a
trademark for the matching name. The Twitter account for this name was
created by someone else and has been suspended. Is there any way to
help them take over this account? They really want to build a Twitter
based app around this name, so using the matching account name is
important to them. And they want me to build the app, so it's
important to me too. Any directions towards a path to resolve this
would be greatly appreciated.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Search result is incorrect

2011-01-05 Thread Adam Green

The search API only goes back about 7 days. Older tweets are not returned.

On Wed, Jan 5, 2011 at 12:45 AM, binku bink...@gmail.com wrote:
 search results is incorret when i search tweets from myself, like
 this: http://search.twitter.com/search?q=+from%3Abinku87.  This is
 only two results, but definitely my tweets(http://twitter.com/#!/
 binku87) is more than two. Everybody has every idea about this?

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] API fails when tweeting with single asterisk

2011-01-04 Thread Adam Green

There are some very strange behaviors when using the statuses/update
API call to send a tweet with a single asterisk.

1. If you send a tweet with just a single asterisk:
*

The API returns 200 and the response string contains the previous good
tweet in the timeline. No new tweet with an asterisk appears in the
timeline. Repeating this API call results in the same behavior.

2. If you send a statuses/update with a single asterisk followed by a
single word:
* test

The first time you do this, the API returns 200 and the response
string contains the previous good tweet in the timeline. No new tweet
with the string sent to the API appears in the timeline. If you repeat
the same API call, the API returns 500 and the response string has an
HTML page that something strange happened:
h2Something is technically wrong./h2
pThanks for noticing we're going to fix it up and have things back
to normal soon./p

No other use of the asterisk has a problem that I can find. These bad
tweet strings cause similar problems on Twitter.com.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] API fails when tweeting with single asterisk

2011-01-04 Thread Adam Green

So I can assume that * and * word will remain unavailable for normal tweeting?

On Tue, Jan 4, 2011 at 7:22 PM, Matt Harris thematthar...@twitter.com wrote:
 Hey Adam,
 The status update you are sending is part of the SMS command set.
     http://support.twitter.com/articles/14020-about-twitter-sms-commands
 It corresponds to the FAV command and is the alias for it. It used to be
 documented but for some reason isn't there at the moment. I've asked the
 support team to make sure it is added.
 Best,
 @themattharris
 Developer Advocate, Twitter
 http://twitter.com/themattharris


 On Tue, Jan 4, 2011 at 4:09 PM, Adam Green 140...@gmail.com wrote:

 There are some very strange behaviors when using the statuses/update
 API call to send a tweet with a single asterisk.

 1. If you send a tweet with just a single asterisk:
 *

 The API returns 200 and the response string contains the previous good
 tweet in the timeline. No new tweet with an asterisk appears in the
 timeline. Repeating this API call results in the same behavior.

 2. If you send a statuses/update with a single asterisk followed by a
 single word:
 * test

 The first time you do this, the API returns 200 and the response
 string contains the previous good tweet in the timeline. No new tweet
 with the string sent to the API appears in the timeline. If you repeat
 the same API call, the API returns 500 and the response string has an
 HTML page that something strange happened:
 h2Something is technically wrong./h2
 pThanks for noticing we're going to fix it up and have things back
 to normal soon./p

 No other use of the asterisk has a problem that I can find. These bad
 tweet strings cause similar problems on Twitter.com.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker:
 http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group:
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Tweeting with single asterisk

2011-01-04 Thread Adam Green

It looks like the following tweets will not be possible:
*
* word

All other uses of the single and double asterisk are acceptable. So,
Alexander, it looks like you are right in wanting ** as your
identifying string. That can be used with no problems. I would
recommend that we stick with that in any position in a tweet and not
even tell people about using a single asterisk.

-- Forwarded message --
From: Matt Harris thematthar...@twitter.com
Date: Tue, Jan 4, 2011 at 8:57 PM
Subject: Re: [twitter-dev] API fails when tweeting with single asterisk
To: twitter-development-talk@googlegroups.com


Hi Adam,
That's correct, a tweet cannot be just a * or a * word. Something
like ** or * html { would be fine though.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris


On Tue, Jan 4, 2011 at 5:29 PM, Adam Green 140...@gmail.com wrote:

 So I can assume that * and * word will remain unavailable for normal tweeting?

 On Tue, Jan 4, 2011 at 7:22 PM, Matt Harris thematthar...@twitter.com wrote:
  Hey Adam,
  The status update you are sending is part of the SMS command set.
      http://support.twitter.com/articles/14020-about-twitter-sms-commands
  It corresponds to the FAV command and is the alias for it. It used to be
  documented but for some reason isn't there at the moment. I've asked the
  support team to make sure it is added.
  Best,
  @themattharris
  Developer Advocate, Twitter
  http://twitter.com/themattharris
 
 
  On Tue, Jan 4, 2011 at 4:09 PM, Adam Green 140...@gmail.com wrote:
 
  There are some very strange behaviors when using the statuses/update
  API call to send a tweet with a single asterisk.
 
  1. If you send a tweet with just a single asterisk:
  *
 
  The API returns 200 and the response string contains the previous good
  tweet in the timeline. No new tweet with an asterisk appears in the
  timeline. Repeating this API call results in the same behavior.
 
  2. If you send a statuses/update with a single asterisk followed by a
  single word:
  * test
 
  The first time you do this, the API returns 200 and the response
  string contains the previous good tweet in the timeline. No new tweet
  with the string sent to the API appears in the timeline. If you repeat
  the same API call, the API returns 500 and the response string has an
  HTML page that something strange happened:
  h2Something is technically wrong./h2
  pThanks for noticing we're going to fix it up and have things back
  to normal soon./p
 
  No other use of the asterisk has a problem that I can find. These bad
  tweet strings cause similar problems on Twitter.com.
 
  --
  Twitter developer documentation and resources: http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 
  --
  Twitter developer documentation and resources: http://dev.twitter.com/doc
  API updates via Twitter: http://twitter.com/twitterapi
  Issues/Enhancements Tracker:
  http://code.google.com/p/twitter-api/issues/list
  Change your membership to this group:
  http://groups.google.com/group/twitter-development-talk
 



 --
 Adam Green
 Twitter API Consultant and Trainer
 http://140dev.com
 @140dev

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk

--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk



-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] how can i get statistics data about a search

The API doesn't return that type of data. You need to collect all the
search results in a database and then calculate the statistics in your
own code.

On Wed, Dec 29, 2010 at 5:02 AM, Macro puxiangc...@gmail.com wrote:
 i`m a new developer about twitter ,and i want to get some data about
 search like how many posts/rewteets/followers/friends  about a search
 day by day in a month or a week.

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Getting user information with oAuth.

If you don't know how to get started with the API, why not use a PHP
library and have it do this work for you? Two to start with are:
http://github.com/abraham/twitteroauth
http://github.com/themattharris/tmhOAuth

Once you get things working you can look at the library's code as a
model and then write it yourself.

On Thu, Dec 30, 2010 at 4:22 AM, xtranophilist xtranophil...@gmail.com wrote:
 I am starting a PHP application and not using any PHP library.
 I have successfully received oauth_token and oauth_verifier in the
 callback url.
 Now, how do I use this authentication to retrieve user information and
 perform other API requests.

 Thanks in advance!

 --
 Twitter developer documentation and resources: http://dev.twitter.com/doc
 API updates via Twitter: http://twitter.com/twitterapi
 Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
 Change your membership to this group: 
 http://groups.google.com/group/twitter-development-talk




-- 
Adam Green
Twitter API Consultant and Trainer
http://140dev.com
@140dev

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Is id_str getting dropped again from streaming API output?

I'm getting errors that the id_str property is not found within the
JSON output of the streaming API. I'm using Phirehose, but nothing has
changed with that or my code that is using it. This has happened
before. Is there a problem returning id_str again?

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

[twitter-dev] Unable to tweet with leading *

When I try entering a tweet through Twitter.com that starts with an
asterisk, I get an error of Sorry! We did something wrong, and the
tweet does not get sent. The same thing happens if I use Tweetdeck.

To try this, send the following tweet:
* test

There is no problem using a single asterisk anywhere else in a tweet
that I can find.

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Re: [twitter-dev] Unable to tweet with leading *