Perfect I have a basic implementation working already with one of my
existing clients... very powerful

Slight change of topic to the Site Streams.  The documentation
mentions public statuses.

I also have a push notification service on iPhone and certainly Site
Streams seems like the right method for this, however if I need to
follow thousands of users and also get their DM's and from both public
and protected accounts (I have the oAuth credentials to authenticate
them too), are these available just by following a user in a Site
Stream?

Richard

On Feb 14, 3:04 pm, Tom van der Woerdt <i...@tvdw.eu> wrote:
> Home Timeline => check it in the friends dictionary
> Mention => match the tweet's text
> Search => match the keywords
>
> The rest is easy.
>
> Tom
>
> On 2/14/11 4:01 PM, Rich wrote:
>
> > Hi all
>
> > I'm just starting to play with the User Streams with the aim of
> > allowing it in addition to REST api.
>
> > I've had a stream open for most of the day looking at the received
> > data and most of it looks pretty straightforward.
>
> > When it comes to DM's, deletes, etc the message tells us that in the
> > JSON.
>
> > The one thing I haven't noticed is how mentions are displayed.... for
> > example I receive a mention from someone I don't follow.  This only
> > appears on my Mentions API under REST and not my home timeline.
>
> > When I connect over User Streams it seems to just come in as any other
> > tweet.  My question is how do I determine that this is a mention that
> > shouldn't appear in my home timeline.
>
> > Do I have to keep track of the initial friends message and compare the
> > user id every time or is there something even simpler that I'm
> > missing?
>
> > Many thanks
> > Richard
>
>

-- 
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