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 entered as a search term (the same as many other
popular search interfaces). For this reason a search for "* test" will
search instead for the word "test" and return the results for it. It maybe
you were just giving an example but generally testing tweets are bad things
to look for in Search. Search is designed around relevance, something that
'test test' doesn't fit well with. Instead real world examples of the
content you are expecting are better tests.
Hope that helps,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Jan 7, 2011 at 4:12 AM, Adam Green <140...@gmail.com> wrote:
> 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:
> >> >> <h2>Something is technically wrong.</h2>
> >> >> <p>Thanks 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 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
