[twitter-dev] filter stream with follow predicate

2010-05-12 Thread Alam Sher
Is filter stream working fine with follow predicate. My application is keep
resetting the connection again and again and even on curl connection drops
just after it is created.


Thanks,
Alam Sher


Re: [twitter-dev] Logical AND supported in streaming API filter endpoint

2010-04-20 Thread Alam Sher
I love you guys. You did it ... That has increased the Streaming usability
to some 1000 times.

Thanks in million ways,
Alam Sher

On Tue, Apr 20, 2010 at 10:03 AM, M. Edward (Ed) Borasky
zn...@comcast.netwrote:

 On 04/19/2010 04:39 PM, Mark McBride wrote:
  To date the streaming API has only supported logical OR in track
  keywords (http://apiwiki.twitter.com/Streaming-API-Documentation#track).
   Today we're happy to announce that we support logical ANDing in
  production as well.
 
  The track parameter is treated as a series of phrases.  Phrases are
  separated by commas. Words within phrases are delimited by spaces. A
  tweet matches if any phrase matches. A phrase matches if all of the
  words are present in the tweet. (e.g. 'the twitter' is 'the' AND
  'twitter', and 'the,twitter' is 'the' OR 'twitter'.).  Some
  examples...
  1) twitter api,twitter streaming
  (
 http://stream.twitter.com/1/statuses/filter.xml?track=twitter+api%2Ctwitter+streaming
 )
  will match the tweets The Twitter API is awesome and The twitter
  streaming deal is fast, but not I'm new to Twitter
  2) The same approach to dealing with case, punctuation, @replies and
  hashtags still applies.  So chirp search,chirp streaming
  (
 http://stream.twitter.com/1statuses/filter.xml?track=chirp+search%2Cchirp+streaming
 )
  will match Listening to the @chirp talk on search, I'm at Chirp
  talking about search!, and loving this search talk #chirp
 
  This should dramatically close the gap on what you can do with the
  search API but not with streaming, and also reduce the amount of data
  users have to consumer to match on multiple keywords.
  Comments/questions welcome as always.
 
---Mark
 
  http://twitter.com/mccv
 
 

 Awesome!

 --
 M. Edward (Ed) Borasky
 borasky-research.net/m-edward-ed-borasky

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


 --
 Subscription settings:
 http://groups.google.com/group/twitter-development-talk/subscribe?hl=en




-- 
___
Alam Sher Khan
+92 331 505 5549


Re: [twitter-dev] Upcoming changes to the way status IDs are sequenced

2010-03-26 Thread Alam Sher
Yup, I am using since_id as well in my application to perform various
sequential tasks. Hopefully new id generation scheme will have  this
parameter support using some alternatives at least.

Alam Sher

On Sat, Mar 27, 2010 at 1:48 AM, Brian Smith br...@briansmith.org wrote:

 Any app that pages through timelines uses since_id or max_id depends
 responses being ordered by tweet ID. What will be the replacement for
 since_id and max_id?



 Taylor Singletary wrote:

 We are planning to replace our current sequential tweet ID generation
 routine with a simple, more scalable solution. IDs will still be 64-bit
 unsigned integers. However, this new solution is no longer guaranteed to
 generate sequential IDs.  Instead IDs will be derived based on time: the
 most significant bits being sourced from a timestamp and the least
 significant bits will be effectively random.



 For the majority of applications we think this scheme switch will be a
 non-event. Before implementing these changes, we'd like to know if your
 applications currently depend on the sequential nature of IDs. Do you depend
 on the density of the tweet sequence being constant?  Are you trying to
 analyze the IDs as anything other than opaque, ordered identifiers? Aside
 for guaranteed sequential tweet ID ordering, what APIs can we provide you to
 accomplish your goals?

 To unsubscribe from this group, send email to twitter-development-talk+
 unsubscribegooglegroups.com or reply to this email with the words REMOVE
 ME as the subject.




-- 
___
Alam Sher Khan
+92 331 505 5549

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words REMOVE ME as the subject.


Re: [twitter-dev] stream api---count parameter

