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

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

2011-01-07 Thread Matt Harris
Hey Adam, There are many reasons why Tweets may not show in Search but exist elsewhere. We have a support article which goes into this in more detail: http://support.twitter.com/articles/66018 To answer your question though it is likely the problem you are hitting is that * is ignored when

[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

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

2011-01-04 Thread Matt Harris
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

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.     

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

2011-01-04 Thread Matt Harris
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