[twitter-dev] xAuth
So, I received the xAuth green light. Yeah!!! Unfortunately, the email was not very detailed about which app was enabled (I have 3). (and for the record I was very detailed in my request about which one I was requesting access for). So I gave it a shot. No dice. Seems to behave the same way as yesterday. So, now I've tried all three of my registered app credentials, just in case. Same 401 result. I've tried changing all the switches on the Twitter App configuration page. Then on all thee apps. Nope. Nope. Nope. Should the xauth parms be included in the base string for generating the signature? My guess is yes, but I couldn't find anything very conclusive after scouring the oauth spec and the xauth paper. I've tried both -- with all my apps -- with all the switches. Nope ^ 4. The number of ambiguous variables is pretty large here. Would anyone on the api team like to throw me a bone and tell me: - which app they enabled? - if there are specific settings on the App page that should be set or not set? (Client or Web? Login with Twitter?) - i'd really love to know the specifics about the xauth params and the signature. i'm sure it's in some doc somewhere -- a link to a page in a doc would be super. Just nailing down a few of those combinations will make the debug process a lot smoother. Currently I'm using an implementation that works very well pre-xauxth and is successfully getting request tokens without any problems. If I switch it over to PIN mode things seem to work well for all three apps of my Twitter apps. It generates the required headers, and exchanges request tokens for oauth tokens reliably. Unfortunately the error messages aren't very interesting: 401: Unauthorized. feel free to email for more techy details. i've got loads. ;-) isaiah http://twitter.com/isaiah
Re: [twitter-dev] retweets_of_me
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)
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
Re: [twitter-dev] xAuth
Like a n00b, I didn't include the id of my app in my original support request (I hadn't registered it since I wasn't using oAuth previously) and so it looks like I've missed the initial boat :( Got a message back asking for my app id so I registered Feathers and got back to the ticket but apparently the Twitter helpdesk/zendesk is down (http://help.twitter.comhttp://help.twitter.com/tickets/863920) so not sure if my ticket was updated. Would really appreciate it if anyone can look into the ticket (Ticket #863920 http://help.twitter.com/tickets/863920) Thanks :) Aral On Sat, Feb 27, 2010 at 6:47 AM, Isaiah Carew isa...@me.com wrote: So, I received the xAuth green light. Yeah!!! Unfortunately, the email was not very detailed about which app was enabled (I have 3). (and for the record I was very detailed in my request about which one I was requesting access for). snip
[twitter-dev] Search with API
Does anybody know how I can search Twitter with the API where every result has my search term at the beginning of the tweet. For example, I want to search for the term Bob at the beginning of every tweet, like this: - Bob is the best. - Bob is cool. - Bob likes food. I don't want it to return results where Bob is anywhere though, so I DON'T want results like this: - There is a guy named Bob. - I met Bob and he is nice. Any help would be very much appreciated. Thanks.
[twitter-dev] how can i save user's data at the time of Oauth?
Hi, My app uses Oauth.When user does Oauth I need to save user's data at least user-name in database. how can i do it. Can anybody help me out here? Thank You in advance. From Rushikesh.
[twitter-dev] Re: Post List members API with OAuth does not work.
Thanks for your reply Abraham. It did not work either.. Hmm.. I tried with parameter, only path and only parameter.. but none of them did work. It is happening on just post list members API only. In other cases, it works well. Hmm... isn't there any server-side problem? On 2월27일, 오전4시11분, Abraham Williams 4bra...@gmail.com wrote: Drop the list_id parameter as it is already included in the path and make sure you are authenticating as tweettimetest. Abraham On Fri, Feb 26, 2010 at 10:26, Caizer cai...@gmail.com wrote: Hi, I'm trying to add user to a list via List API. I am using OAuth authentication, and other list APIs worked perfectly with OAuth. I tried Get lists, Post lists, Delete list id... in same way. And they just work great. By the way.. whenever I try 'Post List members' API via OAuth, and it keeps saying 401 error. Followings are what I've tried and got from twitter. I am tried to add user '55925738' to list named 'another' of 'tweettimetest'. I used 'http://api.twitter.com/1/tweettimetest/another/members.json' to add user. And its parameter was list_id, and id. Did I do something wrong? Is there anyone who have similar issues? POST /1/tweettimetest/another/members.json?id=55925738 HTTP/1.1 Host: api.twitter.com User-Agent: TweetTime/2.3 CFNetwork/459 Darwin/10.2.0 X-Twitter-Client: TweetTime X-Twitter-Client-Version: 2.2 X-Twitter-Client-Url:http://caizer.com Authorization: OAuth realm=, oauth_consumer_key=r***, oauth_token=86***, oauth_signature_method=HMAC- SHA1, oauth_signature=KC***, oauth_timestamp=1267207930, oauth_nonce=4***, oauth_version=1.0, oauth_verifier=2280 Accept: */* Accept-Language: en-us Accept-Encoding: gzip, deflate Content-Type: application/x-www-form-urlencoded Content-Length: 17 Connection: keep-alive ?source=TweetTimeHTTP/1.1 401 Unauthorized Date: Fri, 26 Feb 2010 18:12:11 GMT Server: hi WWW-Authenticate: Basic realm=Twitter API Status: 401 Unauthorized Content-Type: application/json; charset=utf-8 Cache-Control: no-cache, max-age=300 Set-Cookie: guest_id=1267207932049; path=/ Set-Cookie: _twitter_sess=***o6Rmxhc2g6OkZ***25 3D--1164b91ac812d85***4; domain=.twitter.com; path=/ Expires: Fri, 26 Feb 2010 18:17:11 GMT Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 110 Connection: close POST /1/tweettimetest/another/members.json?list_id=another? id=55925738 HTTP/1.1 Host: api.twitter.com User-Agent: TweetTime/2.3 CFNetwork/459 Darwin/10.2.0 X-Twitter-Client: TweetTime X-Twitter-Client-Version: 2.2 X-Twitter-Client-Url:http://caizer.com Authorization: OAuth realm=, oauth_consumer_key=r***, oauth_token=86***, oauth_signature_method=HMAC- SHA1, oauth_signature=KC***, oauth_timestamp=1267207930, oauth_nonce=4***, oauth_version=1.0, oauth_verifier=2280 Accept: */* Accept-Language: en-us Accept-Encoding: gzip, deflate Content-Type: application/x-www-form-urlencoded Content-Length: 17 Connection: keep-alive ?source=TweetTimeHTTP/1.1 401 Unauthorized Date: Fri, 26 Feb 2010 18:18:11 GMT Server: hi Status: 401 Unauthorized WWW-Authenticate: Basic realm=Twitter API Content-Type: application/json; charset=utf-8 Cache-Control: no-cache, max-age=300 Set-Cookie: _twitter_sess=***o6Rmxhc2g6OkZ***25 3D--1164b91ac812d85***4; domain=.twitter.com; path=/ Expires: Fri, 26 Feb 2010 18:23:11 GMT Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 122 Connection: close POST /1/tweettimetest/another/members.json HTTP/1.1 Host: api.twitter.com User-Agent: TweetTime/2.3 CFNetwork/459 Darwin/10.2.0 X-Twitter-Client: TweetTime X-Twitter-Client-Version: 2.2 X-Twitter-Client-Url:http://caizer.com Authorization: OAuth realm=, oauth_consumer_key=r***, oauth_token=86***, oauth_signature_method=HMAC- SHA1, oauth_signature=KC***, oauth_timestamp=1267207930, oauth_nonce=4***, oauth_version=1.0, oauth_verifier=2280 Accept: */* Accept-Language: en-us Accept-Encoding: gzip, deflate Content-Type: application/x-www-form-urlencoded Content-Length: 17 Connection: keep-alive ?source=TweetTimeHTTP/1.1 400 Bad Request Date: Fri, 26 Feb 2010 18:22:25 GMT Server: hi X-Transaction: 1267208545-10948-19469 Status: 400 Bad Request Last-Modified: Fri, 26 Feb 2010 18:22:25 GMT X-Runtime: 0.05457 Content-Type: application/json; charset=utf-8 Pragma: no-cache Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Expires: Tue, 31 Mar 1981 05:00:00 GMT
Re: [twitter-dev] xAuth
i did manage to get xauth working this morning thanks to @SteveReynolds. the big epiphany (Steve's, not mine) was that there is no token exchange at all. in fact you don't even seem to need to acquire a request token ever. you simply jump directly to the auth token request and pass in your default token. it seems to make sense to me now, it was just a leap that i didn't make on my own. i just thought i'd post this in case anyone else out there is stuck too. when it's a bit more cleaned up, i'll post my results to github. isaiah http://twitter.com/isaiah On Feb 27, 2010, at 9:37 AM, Aral Balkan wrote: Like a n00b, I didn't include the id of my app in my original support request (I hadn't registered it since I wasn't using oAuth previously) and so it looks like I've missed the initial boat :( Got a message back asking for my app id so I registered Feathers and got back to the ticket but apparently the Twitter helpdesk/zendesk is down (http://help.twitter.com) so not sure if my ticket was updated. Would really appreciate it if anyone can look into the ticket (Ticket #863920) Thanks :) Aral On Sat, Feb 27, 2010 at 6:47 AM, Isaiah Carew isa...@me.com wrote: So, I received the xAuth green light. Yeah!!! Unfortunately, the email was not very detailed about which app was enabled (I have 3). (and for the record I was very detailed in my request about which one I was requesting access for). snip
Re: [twitter-dev] xAuth
if you all have suggestions for how to make the docs cleaner and more explicit on the wiki to prevent confusion - just respond to this thread On Sat, Feb 27, 2010 at 11:45 AM, Isaiah Carew isa...@me.com wrote: i did manage to get xauth working this morning thanks to @SteveReynolds. the big epiphany (Steve's, not mine) was that there is no token exchange at all. in fact you don't even seem to need to acquire a request token ever. you simply jump directly to the auth token request and pass in your default token. it seems to make sense to me now, it was just a leap that i didn't make on my own. i just thought i'd post this in case anyone else out there is stuck too. when it's a bit more cleaned up, i'll post my results to github. isaiah http://twitter.com/isaiah On Feb 27, 2010, at 9:37 AM, Aral Balkan wrote: Like a n00b, I didn't include the id of my app in my original support request (I hadn't registered it since I wasn't using oAuth previously) and so it looks like I've missed the initial boat :( Got a message back asking for my app id so I registered Feathers and got back to the ticket but apparently the Twitter helpdesk/zendesk is down (http://help.twitter.comhttp://help.twitter.com/tickets/863920) so not sure if my ticket was updated. Would really appreciate it if anyone can look into the ticket (Ticket #863920 http://help.twitter.com/tickets/863920) Thanks :) Aral On Sat, Feb 27, 2010 at 6:47 AM, Isaiah Carew isa...@me.com wrote: So, I received the xAuth green light. Yeah!!! Unfortunately, the email was not very detailed about which app was enabled (I have 3). (and for the record I was very detailed in my request about which one I was requesting access for). snip -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] how can i save user's data at the time of Oauth?
When you get an accounts access_token the screen_name and user_id are also returned. You can save those. Abraham On Sat, Feb 27, 2010 at 06:26, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi, My app uses Oauth.When user does Oauth I need to save user's data at least user-name in database. how can i do it. Can anybody help me out here? Thank You in advance. From Rushikesh. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Search with API
You will have to filter the results within your application. Abraham On Sat, Feb 27, 2010 at 10:00, rossfishkind rossfishk...@gmail.com wrote: Does anybody know how I can search Twitter with the API where every result has my search term at the beginning of the tweet. For example, I want to search for the term Bob at the beginning of every tweet, like this: - Bob is the best. - Bob is cool. - Bob likes food. I don't want it to return results where Bob is anywhere though, so I DON'T want results like this: - There is a guy named Bob. - I met Bob and he is nice. Any help would be very much appreciated. Thanks. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] TwitteRBL - Filtering SPAMs from Twitter
Hi, I'm currently using the streaming API for a new service I work on, but I see lots of tweets I would consider as SPAM and I'd like to find a way to prevent it. I have not found anything to filter them, therefor I wrote a little blog post about how it could be done. Something to combine RBL and Tweets, but I wonder if that makes sense. Any feedback welcome. http://blog.penso.info/2010/02/28/filtering-spams-on-twitter-twitterbl/ -- Fabien Penso @fabienpenso
[twitter-dev] Re: xAuth implemented in Perl Net::Twitter
* Marc Mims marc.m...@gmail.com [100226 17:36]: I have implemented xAuth in Perl Net::Twitter, but it is currently untested. I am waiting approval of an xAuth access request for one of my own OAuth apps so I can test it. Raffi gave me xAuth access to one of my own apps. After a minor code change, it works. I shipped a new release with xAuth support to CPAN. Coming to a mirror near you [1]. @semifor [1] http://search.cpan.org/~mmims/Net-Twitter-3.11007/
Re: [twitter-dev] Delete messages from the filter stream with location parameters??
Couldn't you add a cleaning process to statuses just before they are sent to clients but after they have been filtered into streams? The cleaning process could pick up delete flags and remove extraneous metadata from the status. Abraham On Fri, Feb 26, 2010 at 23:31, M. Edward (Ed) Borasky zzn...@gmail.comwrote: -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos Quoting Mark McBride mmcbr...@twitter.com: Yes, that's correct. We've considered adding more metadata to delete messages to make routing easier, but the privacy issues involved get tricky (if I delete something, do I *really* want the full text re-sent to a bunch of people?) Yeah - definitely tricky. The delete messages coming from sample only give the user_id and status_id, and I have to assume that the publish process doesn't send me a delete for a status that it didn't send to me. ;-) I suppose you could do the same for filter, but that would mean keeping track of all the tweets sent to *each* filter connection, not just one set of tweets like sample. That could get ugly since you can't predict / control how many filter connections you're going to get or how many tweets are going to be passed by the filter criteria. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: @twitterapi meetup @ Twitter HQ
On Feb 27, 1:00 am, Orian Marx (@orian) or...@orianmarx.com wrote: If TwitterHQ isn't opposed I'm sure there's someone who'd be willing to stream the event... ... recording would be cool too. and probably less hassle to do than streaming. rgds, Jaanus
Re: [twitter-dev] Delete messages from the filter stream with location parameters??
A user has essentially an infinite amount of time to delete a tweet he has sent. The sequence of events is a. User sends a tweet. b. Twitter forwards it to Streaming and inserts it into the Search indexing queue if the user is not blocked. c. User says at some point later, Oh crap - did I really say that? and deletes the tweet. d. Twitter deletes the tweet from Search and its other public-facing facilities, and sends a delete message with the deleted tweet's user and status IDs out to the *unfiltered* Streaming connections. I'm assuming it knows enough not to send all the firehose deletes to lower-frequency streams - it's none of sample's business what tweets got deleted from firehose or gardenhose. ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos Quoting Abraham Williams 4bra...@gmail.com: Couldn't you add a cleaning process to statuses just before they are sent to clients but after they have been filtered into streams? The cleaning process could pick up delete flags and remove extraneous metadata from the status. Abraham On Fri, Feb 26, 2010 at 23:31, M. Edward (Ed) Borasky zzn...@gmail.comwrote: -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos Quoting Mark McBride mmcbr...@twitter.com: Yes, that's correct. We've considered adding more metadata to delete messages to make routing easier, but the privacy issues involved get tricky (if I delete something, do I *really* want the full text re-sent to a bunch of people?) Yeah - definitely tricky. The delete messages coming from sample only give the user_id and status_id, and I have to assume that the publish process doesn't send me a delete for a status that it didn't send to me. ;-) I suppose you could do the same for filter, but that would mean keeping track of all the tweets sent to *each* filter connection, not just one set of tweets like sample. That could get ugly since you can't predict / control how many filter connections you're going to get or how many tweets are going to be passed by the filter criteria. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Search crossdomain.xml accidentally deleted again?
My flash application is currently getting security errors from search.twitter.com. It would appear the crossdomain.xml file no longer exists. This problem has happened before: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d3230be66c27c88e/ And while we're at it... has the Twitter team thought more about loosening the restrictions in their crossdomain.xml files so that Flash developers can actually access the api without using a php or similar proxy? I brought this issue up in October: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e35a708400b529b3/
Re: [twitter-dev] Delete messages from the filter stream with location parameters??
We could do so, but we have a dogmatic belief that Hosebird should remain middleware and that it should not render content. Well, except for limit messages. But, other than that, no rendering. Recently, we committed a major apostasy for an experiment, and re-rendered Tweets inside Hosebird on a non-public cluster. And then, Mark and I spent a whole day chasing down intermittent character encoding bugs. And we sucked half of the Infrastructure team down with us for a while too. On a deadline. And it still doesn't work quite right. This was not a good deal. That being said, I think I know how we could work this out. (Files a bug against himself.) We'll see. -John On Sat, Feb 27, 2010 at 4:53 PM, Abraham Williams 4bra...@gmail.com wrote: Couldn't you add a cleaning process to statuses just before they are sent to clients but after they have been filtered into streams? The cleaning process could pick up delete flags and remove extraneous metadata from the status. Abraham On Fri, Feb 26, 2010 at 23:31, M. Edward (Ed) Borasky zzn...@gmail.comwrote: -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos Quoting Mark McBride mmcbr...@twitter.com: Yes, that's correct. We've considered adding more metadata to delete messages to make routing easier, but the privacy issues involved get tricky (if I delete something, do I *really* want the full text re-sent to a bunch of people?) Yeah - definitely tricky. The delete messages coming from sample only give the user_id and status_id, and I have to assume that the publish process doesn't send me a delete for a status that it didn't send to me. ;-) I suppose you could do the same for filter, but that would mean keeping track of all the tweets sent to *each* filter connection, not just one set of tweets like sample. That could get ugly since you can't predict / control how many filter connections you're going to get or how many tweets are going to be passed by the filter criteria. -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Search crossdomain.xml accidentally deleted again?
My flash application is currently getting security errors from search.twitter.com. It would appear the crossdomain.xml file no longer exists. i still see it [ra...@tw-mbp13-raffi Desktop]$ wget http://search.twitter.com/crossdomain.xml --2010-02-27 20:29:27-- http://search.twitter.com/crossdomain.xml Resolving search.twitter.com... 168.143.162.59 Connecting to search.twitter.com|168.143.162.59|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 206 [application/xml] Saving to: `crossdomain.xml' 100%[=] 206 --.-K/s in 0s 2010-02-27 20:29:27 (16.4 MB/s) - `crossdomain.xml' saved [206/206] And while we're at it... has the Twitter team thought more about loosening the restrictions in their crossdomain.xml files so that Flash developers can actually access the api without using a php or similar proxy? yup. we have a few thing we want to make sure we do first, and then the plan is to loosen restrictions on api.twitter.com. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Streaming API Best Practice (Multiple Connections or Single)
Each developer will come to understand Fullness in a unique inner-directed manner. One might decide that exhausting the predicate list constitutes adequate Fullness. Another might decide that data loss becomes unacceptable at another point, perhaps due to the rapid cycling. A third might develop another Fullness heuristic. We should not judge their reasons, rather their reasoning and purity of motive. And their careful adherence to the connection guidelines, as offered in the Wiki of Truth. On Sat, Feb 27, 2010 at 5:14 AM, Alam Sher alamshe...@gmail.com wrote: 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.comwrote: 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
Re: [twitter-dev] TwitteRBL - Filtering SPAMs from Twitter
Hey, This sounds like a collaborative filtering problem. But rule based system alone might not be your best choice for such a dynamic environment like twitter. I would say if u can develop a bag of word approach to write a classifier and add that to your rule based system then u stand a good chance, I would assume. I would assume a few hours worth of tweets from Stream with classification done would serve a good training set for the algorithm. I do not have any empirical evidence as of now, but that my hunch about this. Regards, Atul. On Sat, Feb 27, 2010 at 6:29 PM, Fabien Penso fabienpe...@gmail.com wrote: Hi, I'm currently using the streaming API for a new service I work on, but I see lots of tweets I would consider as SPAM and I'd like to find a way to prevent it. I have not found anything to filter them, therefor I wrote a little blog post about how it could be done. Something to combine RBL and Tweets, but I wonder if that makes sense. Any feedback welcome. http://blog.penso.info/2010/02/28/filtering-spams-on-twitter-twitterbl/ -- Fabien Penso @fabienpenso -- Regards, Atul Kulkarni