2010-03-25 Thread Alam Sher
Sorry to hijack the thread at this point. But I would also like to know how
does +ve and -ve count values affect the history browsing.

Alam Sher

On Thu, Mar 25, 2010 at 9:43 PM, Mark McBride mmcbr...@twitter.com wrote:

 For the streaming API, the count parameter indicates how many statuses back
 in history you want streamed before switching over to the live stream.  This
 isn't supported on any of the default access levels that I know of.

 When you say the download speed is too slow, what do you mean?  That you
 want more statuses coming over the wire?

   ---Mark

 http://twitter.com/mccv



 On Thu, Mar 25, 2010 at 2:29 AM, erichou yhl7585...@gmail.com wrote:

 Dear Experts,

 Well I have been developing Twitter applicaiton,but encounter some
 difficult. I don't know how to use the count parameter, and what is
 the use of count parameter?

 Now in my application, I use sample api download status, and download
 20 status per second, But the download speed is too slow. If I want to
 improve the speed, what can i do?
 I don't know wheather I can improve the speed whenI use the count
 parameter,if can, how to use?

 To unsubscribe from this group, send email to twitter-development-talk+
 unsubscribegooglegroups.com or reply to this email with the words REMOVE
 ME as the subject.


  To unsubscribe from this group, send email to twitter-development-talk+
 unsubscribegooglegroups.com or reply to this email with the words REMOVE
 ME as the subject.




-- 
___
Alam Sher Khan
+92 331 505 5549

To unsubscribe from this group, send email to 
twitter-development-talk+unsubscribegooglegroups.com or reply to this email 
with the words REMOVE ME as the subject.


Re: [twitter-dev] Twitter API Request to Get the List of Friends Who have not followed you back

2010-03-10 Thread Alam Sher
I think its the simplest of features to implement using existing Twitter API
as Scott suggest.

Just write a method in your service to fetch friends ids and followers ids
and then compare these ids to separate the list of followers ids who are not
friends. Then provide links to unfollow these ids on interface. Is that
difficult? Not at all. Some client side programming is needed only.

Cheers,
Alam Sher

