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

Reply via email to