[twitter-dev] Re: Streaming API: Spritzer-stream coverage
On Tue, May 26, 2009 at 10:07 PM, elversatile elversat...@gmail.com wrote: Makes sense. I was assuming the same. Thanks people! John from Twitter said that spritzer is 1/3 of the gardenhose, which makes it 15%. So I guess statistical insignificance of spritzer is due to its low percentage. I'm also curious what statistical insignificance means in this context, since in the Streaming API docs they're pretty assiduous saying which are significant vs. insignificant. Sample sizes far lower than 4% are of course fine for certain purposes as long as they're drawn uniformly. And even if not all that uniform, they might still be good enough :) There are so many different things to do with *hose/spritzer I'm not sure what statistical significance means in the abstract. I'm seeing hundreds of thousands of messages per day on /spritzer. If you're interested in computing a statistic that holds across all tweets -- say, average tweet length -- that's *plenty*. (Now, if you wanted to compute the statistic per 1 minute time window and cared about minute-per-minute differences, the story might be different...) I'm curious to know what the docs author meant by statistically (in)significant here. Brendan [ http://anyall.org ]
[twitter-dev] Re: Search Twitter (Java, C#) - Language Preferences?
On Tue, May 26, 2009 at 5:32 AM, Merrows sa...@merrows.co.uk wrote: I have a system already written in C# and .NET which I started in 2003. I have been happy with using c# and .NET as it has a good class structure, and also Winforms works well for writing client-server applications. Recently, I have seen much less interest in C# from developers. I want to integrate search results from twitter into the current system and I am thinking of what languages to use. I have googled what language to use, and the limits of JSON and ATOM have placed some restrictions on what I can do. Especially, some developers have complained about performance issues using C# and .NET related to serialization of the data. C or C++ will be faster, but those are pretty much the only mainstream programming languages faster than C# and Java. Unless your C# JSON or XML/ATOM libraries are a bottleneck, which I doubt... -- Brendan O'Connor - http://anyall.org
[twitter-dev] Re: Search Twitter (Java, C#) - Language Preferences?
On May 26, 3:10 pm, Andrew Badera and...@badera.us wrote: The language you're using is going to be pretty agnostic to the performance of search.twitter.com. You're dealing with a loosely coupled architecture over an Internet WAN connection ... and nothing you do will change the base performance of search.twitter.com itself. The specific API you select could be an entirely different story, but with a RESTful API, most APIs are going to have a hard time making performance mistakes. If you have a lot of client-side processing, C# may be your best bet on a Windows x86 or x64 machine, with Java equal, or a close second. (Java's only faster on Java processors, and really only at scale.) Any interpreted languages are going to have a much harder time doing in-memory or I/O bound work with the same level of performance, if that's what you're after. Thanks- - Andy Badera - and...@badera.us - Google me:http://www.google.com/search?q=andrew+badera - This email is: [ ] bloggable [x] ask first [ ] private On Tue, May 26, 2009 at 8:32 AM, Merrows sa...@merrows.co.uk wrote: I have a system already written in C# and .NET which I started in 2003. I have been happy with using c# and .NET as it has a good class structure, and also Winforms works well for writing client-server applications. Recently, I have seen much less interest in C# from developers. I want to integrate search results from twitter into the current system and I am thinking of what languages to use. I have googled what language to use, and the limits of JSON and ATOM have placed some restrictions on what I can do. Especially, some developers have complained about performance issues using C# and .NET related to serialization of the data. Does anyone have any experience of Twitter API's and especially the search? If so, are there are machine performance issues, or issues with finding open source code?- Hide quoted text - - Show quoted text - Actually the efficiency arose from a blog. Apparently the blogger said many developers had complained about the slowness of C# code in using the search twitter api.
[twitter-dev] Obtaining a complete user feed
Hello Twitter Team, I was wondering whether there is a way, currently or planned, to obtain the complete twitterstream of one or multiple given users for data mining and backup purposes. It would be sufficient for me if I could request the data and would then, some time later, be notified that the data is available for download, it need not be live. Is there anything like this? -Matt
[twitter-dev] Re: To get User email id as given in the User Profile
hi all, Thanks for the immediate response :D Surya Sravanthi On May 26, 12:58 am, jmathai jmat...@gmail.com wrote: Don't hold your breath for that one :) On May 25, 6:59 am, sravs.. sravanthi.su...@gmail.com wrote: hi, I am a new user. can anyone tell me is there any way togetthe emailidof the user once the user has given access to a consumer application via oauth This is really urgent... Sravanthi
[twitter-dev] LINQ to Twitter v1.0 RTW
LINQ to Twitter, v1.0 is now RTW: http://linqtotwitter.codeplex.com/. LINQ to Twitter allows .NET developers who program in C# or VB to program Twitter applications using familiar LINQ syntax they are accustomed to. This is an open source project that comes with a full Visual Studio 2008 solution. I plan to keep LINQ to Twitter up-to-date as the Twitter API evolves and welcome new ideas and feature requests. I'd like to say a special thanks to the API developers at Twitter for doing such a great job. I see you folks working hard and providing awesome support to developers. I would love to hear from anyone who uses LINQ to Twitter in their own projects. Joe
[twitter-dev] Re: LINQ to Twitter v1.0 RTW
Nice. I might just have to play with this, will keep you posted. --ab On Wed, May 27, 2009 at 9:56 AM, Joe Mayo mayos...@gmail.com wrote: LINQ to Twitter, v1.0 is now RTW: http://linqtotwitter.codeplex.com/. LINQ to Twitter allows .NET developers who program in C# or VB to program Twitter applications using familiar LINQ syntax they are accustomed to. This is an open source project that comes with a full Visual Studio 2008 solution. I plan to keep LINQ to Twitter up-to-date as the Twitter API evolves and welcome new ideas and feature requests. I'd like to say a special thanks to the API developers at Twitter for doing such a great job. I see you folks working hard and providing awesome support to developers. I would love to hear from anyone who uses LINQ to Twitter in their own projects. Joe
[twitter-dev] Re: Streaming API: Spritzer-stream coverage
Folks, The significant/insignificant language currently isn't that important or clear, as we're preparing for future changes. The spritzer will likely remain a small public sample, the gardenhose will likely remain a larger sample that requires an EULA. The proportions, however, are subject to continuous change -- we want to provide a useful flow, but, at the same time, we don't want to incur excessive cost or overwhelm clients. Given our traffic growth, we will probably have to trim rates down -- few clients want a 5 mbit/sec spritzer feed. We haven't, yet, worked out a model for adjusting the sampling proportions. The sampling may be based on some public model of statistical significance, it may be driven by practical matters, by client requirements, some unknown factor, or some combination of them all. We're still measuring, analyzing, and reasoning about the Streaming API, and there's plenty we don't know just yet. -John Kalucki Services, Twitter Inc. On May 26, 11:55 pm, Brendan O'Connor breno...@gmail.com wrote: On Tue, May 26, 2009 at 10:07 PM, elversatile elversat...@gmail.com wrote: Makes sense. I was assuming the same. Thanks people! John from Twitter said that spritzer is 1/3 of the gardenhose, which makes it 15%. So I guess statistical insignificance of spritzer is due to its low percentage. I'm also curious what statistical insignificance means in this context, since in the Streaming API docs they're pretty assiduous saying which are significant vs. insignificant. Sample sizes far lower than 4% are of course fine for certain purposes as long as they're drawn uniformly. And even if not all that uniform, they might still be good enough :) There are so many different things to do with *hose/spritzer I'm not sure what statistical significance means in the abstract. I'm seeing hundreds of thousands of messages per day on /spritzer. If you're interested in computing a statistic that holds across all tweets -- say, average tweet length -- that's *plenty*. (Now, if you wanted to compute the statistic per 1 minute time window and cared about minute-per-minute differences, the story might be different...) I'm curious to know what the docs author meant by statistically (in)significant here. Brendan [http://anyall.org]
[twitter-dev] Re: Proposal: account_type property
Hmm, could definitely be of some use. Of course, with no policing it would not be entirely reliable, but I guess it could help in a number of different ways. The difficult part is classifying things, I would probably want a few more types 1. Personal - your standard user on twitter 2. Business - similar to personal, but represents a company 3. FeedBot - auto tweets from rss feed 4. Bot - auto tweets based off of some other sort of information stream 5. I'm sure there are more... On May 27, 10:17 am, MPS mpelzsher...@gmail.com wrote: I would like to propose an additional property on twitter accounts: account_type. The main purpose for this would be to distinguish personal vs. business accounts. This would be very useful for apps that want to target one or the other type of twitter account. Who's with me on this? :-) - Michael
[twitter-dev] Re: Whitelisted application still getting limited
Hi Miles, I just checked the list of whitelisting requests and I don't see you anywhere in it, either approved, rejected or pending. Please forward me your approval email (matt [at] twitter.com) and I'll track down where things went wrong. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 26, 2009, at 7:16 PM, jobtrain wrote: HI Matt, Thanks very much - the account name is @hashjobs Best, Miles On May 26, 1:32 pm, Matt Sanford m...@twitter.com wrote: Hi there, There is no known issue surrounding white listing. The most common cause for what you are describing is hosting providers that use NAT causing your requests to show up under a different IP address. If you provide the account screen name I can double check it is correctly white listed. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 26, 2009, at 9:55 AM,jobtrainwrote: Both my Twitter account and IP address were whitelisted, but I am still being limited. Nothing really changed after the whitelist update. I am getting limited in the amount that I can post updates, it's still at about 100/hour. Is this just a bug, or is it perhaps something that I am doing? Or has Twitter just been bogged down recently? Thanks!
[twitter-dev] Re: Whitelisted application still getting limited
Hi Matt, Thanks so much - just forwarded you the original email! On May 27, 11:05 am, Matt Sanford m...@twitter.com wrote: Hi Miles, I just checked the list of whitelisting requests and I don't see you anywhere in it, either approved, rejected or pending. Please forward me your approval email (matt [at] twitter.com) and I'll track down where things went wrong. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 26, 2009, at 7:16 PM, jobtrain wrote: HI Matt, Thanks very much - the account name is @hashjobs Best, Miles On May 26, 1:32 pm, Matt Sanford m...@twitter.com wrote: Hi there, There is no known issue surrounding white listing. The most common cause for what you are describing is hosting providers that use NAT causing your requests to show up under a different IP address. If you provide the account screen name I can double check it is correctly white listed. Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 26, 2009, at 9:55 AM,jobtrainwrote: Both my Twitter account and IP address were whitelisted, but I am still being limited. Nothing really changed after the whitelist update. I am getting limited in the amount that I can post updates, it's still at about 100/hour. Is this just a bug, or is it perhaps something that I am doing? Or has Twitter just been bogged down recently? Thanks!- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Proposal: account_type property
Sounds like a third party app to me. 2009/5/27 Adam Covati cov...@gmail.com Hmm, could definitely be of some use. Of course, with no policing it would not be entirely reliable, but I guess it could help in a number of different ways. The difficult part is classifying things, I would probably want a few more types 1. Personal - your standard user on twitter 2. Business - similar to personal, but represents a company 3. FeedBot - auto tweets from rss feed 4. Bot - auto tweets based off of some other sort of information stream 5. I'm sure there are more... On May 27, 10:17 am, MPS mpelzsher...@gmail.com wrote: I would like to propose an additional property on twitter accounts: account_type. The main purpose for this would be to distinguish personal vs. business accounts. This would be very useful for apps that want to target one or the other type of twitter account. Who's with me on this? :-) - Michael -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: Proposal: account_type property
Need to classify a twitter account? There's an app for that! ...maybe -Chad On Wed, May 27, 2009 at 11:26 AM, Abraham Williams 4bra...@gmail.com wrote: Sounds like a third party app to me. 2009/5/27 Adam Covati cov...@gmail.com Hmm, could definitely be of some use. Of course, with no policing it would not be entirely reliable, but I guess it could help in a number of different ways. The difficult part is classifying things, I would probably want a few more types 1. Personal - your standard user on twitter 2. Business - similar to personal, but represents a company 3. FeedBot - auto tweets from rss feed 4. Bot - auto tweets based off of some other sort of information stream 5. I'm sure there are more... On May 27, 10:17 am, MPS mpelzsher...@gmail.com wrote: I would like to propose an additional property on twitter accounts: account_type. The main purpose for this would be to distinguish personal vs. business accounts. This would be very useful for apps that want to target one or the other type of twitter account. Who's with me on this? :-) - Michael -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: Obtaining a complete user feed
Twitter has said in the pas they intend to make complete archives available. No idea what form they will actually happen in though. Some time in the future... 2009/5/27 Matthias Bauer moef...@gmail.com Hello Twitter Team, I was wondering whether there is a way, currently or planned, to obtain the complete twitterstream of one or multiple given users for data mining and backup purposes. It would be sufficient for me if I could request the data and would then, some time later, be notified that the data is available for download, it need not be live. Is there anything like this? -Matt -- Abraham Williams | http://the.hackerconundrum.com Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from San Francisco, California, United States
[twitter-dev] Re: Deprecation of following and notification elements
Has this been implemented? I'm getting results that seem to indicate so. Example: curl http://twitter.com/friendships/exists.json?user_a=spaztestuser_b=funkatron; true curl http://twitter.com/friendships/exists.json?user_a=funkatronuser_b=spaztest; true so those users are following each other. However, user info returned in an authenticated request shows following:0 (that's the integer zero) curl -k -u funkatron:## https://twitter.com/users/spaztest.json | prettyjson [...] following:0, [...] curl -k -u spaztest:perlsucks https://twitter.com/users/funkatron.json | prettyjson [...] following:0, [...] I believe that following is supposed to indicate of the authenticating user is following the requested user, but even if it's the other way around, it seems wrong. Am I missing something, though? -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On May 11, 5:18 pm, Doug Williams d...@twitter.com wrote: Issues 419 [1] and 474 [2] are very popular, in the painful kind of way. The defects report that methods returning user objects (see users/show for an example [3]) are returning incorrect or invalid values for the following element. The fix for this inconsistency is in fact non trivial [4]. The problem lies within the interaction of the application logic, caching layer and database design. The persistent data behind following and notification values are separate from the user data in our architecture, so to keep these elements valid in cache alongside user objects adds a large amount of complexity. Developers made it obvious that these data are a priority and we want to ensure they available. We also want to guarantee they are accurate and that performance remains good. Given the problems explained above, we are going to be making a number of changes to the API so that you can rely on the following or notification data. Deprecations: The following elements are to be removed from all returned user objects returned by the API: 1) following 2) notifications This deprecation will not occur until we finish the following: Additions: To continue to provide access to this data we will be creating a new method: Issue 532 [4] outlines the need to perform a mutual following lookup. We will use a method similar to that described in this issue to deliver following, followedby, notification and pending (in the case of protected users) data with a single call. We realize this change will cause an increase in API usage for some applications. Therefore we are going to increase the default API rate limit across the board. This should help absorb some of the costs for applications attempting to do interesting things with social graph data. The number will be somewhere between 101 and 200 calls but we still need to look at growth projections and current hardware capacity before settling on a definite number. We plan to begin work on this relatively soon with the fix coming in a few weeks. We do not have a planned ship date at this time but will communicate specifics with developers as they are determined. We anticipate the new number of calls and a documented schema for the new method will be made available before the new method ships. Please watch this thread and @twitterapi for the incremental details. 1.http://code.google.com/p/twitter-api/issues/detail?id=419 2.http://code.google.com/p/twitter-api/issues/detail?id=474 3.http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show 4.http://www.jamesshuggins.com/h/tek1/first_computer_bug_large.htm 5.http://code.google.com/p/twitter-api/issues/detail?id=532 Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw
[twitter-dev] Re: Deprecation of following and notification elements
Or, as I think slightly more clearly, perhaps this is an example of the inconsistency discussed in the OP. Sorry for the noise if that's the case. -- Ed Finkler http://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On May 27, 11:50 am, Ed Finkler funkat...@gmail.com wrote: Has this been implemented? I'm getting results that seem to indicate so. Example: curl http://twitter.com/friendships/exists.json?user_a=spaztestuser_b=fun...; true curl http://twitter.com/friendships/exists.json?user_a=funkatronuser_b=sp...; true so those users are following each other. However, user info returned in an authenticated request shows following:0 (that's the integer zero) curl -k -u funkatron:##https://twitter.com/users/spaztest.json| prettyjson [...] following:0, [...] curl -k -u spaztest:perlsuckshttps://twitter.com/users/funkatron.json| prettyjson [...] following:0, [...] I believe that following is supposed to indicate of the authenticating user is following the requested user, but even if it's the other way around, it seems wrong. Am I missing something, though? -- Ed Finklerhttp://funkatron.com Twitter:@funkatron AIM: funka7ron ICQ: 3922133 XMPP:funkat...@gmail.com On May 11, 5:18 pm, Doug Williams d...@twitter.com wrote: Issues 419 [1] and 474 [2] are very popular, in the painful kind of way. The defects report that methods returning user objects (see users/show for an example [3]) are returning incorrect or invalid values for the following element. The fix for this inconsistency is in fact non trivial [4]. The problem lies within the interaction of the application logic, caching layer and database design. The persistent data behind following and notification values are separate from the user data in our architecture, so to keep these elements valid in cache alongside user objects adds a large amount of complexity. Developers made it obvious that these data are a priority and we want to ensure they available. We also want to guarantee they are accurate and that performance remains good. Given the problems explained above, we are going to be making a number of changes to the API so that you can rely on the following or notification data. Deprecations: The following elements are to be removed from all returned user objects returned by the API: 1) following 2) notifications This deprecation will not occur until we finish the following: Additions: To continue to provide access to this data we will be creating a new method: Issue 532 [4] outlines the need to perform a mutual following lookup. We will use a method similar to that described in this issue to deliver following, followedby, notification and pending (in the case of protected users) data with a single call. We realize this change will cause an increase in API usage for some applications. Therefore we are going to increase the default API rate limit across the board. This should help absorb some of the costs for applications attempting to do interesting things with social graph data. The number will be somewhere between 101 and 200 calls but we still need to look at growth projections and current hardware capacity before settling on a definite number. We plan to begin work on this relatively soon with the fix coming in a few weeks. We do not have a planned ship date at this time but will communicate specifics with developers as they are determined. We anticipate the new number of calls and a documented schema for the new method will be made available before the new method ships. Please watch this thread and @twitterapi for the incremental details. 1.http://code.google.com/p/twitter-api/issues/detail?id=419 2.http://code.google.com/p/twitter-api/issues/detail?id=474 3.http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show 4.http://www.jamesshuggins.com/h/tek1/first_computer_bug_large.htm 5.http://code.google.com/p/twitter-api/issues/detail?id=532 Thanks, Doug -- Doug Williams Twitter Platform Supporthttp://twitter.com/dougw
[twitter-dev] Re: Whitelisted but being rate limited?
Hi there,
Whitelisting raises the various limits but it does not remove
them. It sounds like you may have reached the direct message limit for
whitelisted accounts.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 27, 2009, at 8:56 AM, jmathai wrote:
This morning an app of ours was rate limited when sending direct
messages. Here is the response we get from the API:
{request:/direct_messages/new.json,error:There was an error
sending your message: We know you have a lot to say, but you can only
send so many direct messages per day. (a href=http://
help.twitter.com/forums/10711/entries/15364click here/a for more
info.)}
Following the link: http://help.twitter.com/forums/10711/entries/15364
it says that being whitelisted should lift the limits.
Our IP address is 209.123.162.18. I don't have the original email
since I submitted it via the online form. But I did exchange emails
with @dougw and know that sent 100+ requests in under an hour earlier
this week.
[twitter-dev] Re: Whitelisted but being rate limited?
@wirah sent me:
http://apiwiki.twitter.com/FAQ#IkeephittingtheratelimitHowdoIgetmorerequestsperhour
On May 27, 9:06 am, jmathai jmat...@gmail.com wrote:
Ok...what exactly is that so we can program around it. I haven't seen
it in my searching.
On May 27, 9:01 am, Matt Sanford m...@twitter.com wrote:
Hi there,
Whitelisting raises the various limits but it does not remove
them. It sounds like you may have reached the direct message limit for
whitelisted accounts.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On May 27, 2009, at 8:56 AM, jmathai wrote:
This morning an app of ours was rate limited when sending direct
messages. Here is the response we get from the API:
{request:/direct_messages/new.json,error:There was an error
sending your message: We know you have a lot to say, but you can only
send so many direct messages per day. (a href=http://
help.twitter.com/forums/10711/entries/15364click here/a for more
info.)}
Following the link:http://help.twitter.com/forums/10711/entries/15364
it says that being whitelisted should lift the limits.
Our IP address is 209.123.162.18. I don't have the original email
since I submitted it via the online form. But I did exchange emails
with @dougw and know that sent 100+ requests in under an hour earlier
this week.
[twitter-dev] RSS rate limit
Is getting RSS feed using end point such as feed://twitter.com/statuses/friends_timeline/12345.rss subject to rate limiting also?
[twitter-dev] Re: search.rss
Hi Jonas, It is not safe to use and will go away at some point. It was added for questionable reasons and has never been linked to or documented. Having said that I don't remove it because people have changed .atom to .rss and started relying on it. Please don't use it since it has some known bugs and less data than the atom version (thank you RSS spec for not having a link with a rel attribute). Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 27, 2009, at 12:32 PM, Jonas wrote: Hi, I was using the search.atom command and just happened to try search.rss. I was surprised that this works because I didn't see it documented in the api docs. Is search.rss documented anywhere? Is it safe to use? I noticed two problem with search.rss. 1) When since= is empty the returned rss always contains a twitter:warning element. 2) When near= is not empty (for instance near=NYC) I always get a 406 http error. Thanks, Jonas
[twitter-dev] get alerts on topics in twitter
Hey guys, I found a free online tool called Trackle ( http://tinyurl.com/pd9rag ). It allows you to track Twitter for information on anything or anyone and receive alerts when a tweet appears. It's cool! Cheers, Steve
[twitter-dev] Re: search.rss
Matt, Okay, I'm switching back to search.atom. However, I still get an Invalid Parameter error when since= is not empty. Are all the parameters that are available to the search command also available to the search.atom command? Jonas On May 27, 3:41 pm, Matt Sanford m...@twitter.com wrote: Hi Jonas, It is not safe to use and will go away at some point. It was added for questionable reasons and has never been linked to or documented. Having said that I don't remove it because people have changed .atom to .rss and started relying on it. Please don't use it since it has some known bugs and less data than the atom version (thank you RSS spec for not having a link with a rel attribute). Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 27, 2009, at 12:32 PM, Jonas wrote: Hi, I was using the search.atom command and just happened to try search.rss. I was surprised that this works because I didn't see it documented in the api docs. Is search.rss documented anywhere? Is it safe to use? I noticed two problem with search.rss. 1) When since= is empty the returned rss always contains a twitter:warning element. 2) When near= is not empty (for instance near=NYC) I always get a 406 http error. Thanks, Jonas
[twitter-dev] Automatic Tweets?
Hey All, I've got a big question and just need a quick and dirty answer. I want to know if it possible to have our software send out tweets based on events. Quick back story: We currently have software that does point of sale, track timing, HR, financials, etc. for race tracks and kart tracks. I want to have our system send out a tweet any time there is a new lap record or top time of the day, or top overall times, etc. Is this something that's possible? I'm not a dev, but I want to go to my devs with as much info as possible when pitching the idea. Thanks for any help you can offer! CW
[twitter-dev] Re: search.rss
Hi Matt, I mistakenly wrote since= above when I meant to write near=. The following url should return tweets with 15 miles of nyc, but instead I get invalid parameter. http://search.twitter.com/search.atom?q=ands=phrase=ors=nots=tag=lang=enfrom=to=ref=near=nycwithin=15units=misince=until=rpp=10 Jonas On May 27, 4:28 pm, Matt Sanford m...@twitter.com wrote: Hi Jonas, Yes, they are. The since= parameter should not be required, can you share the URL you're getting the error from? Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 27, 2009, at 1:13 PM, Jonas wrote: Matt, Okay, I'm switching back to search.atom. However, I still get an Invalid Parameter error when since= is not empty. Are all the parameters that are available to the search command also available to the search.atom command? Jonas On May 27, 3:41 pm, Matt Sanford m...@twitter.com wrote: Hi Jonas, It is not safe to use and will go away at some point. It was added for questionable reasons and has never been linked to or documented. Having said that I don't remove it because people have changed .atom to .rss and started relying on it. Please don't use it since it has some known bugs and less data than the atom version (thank you RSS spec for not having a link with a rel attribute). Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 27, 2009, at 12:32 PM, Jonas wrote: Hi, I was using the search.atom command and just happened to try search.rss. I was surprised that this works because I didn't see it documented in the api docs. Is search.rss documented anywhere? Is it safe to use? I noticed two problem with search.rss. 1) When since= is empty the returned rss always contains a twitter:warning element. 2) When near= is not empty (for instance near=NYC) I always get a 406 http error. Thanks, Jonas
[twitter-dev] Re: search.rss
near is not supported in .rss, .atom, or .json feeds for search (is said so in the old API docs, not sure about new ones). You can use the geocode search operator in the query, though... Try this for new york: geocode:40.714550,-74.007124,15mi -Chad On Wed, May 27, 2009 at 4:35 PM, Jonas boxnumbe...@gmail.com wrote: Hi Matt, I mistakenly wrote since= above when I meant to write near=. The following url should return tweets with 15 miles of nyc, but instead I get invalid parameter. http://search.twitter.com/search.atom?q=ands=phrase=ors=nots=tag=lang=enfrom=to=ref=near=nycwithin=15units=misince=until=rpp=10 Jonas On May 27, 4:28 pm, Matt Sanford m...@twitter.com wrote: Hi Jonas, Yes, they are. The since= parameter should not be required, can you share the URL you're getting the error from? Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 27, 2009, at 1:13 PM, Jonas wrote: Matt, Okay, I'm switching back to search.atom. However, I still get an Invalid Parameter error when since= is not empty. Are all the parameters that are available to the search command also available to the search.atom command? Jonas On May 27, 3:41 pm, Matt Sanford m...@twitter.com wrote: Hi Jonas, It is not safe to use and will go away at some point. It was added for questionable reasons and has never been linked to or documented. Having said that I don't remove it because people have changed .atom to .rss and started relying on it. Please don't use it since it has some known bugs and less data than the atom version (thank you RSS spec for not having a link with a rel attribute). Thanks; – Matt Sanford / @mzsanford Twitter Dev On May 27, 2009, at 12:32 PM, Jonas wrote: Hi, I was using the search.atom command and just happened to try search.rss. I was surprised that this works because I didn't see it documented in the api docs. Is search.rss documented anywhere? Is it safe to use? I noticed two problem with search.rss. 1) When since= is empty the returned rss always contains a twitter:warning element. 2) When near= is not empty (for instance near=NYC) I always get a 406 http error. Thanks, Jonas
[twitter-dev] Re: Automatic Tweets?
Quick and Dirty answer: yes. Depending on your kart tracking software/system, there are tons of options to integrate sending a tweet based on events (as long as the software you use allows for it). Side note: this is a cool idea. /karting nerd -Chad On Wed, May 27, 2009 at 4:28 PM, Chris webbmotorspo...@gmail.com wrote: Hey All, I've got a big question and just need a quick and dirty answer. I want to know if it possible to have our software send out tweets based on events. Quick back story: We currently have software that does point of sale, track timing, HR, financials, etc. for race tracks and kart tracks. I want to have our system send out a tweet any time there is a new lap record or top time of the day, or top overall times, etc. Is this something that's possible? I'm not a dev, but I want to go to my devs with as much info as possible when pitching the idea. Thanks for any help you can offer! CW
[twitter-dev] Twitter may add location data to each tweet... What will the location data be?
I am working on an app that uses location data and this may change the way I design the app. Will it be WOEID? Latitude Longitude? GPS? Geo Tag? etc. This is of major interest to me.
[twitter-dev] Quick hack: using Twitter with Yahoo Placemaker to geolocate tweets
http://isithackday.com/hacks/placemaker/tweet-locations.php?user=codepo8 What do you think? I can put up a how-to if wanted. cheers Chris
[twitter-dev] UserIDs to UserName - in bulk
Is there a way to turn a list of UserIDs into User Name / Profile information in one web service call? or feed? Or for 8000 followers do I need to make 8000 follow up web service calls? Thanks, Matt
[twitter-dev] Re: Quick hack: using Twitter with Yahoo Placemaker to geolocate tweets
Hi Chris, Very nice! I'd be interested in a how-to. Jonas On Wed, May 27, 2009 at 8:04 PM, Christian Heilmann chris.heilm...@gmail.com wrote: http://isithackday.com/hacks/placemaker/tweet-locations.php?user=codepo8 What do you think? I can put up a how-to if wanted. cheers Chris
[twitter-dev] Re: lots of 404s?
Check out the content of the XML returned with the error you would see: hash request/users/show.xml?user_id=41714775/request errorUser has been suspended./error /hash Thanks, Doug -- Doug Williams Twitter Platform Support http://twitter.com/dougw On Wed, May 27, 2009 at 7:12 PM, Jeffrey Greenberg jeffreygreenb...@gmail.com wrote: I'm seeing alot of 404 failures... some are for users that are suspended and some are just failng. These are id's i'm getting from the social graph apise.g. this is failing: http://twitter.com/users/show.xml?user_id=41714775 here's some more from my logs: getuser failed: /33687642 - /33687642 get user httpstatus: 404 getuser failed: /37079194 - /37079194 get user httpstatus: 404 getuser failed: /37616625 - /37616625 get user httpstatus: 404 My site: www.tweettronics.com is whitelisted btw...
[twitter-dev] Re: UserIDs to UserName - in bulk
On Wed, May 27, 2009 at 8:32 PM, Brendan O'Connor breno...@gmail.com wrote: I've been wondering about the same thing, especially with the REST API's rate limit. I also wanted to dereference user id's from the Search API, where the tweet data objects don't have the big nested user info object like they do in the REST API (or at least *hose) Brendan Also, the ids aren't the same between REST API and Search API for historical reasons. -damon -- http://twitter.com/damon
[twitter-dev] Re: Quick hack: using Twitter with Yahoo Placemaker to geolocate tweets
On Wed, May 27, 2009 at 8:08 PM, Nancy M nmira...@gmail.com wrote: I do like the maps, but 50% error -- you would not possibly get on an airplane with that kind of error rate, would you? And I don't think I'd want to make decisions about my demographics on something with that error rate either. Why not take the IPS and bounce them against whois or something? This app isn't about that; it's about what places a person is talking about. You can't use their IP's, the point is to identify locations in the text of their tweets. (I asked whether the app was looking at the author's location to help disambiguate because i thought it could be used to improve accuracy; but this is hypothetical.) In defense of error rates, if the task is just to get a sense about what regions of the world someone tends to talk about, then something like a 10% or 20% error rate might be ok; and it was lower than that for Chris's and some of the other example twitter users the app was suggesting. But here's one case where errors are very bad. One thing I thought was great about the map UI was that you can see a flag all by itself out in mexico or something, and be curious what the person is saying about mexico, and click on it to see the message. If errors tend to be geographic outliers then they really hurt this use case since geographic outliers are easy to see and are interesting simply because they are unusual (oh, brendan's always boring and talks about california, but look, one time he talked about switzerland! oops, not really.) I think the issue with some of the errors the yahoo placemaker thing was making with my tweets is, is that it's not integrating very well prior information about how commonly those locations are talked about. I think scala is only rarely used to mean the switzerland canton, but is quite often used to mean the programming language; but placemaker is happy to use a rare, unlikely sense of scala here. -- Brendan O'Connor - http://anyall.org