On Tue, Mar 9, 2010 at 8:46 PM, Dean Collins d...@cognation.net wrote:

 www.mypostbutler.com does that, basically in the unfollow feature it
 separates out who follows you back or not you can then see who has no
 return love for you :(



 Cheers,

 Dean




 -Original Message-
 From: twitter-development-talk@googlegroups.com
 [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Scott
 Wilcox
 Sent: Tuesday, March 09, 2010 9:58 AM
 To: twitter-development-talk@googlegroups.com
 Subject: Re: [twitter-dev] Twitter API Request to Get the List of
 Friends Who have not followed you back

 There is no API endpoint for this. You will need to build it clientside
 yourself. Get your list of followers and friends and then compare.

 Scott.

 On 9 Mar 2010, at 10:51, Durrab wrote:

  Hello,
 My name is Durrab and I want Twitter to Provide one more
  API Request as those Friends who have not followed your.
 
  For Example:
 
  http://api.twitter.com/1/friends/notfollowed/ids.format
 
  Thanks  Regards:
 
  Durrab




-- 
___
Alam Sher Khan
+92 331 505 5549


Re: [twitter-dev] retweets_of_me

2010-02-27 Thread Alam Sher
Thanks Abraham ...



On Fri, Feb 26, 2010 at 11:49 PM, Abraham Williams 4bra...@gmail.comwrote:

 Have a look at:
 http://apiwiki.twitter.com/Twitter-REST-API-Method:-statuses-retweets

 Abraham


 On Fri, Feb 26, 2010 at 03:10, Alam Sher alamshe...@gmail.com wrote:

 Hi,

 statuses/retweets_of_me.json returns me the tweets of mine that were
 retweeted. How to get the information that Who actually retweeted my
 tweet?

 Thanks,
 Alam Sher




 --
 Abraham Williams | Community Advocate | http://abrah.am
 Project | Out Loud | http://outloud.labs.poseurtech.com
 This email is: [ ] shareable [x] ask first [ ] private.




-- 
___
Alam Sher Khan
+92 331 505 5549


Re: [twitter-dev] Re: Streaming API Best Practice (Multiple Connections or Single)

2010-02-27 Thread Alam Sher
Okay, great.

When we say a default access account or elevated access is TOO FULL. Does
that mean, we have started getting rate limit messages in stream? Or it is
something else?


Thanks,
Alam Sher

On Sat, Feb 27, 2010 at 2:31 AM, John Kalucki j...@twitter.com wrote:

 The elevated access account can reconnect much less frequently by adding
 new predicates to a default access stream that cycles based on demand. When
 the default access account cycles, very little data will be lost, as it
 receives a small fraction of your total feed. Once the default access
 account is too full, the elevated access account can be restarted with the
 current predicates.


 -John Kalucki
 http://twitter.com/jkalucki
 Infrastructure, Twitter Inc.


 On Thu, Feb 25, 2010 at 12:25 PM, Alam Sher alamshe...@gmail.com wrote:

 Sorry, but exactly this portion of the documentations goes above my head.

 Can you please explain a bit more to me how a default access account can
 be used along with the elevated access account to minimize the data loss?

 Thanks,
 Alam Sher


 On Thu, Feb 25, 2010 at 7:15 PM, John Kalucki j...@twitter.com wrote:

 Yes, this is indeed what you should be doing. If you have a low tolerance
 for data loss, you will then use a total of four accounts: 2 elevated and 2
 default access accounts. If you can tolerate a few missing tweets on each
 reconnect, you can just use the two elevated accounts.

 -John Kalucki

 http://twitter.com/jkalucki
 Infrastructure, Twitter Inc.


 On Thu, Feb 25, 2010 at 2:06 AM, Alam Sher alamshe...@gmail.com wrote:

 So in case, if I have 20K users and I have to, say track 60K keywords
 for them + also have to follow all of them. I should be applying for 2
 higher access accounts one for track predicates and other for follow
 predicate. Does this make sense?

 Thanks,

 On Feb 25, 8:44 am, John Kalucki j...@twitter.com wrote:
  This technique works for updating any filter predicate. The count
 parameter
  should work on a shadow account. It won't work on a default access
 account.
  We have a number of very large integrations using this technique with
  Birddog access -- it should scale down to Shadow access just fine.
 
  The documentation makes it clear which cases are supported and which
 ones
  are not:http://apiwiki.twitter.com/Streaming-API-Documentation#count
 
  The count parameter isn't supported on track streams for computational
  complexity reasons, and it isn't supported on the default access role
 for
  policy reasons.
 
  -John Kaluckihttp://twitter.com/jkalucki
  Infrastructure, Twitter Inc.
 
  On Wed, Feb 24, 2010 at 2:31 PM, Jonathan Strauss 
 
  jonat...@snowballfactory.com wrote:
   On Feb 24, 2:06 pm, John Kalucki j...@twitter.com wrote:
The documentation should be pretty clear on this topic. One main
   connection,
and perhaps an auxiliary connection to manage query velocity.
 
   Hey John,
 
   Do you recommend this kind of 2 connection setup for updating our
 user
   list when using the follow predicate?
 
   We've been trying unsuccessfully to use the count parameter when
   reconnecting to add new users to our follow list. I've found several
   oblique mentions of the count parameter only working in some cases,
   but no specifics on how or why.
 
   We currently have shadow role access for the TweetPo.st app. We're
   trying to update our Streaming API connection when new users signup
   for TweetPo.st without losing tweets for existing users during
   reconnect. Any suggestions on the best way to do this would be
 greatly
   appreciated.
 
   Thanks!
   -jonathan
 
   =
   Jonathan Strauss, Co-Founder
  http://snowballfactory.com
 
   Campaign tracking for social media -http://awe.sm
   A smarter way to update Facebook from Twitter -http://tweetpo.st
   Sharecount button for Facebook -http://www.fbshare.me





 --
 ___
 Alam Sher Khan
 +92 331 505 5549





-- 
___
Alam Sher Khan
+92 331 505 5549


[twitter-dev] retweets_of_me

2010-02-26 Thread Alam Sher
Hi,

statuses/retweets_of_me.json returns me the tweets of mine that were
retweeted. How to get the information that Who actually retweeted my
tweet?

Thanks,
Alam Sher


Re: [twitter-dev] Re: Streaming API Best Practice (Multiple Connections or Single)

2010-02-25 Thread Alam Sher
So in case, if I have 20K users and I have to, say track 60K keywords for
them + also have to follow all of them. I should be applying for 2 higher
access accounts one for track predicates and other for follow predicate.
Does this make sense?

Thanks,
Alam Sher

On Thu, Feb 25, 2010 at 8:44 AM, John Kalucki j...@twitter.com wrote:

 This technique works for updating any filter predicate. The count parameter
 should work on a shadow account. It won't work on a default access account.
 We have a number of very large integrations using this technique with
 Birddog access -- it should scale down to Shadow access just fine.

 The documentation makes it clear which cases are supported and which ones
 are not: http://apiwiki.twitter.com/Streaming-API-Documentation#count

 The count parameter isn't supported on track streams for computational
 complexity reasons, and it isn't supported on the default access role for
 policy reasons.


 -John Kalucki
 http://twitter.com/jkalucki
 Infrastructure, Twitter Inc.



 On Wed, Feb 24, 2010 at 2:31 PM, Jonathan Strauss 
 jonat...@snowballfactory.com wrote:

 On Feb 24, 2:06 pm, John Kalucki j...@twitter.com wrote:
  The documentation should be pretty clear on this topic. One main
 connection,
  and perhaps an auxiliary connection to manage query velocity.

 Hey John,

 Do you recommend this kind of 2 connection setup for updating our user
 list when using the follow predicate?

 We've been trying unsuccessfully to use the count parameter when
 reconnecting to add new users to our follow list. I've found several
 oblique mentions of the count parameter only working in some cases,
 but no specifics on how or why.

 We currently have shadow role access for the TweetPo.st app. We're
 trying to update our Streaming API connection when new users signup
 for TweetPo.st without losing tweets for existing users during
 reconnect. Any suggestions on the best way to do this would be greatly
 appreciated.

 Thanks!
 -jonathan

 =
 Jonathan Strauss, Co-Founder
 http://snowballfactory.com

 Campaign tracking for social media - http://awe.sm
 A smarter way to update Facebook from Twitter - http://tweetpo.st
 Sharecount button for Facebook - http://www.fbshare.me





-- 
___
Alam Sher Khan
+92 331 505 5549


[twitter-dev] Re: Streaming API Best Practice (Multiple Connections or Single)

2010-02-25 Thread Alam Sher
So in case, if I have 20K users and I have to, say track 60K keywords
for them + also have to follow all of them. I should be applying for 2
higher access accounts one for track predicates and other for follow
predicate. Does this make sense?

Thanks,

On Feb 25, 8:44 am, John Kalucki j...@twitter.com wrote:
 This technique works for updating any filter predicate. The count parameter
 should work on a shadow account. It won't work on a default access account.
 We have a number of very large integrations using this technique with
 Birddog access -- it should scale down to Shadow access just fine.

 The documentation makes it clear which cases are supported and which ones
 are not:http://apiwiki.twitter.com/Streaming-API-Documentation#count

 The count parameter isn't supported on track streams for computational
 complexity reasons, and it isn't supported on the default access role for
 policy reasons.

 -John Kaluckihttp://twitter.com/jkalucki
 Infrastructure, Twitter Inc.

 On Wed, Feb 24, 2010 at 2:31 PM, Jonathan Strauss 

 jonat...@snowballfactory.com wrote:
  On Feb 24, 2:06 pm, John Kalucki j...@twitter.com wrote:
   The documentation should be pretty clear on this topic. One main
  connection,
   and perhaps an auxiliary connection to manage query velocity.

  Hey John,

  Do you recommend this kind of 2 connection setup for updating our user
  list when using the follow predicate?

  We've been trying unsuccessfully to use the count parameter when
  reconnecting to add new users to our follow list. I've found several
  oblique mentions of the count parameter only working in some cases,
  but no specifics on how or why.

  We currently have shadow role access for the TweetPo.st app. We're
  trying to update our Streaming API connection when new users signup
  for TweetPo.st without losing tweets for existing users during
  reconnect. Any suggestions on the best way to do this would be greatly
  appreciated.

  Thanks!
  -jonathan

  =
  Jonathan Strauss, Co-Founder
 http://snowballfactory.com

  Campaign tracking for social media -http://awe.sm
  A smarter way to update Facebook from Twitter -http://tweetpo.st
  Sharecount button for Facebook -http://www.fbshare.me


Re: [twitter-dev] Re: Streaming API Best Practice (Multiple Connections or Single)

2010-02-25 Thread Alam Sher
Sorry, but exactly this portion of the documentations goes above my head.

Can you please explain a bit more to me how a default access account can be
used along with the elevated access account to minimize the data loss?

Thanks,
Alam Sher

On Thu, Feb 25, 2010 at 7:15 PM, John Kalucki j...@twitter.com wrote:

 Yes, this is indeed what you should be doing. If you have a low tolerance
 for data loss, you will then use a total of four accounts: 2 elevated and 2
 default access accounts. If you can tolerate a few missing tweets on each
 reconnect, you can just use the two elevated accounts.

 -John Kalucki

 http://twitter.com/jkalucki
 Infrastructure, Twitter Inc.


 On Thu, Feb 25, 2010 at 2:06 AM, Alam Sher alamshe...@gmail.com wrote:

 So in case, if I have 20K users and I have to, say track 60K keywords
 for them + also have to follow all of them. I should be applying for 2
 higher access accounts one for track predicates and other for follow
 predicate. Does this make sense?

 Thanks,

 On Feb 25, 8:44 am, John Kalucki j...@twitter.com wrote:
  This technique works for updating any filter predicate. The count
 parameter
  should work on a shadow account. It won't work on a default access
 account.
  We have a number of very large integrations using this technique with
  Birddog access -- it should scale down to Shadow access just fine.
 
  The documentation makes it clear which cases are supported and which
 ones
  are not:http://apiwiki.twitter.com/Streaming-API-Documentation#count
 
  The count parameter isn't supported on track streams for computational
  complexity reasons, and it isn't supported on the default access role
 for
  policy reasons.
 
  -John Kaluckihttp://twitter.com/jkalucki
  Infrastructure, Twitter Inc.
 
  On Wed, Feb 24, 2010 at 2:31 PM, Jonathan Strauss 
 
  jonat...@snowballfactory.com wrote:
   On Feb 24, 2:06 pm, John Kalucki j...@twitter.com wrote:
The documentation should be pretty clear on this topic. One main
   connection,
and perhaps an auxiliary connection to manage query velocity.
 
   Hey John,
 
   Do you recommend this kind of 2 connection setup for updating our user
   list when using the follow predicate?
 
   We've been trying unsuccessfully to use the count parameter when
   reconnecting to add new users to our follow list. I've found several
   oblique mentions of the count parameter only working in some cases,
   but no specifics on how or why.
 
   We currently have shadow role access for the TweetPo.st app. We're
   trying to update our Streaming API connection when new users signup
   for TweetPo.st without losing tweets for existing users during
   reconnect. Any suggestions on the best way to do this would be greatly
   appreciated.
 
   Thanks!
   -jonathan
 
   =
   Jonathan Strauss, Co-Founder
  http://snowballfactory.com
 
   Campaign tracking for social media -http://awe.sm
   A smarter way to update Facebook from Twitter -http://tweetpo.st
   Sharecount button for Facebook -http://www.fbshare.me





-- 
___
Alam Sher Khan
+92 331 505 5549


[twitter-dev] Streaming API Best Practice (Multiple Connections or Single)

2010-02-24 Thread Alam Sher
Hi,

What is the best practice if I have 20K twitter user base and I want
to track user's specific keywords via statuses/filter?

Should I distribute the processing on multiple nodes, lets say open a
streaming connection tracking keywords for 5K users each (on different
IPs or same IP with different authenticating users)?

Or just apply for a bigger access level and use a single connection to
get the whole thing.

Thanks,
Alam Sher