[twitter-dev] Re: Bulk user lookup 502s
Yes, I am dealing with the 502s by following up with a retry until it succeeds. I have not come across any that did not succeed after a second attempt. Just wanted to give the team a heads up. Not mission critical at this point for me. On Apr 2, 8:21 pm, jmathai jmat...@gmail.com wrote: In my experience you have to deal with 502s. I had a retry mechanism in place which would retry a request up to 3 times if a 5xx response was received. This was ≈ 6 months ago so I'm not sure the current state of affairs. On Apr 2, 11:47 am, iematthew matthew.dai...@ientryinc.com wrote: Sorry, I hit the reply to author accidentally on my last reply. Sounds like what's happening is a caching latency. I've set my script to do an exponential backoff on the errors starting at 4 seconds, but none of the attempts ever requires more than the 4 second delay. Until the Twitter team can figure out an optimization for this I'll just keep the number of IDs per call down to 50 or less. Thanks for your time! On Apr 2, 12:31 pm, Raffi Krikorian ra...@twitter.com wrote: i'm not sure the time between your calls is at issue, but rather the number of items you are looking at one time. we'll look into it. On Fri, Apr 2, 2010 at 9:11 AM, iematthew matthew.dai...@ientryinc.comwrote: I'm looking at updating some of my systems to use the new bulk user lookup method, but I'm getting a high rate of 502 returns in my testing when I try to do more than about 50 IDs per request. Even at 50 IDs per call with a 1 second delay between each (this is a white- listed account), I still received about 16% 502s returned. When I pushed it up to 100 the failure rate was almost 100%. Is this a temporary glitch in the system, or should I plan on keeping my processes throttled down as far as the number of IDs per call? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Twitter API question??
I know it's obvious, but have you tried looking here? http://apiwiki.twitter.com/Twitter-API-Documentation Best, Eelke On Apr 4, 12:06 pm, Stuart Chaney stuartchane...@gmail.com wrote: Hey guys, Long time PHP developer and am just getting into the twitter API. :) Quick question... How is this done?http://twitterholic.com/top100/followers/ Basically it is a list of twitter users sorted by the number of followers they have, thus showing the most popular twitterers.. Is it a database which is periodically updated or is their anyway to get this info from a request to the API? Any Ideas? Cheers, Stuart -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] How to show twitts of DC Sports would have a list like Redskins, Capitols etc
Hi friends, i am PHP developer, and i am just getting into twitter api . i have to show the latest first 20 twitts of Local Celebrities of some famous cities according their categories such as sport,music,literature etc how it possible beacse i reads tutorial from this link https://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search; but i am can't understand what i have to do exact so can able to show twitts as per my site requirement\ Pls help as soon as possible -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Twitter API question??
Twitterholic has such a huge cache of user profiles that they know who has the most followers and can call users/show periodically to keep the information up to date. http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Abraham On Sun, Apr 4, 2010 at 03:06, Stuart Chaney stuartchane...@gmail.comwrote: Hey guys, Long time PHP developer and am just getting into the twitter API. :) Quick question... How is this done? http://twitterholic.com/top100/followers/ Basically it is a list of twitter users sorted by the number of followers they have, thus showing the most popular twitterers.. Is it a database which is periodically updated or is their anyway to get this info from a request to the API? Any Ideas? Cheers, Stuart -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Bulk user lookup 502s
and thanks for the heads up - we're investigating this to see if it can e made more responsive when we're under load. On Apr 5, 2010, at 6:05 AM, iematthew matthew.dai...@ientryinc.com wrote: Yes, I am dealing with the 502s by following up with a retry until it succeeds. I have not come across any that did not succeed after a second attempt. Just wanted to give the team a heads up. Not mission critical at this point for me. On Apr 2, 8:21 pm, jmathai jmat...@gmail.com wrote: In my experience you have to deal with 502s. I had a retry mechanism in place which would retry a request up to 3 times if a 5xx response was received. This was ≈ 6 months ago so I'm not sure the current state of affairs. On Apr 2, 11:47 am, iematthew matthew.dai...@ientryinc.com wrote: Sorry, I hit the reply to author accidentally on my last reply. Sounds like what's happening is a caching latency. I've set my script to do an exponential backoff on the errors starting at 4 seconds, but none of the attempts ever requires more than the 4 second delay. Until the Twitter team can figure out an optimization for this I'll just keep the number of IDs per call down to 50 or less. Thanks for your time! On Apr 2, 12:31 pm, Raffi Krikorian ra...@twitter.com wrote: i'm not sure the time between your calls is at issue, but rather the number of items you are looking at one time. we'll look into it. On Fri, Apr 2, 2010 at 9:11 AM, iematthew matthew.dai...@ientryinc.comwrote: I'm looking at updating some of my systems to use the new bulk user lookup method, but I'm getting a high rate of 502 returns in my testing when I try to do more than about 50 IDs per request. Even at 50 IDs per call with a 1 second delay between each (this is a white- listed account), I still received about 16% 502s returned. When I pushed it up to 100 the failure rate was almost 100%. Is this a temporary glitch in the system, or should I plan on keeping my processes throttled down as far as the number of IDs per call? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Can't reset application's callback address
Before you delete your Twitter account try creating a new application. If the issue is reproducible you should file a bug report. http://code.google.com/p/twitter-api/issues/entry http://code.google.com/p/twitter-api/issues/entryAbraham On Sun, Apr 4, 2010 at 16:20, Jonathan Sachs jhsa...@jhsachs.com wrote: I'm trying to run the sample program that comes with the TwitterOAuth library. It's not working because when I registered my web as a Twitter API client, I mistyped the domain name. Twitter sends the OAuth token to an invalid URL, and the sample program never gets it. I corrected the URL in Twitter, but it's still sending the token to the old URL. I've tried everything possible on the client end to make it stop, including switching browsers and rebooting. Nothing helped. I'm going to delete and recreate my Twitter account, which should fix the problem, but my development work will probably require changing the URL several times, and I can't go through that each time. How can I make Twitter send the token to the right URL? -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Profile avatars with AWS S3 versioning
+1 --- Wynn Netherland blog: http://wynnnetherland.com twitter: pengwynn skype: pengwynn linkedin: http://linkedin.com/in/netherland On Feb 12, 10:02 pm, Abraham Williams 4bra...@gmail.com wrote: Now that Amazon S3 supports versioning couldn't profile avatars use static URLs and let browsers handle the caching with ETags? More info on S3 Versioning:http://goo.gl/CMch Abraham -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Profile avatars with AWS S3 versioning
There is now a petition going to get screen_name based profile_image_urls: http://act.ly/1vk Abraham On Fri, Feb 12, 2010 at 19:03, Andrew Badera and...@badera.us wrote: On Fri, Feb 12, 2010 at 10:02 PM, Abraham Williams 4bra...@gmail.com wrote: Now that Amazon S3 supports versioning couldn't profile avatars use static URLs and let browsers handle the caching with ETags? More info on S3 Versioning: http://goo.gl/CMch Abraham -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States +1 --ab -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Chirp is coming to San Francisco April 14 and 15
I look forward to meeting all you awesome developers there. Abraham On Mon, Apr 5, 2010 at 12:04, Doug Williams d...@twitter.com wrote: Hi all -- With only nine days left until Biz's opening speech, Chirp -- Twitter's first conference for developers -- is fast approaching! The two day event will be in San Francisco on April 14th and 15th. You can image how excited we are to have a conversation with everyone from the ecosystem in the same room. The conference opens at the Palace of Fine Arts from 9AM to 6PM on April 14th. The schedule features keynotes from Biz Stone, Ev Williams, Ryan Sarver, and Dick Costolo which include announcements and roadmap details. On April 14th at 7PM we all move to Fort Mason to start the Hack Day. Here is where everyone will have a chance to collaborate, meet other members of the ecosystem, and have the entire Twitter team on call to answer questions. After an Ignite session at 8PM on the night of the 14th, we'll leave the doors to Fort Mason open all night for developers who want to dig into their code or conversations. The content on April 15th will pick up at 10AM. The day includes breakout talks on technology, best practices, policy, design, and more. Additionally, we're hosting times for developers to meet with Twitter's designers, Legal team, Platform team, the EFF and others to get their individual questions answered. Even Ev and Biz are hosting an hour so everyone can meet the founders. We'll wrap the entire conference with a rockin' party later that night! We have more space at Fort Mason than the Palace of Fine Arts so last week we opened tickets for the Hack Day. There are still $140 Hack Day passes and a few full conference tickets left so if you would like to attend please head to http://chirp.twitter.com and register. We hope to see you there! Thanks, Doug http://twitter.com/dougw -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Chirp is coming to San Francisco April 14 and 15
Going to be off the hook. Geek style. Zac Bowling @zbowling On Mon, Apr 5, 2010 at 12:23 PM, Abraham Williams 4bra...@gmail.com wrote: I look forward to meeting all you awesome developers there. Abraham On Mon, Apr 5, 2010 at 12:04, Doug Williams d...@twitter.com wrote: Hi all -- With only nine days left until Biz's opening speech, Chirp -- Twitter's first conference for developers -- is fast approaching! The two day event will be in San Francisco on April 14th and 15th. You can image how excited we are to have a conversation with everyone from the ecosystem in the same room. The conference opens at the Palace of Fine Arts from 9AM to 6PM on April 14th. The schedule features keynotes from Biz Stone, Ev Williams, Ryan Sarver, and Dick Costolo which include announcements and roadmap details. On April 14th at 7PM we all move to Fort Mason to start the Hack Day. Here is where everyone will have a chance to collaborate, meet other members of the ecosystem, and have the entire Twitter team on call to answer questions. After an Ignite session at 8PM on the night of the 14th, we'll leave the doors to Fort Mason open all night for developers who want to dig into their code or conversations. The content on April 15th will pick up at 10AM. The day includes breakout talks on technology, best practices, policy, design, and more. Additionally, we're hosting times for developers to meet with Twitter's designers, Legal team, Platform team, the EFF and others to get their individual questions answered. Even Ev and Biz are hosting an hour so everyone can meet the founders. We'll wrap the entire conference with a rockin' party later that night! We have more space at Fort Mason than the Palace of Fine Arts so last week we opened tickets for the Hack Day. There are still $140 Hack Day passes and a few full conference tickets left so if you would like to attend please head to http://chirp.twitter.com and register. We hope to see you there! Thanks, Doug http://twitter.com/dougw -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Saving Access Tokens
the point of the access token is that an application can save it to access twitter APIs on behalf of a user. so, this is part of the use case. On Mon, Apr 5, 2010 at 12:31 PM, mac1175 mac1...@gmail.com wrote: Hi, I am create an application which is in two parts: the web application and the running service. What I would like to do is allow my service to read a users tweet after a user uses the web application to allow my service to do this. So, is it against TOS to save an access token for my service to access the user's data while they are offline (the user will be aware that this will be happening). Thanks. Mitch -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Current Trends
Hey Raffi, Baiscaily, the current trends, and even the daily trends, as I mentioned, this API call has a lot of noise/spam in it such as nowplaying, which always shows up as a trend... on the Twitter homepage, however, it looks like some of the non- relevant trends were removed from the list - for example nowplaying isn't currently showing up on the homepage of Twitter even though the API currently has nowplaying both in the current trends and daily trends call... thanks again for your time... On Apr 4, 2:34 pm, Raffi Krikorian ra...@twitter.com wrote: can you please be more specific? which API calls are you comparing to the homepage? On Fri, Apr 2, 2010 at 6:05 PM, ELB ebrit...@gmail.com wrote: The current list of 10 trends often has non-relevant trends such as nowplaying or FF . The new Twiitter homepage seems to remove these trends as it only shows more relevant trends. Will there be a new way in the API to get the current trends with some of the spam/non relevant replaced with trends that are more meaningful -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Current Trends
Have a look at the parameters section of trends/current for exclude=hashtags. Abraham On Mon, Apr 5, 2010 at 14:16, ELB ebrit...@gmail.com wrote: Hey Raffi, Baiscaily, the current trends, and even the daily trends, as I mentioned, this API call has a lot of noise/spam in it such as nowplaying, which always shows up as a trend... on the Twitter homepage, however, it looks like some of the non- relevant trends were removed from the list - for example nowplaying isn't currently showing up on the homepage of Twitter even though the API currently has nowplaying both in the current trends and daily trends call... thanks again for your time... On Apr 4, 2:34 pm, Raffi Krikorian ra...@twitter.com wrote: can you please be more specific? which API calls are you comparing to the homepage? On Fri, Apr 2, 2010 at 6:05 PM, ELB ebrit...@gmail.com wrote: The current list of 10 trends often has non-relevant trends such as nowplaying or FF . The new Twiitter homepage seems to remove these trends as it only shows more relevant trends. Will there be a new way in the API to get the current trends with some of the spam/non relevant replaced with trends that are more meaningful -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
On 04/05/2010 12:55 AM, Tim Haines wrote: This made me laugh. Hard. On Fri, Apr 2, 2010 at 6:47 AM, Dewald Pretorius dpr...@gmail.com wrote: Mark, It's extremely important where you have two bots that reply to each others' tweets. With incorrectly sorted tweets, you get conversations that look completely unnatural. On Apr 1, 1:39 pm, Mark McBride mmcbr...@twitter.com wrote: Just out of curiosity, what applications are you building that require sub-second sorting resolution for tweets? Yeah - my bot laughed too ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
To be fair to Taylor, we may be expecting too much from his role. When reading the job description of a Twitter Developer Advocate [1], the only traditional advocate responsibility listed there is Represent developer needs when planning new API features and changes. Now, if Taylor conveyed our objections to the Platform team, then he adequately executed that responsibility. I'm sure he did. The rest of the responsibilities all speak in a Twitter to Developer direction, i.e., more a Communicator than an Advocate. In particular, in the About This Job section, it says, it is necessary to have an official voice regularly communicating with the community, which underlines Communicator instead of Advocate. [1] http://dld.bz/7Z On Apr 4, 9:39 pm, funkatron funkat...@gmail.com wrote: Taylor, I'm about to vent. Sorry about this. At some point did you plan on addressing any of the numerous complaints raised against making this anything other than opt-in? Several of us raised this, and you offered no response for 10 days. See http://groups.google.com/group/twitter-development-talk/ browse_thread/thread/983086ae9935d50c/d4a8e0fbc0fee5c0? lnk=gstq=popular+search#d4a8e0fbc0fee5c0 When you *did* post, you didn't actually address any concerns, or say hey, I spoke with the API team. This is why it's going like this. Like, say, an advocate of 3rd party developers would do. I'm not doing Twitter any favors; I realize that. I'm just the developer of a tiny, old open source client whose been hacking away on the API since spring of 2007. I'm not a strategic partner, and I don't bring Twitter any value. No VC funding will be coming my way, I'm afraid, and it doesn't make headlines on TechCrunch when I add a new feature (ping.fm? I supported that in 2007). But what I would like is to be treated with some respect. If you post something, and get significant pushback, I'd expect at *very* least some explanation about why doing it the way you guys want to do it is a great idea. If you are an advocate for 3rd party developers, as I interpreted your title, then doing us the courtesy of not simply ignoring/avoiding the concerns we voice seems like part of your job. It seems like you're doing a lot of selling of changes to *us*. That's not an advocate -- that's an evangelist. If your role there is an evangelist, then fine. You're doing a good job of ignoring the tougher questions and sticking to company lines. The point here is that I used to cut the API crew a lot of slack because I thought they at least weren't feeding us a line. I felt they actually were aiming for transparency, but were just overworked. If this is the way things are gonna go with someone who is, presumably, tasked with being *our* advocate, I think Twitter is losing the thread. Maybe it doesn't matter for you guys financially, and you'll go on and do Very Important Things and lots of people will continue to view Twitter as Game-Changing Technology, but it sure is a bummer for me. -- Ed Finklerhttp://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 1, 8:53 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, As indicated a few weeks ago, we're launching our new *beta* enhancements to search.twitter.com and the Search API today -- it's currently rolling out to our servers. Thank you all for your feedback. *Key API Takeaways*: - During the current phase, receiving popular tweets in your API search results is *OPT-IN*. You will not see the new top results in search unless you specify the *result_typ**e* parameter on your search query string. - The result_type parameter takes one of three values: * *mixed* - receive both popular tweets and most recent tweets for the query. This is the equivalent of the future default behavior. * *popular* - receive only popular tweets for the query. * *recent* - receive only recent results for the query. This is the equivalent of the behavior you've come to expect until present - Each tweet in a search result will now contain a metadata node, with a field called 'result_type' that indicates whether the tweet is popular or recent. In the future, there may be other result_types. The metadata node will eventually contain other fields as well. - In addition to result_type, the metadata node may also include a 'recent_retweets' field indicating the number of retweets the tweet has received recently, rounded to a reasonable integer. - This metadata field will now appear in search results regardless of your OPT-IN status on the popular tweets feature. You don't have to do anything to receive this new metadata along with tweets in search results. In JSON, the metadata field is simply metadata. In XML, you'll see it expressed as twitter:metadata. *Continued Discussion*: To date, Twitter's real-time search has proven to be incredibly valuable.
[twitter-dev] Musings About Twitter Search (was Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available))
On 04/05/2010 09:47 AM, Dewald Pretorius wrote: +1 ^ 10. Very well said, Ed. You're getting an enthusiastic standing ovation and one-man Mexican wave from me. I think as a community, we're letting a golden opportunity for discussion about Twitter Search pass us by while we vent and rant about the inconveniences and about roles and titles. I'm not by any means an expert on search in the large, although I do spend a fair amount of time trying to keep up with the natural language processing and computational linear algebra technologies that power search. But I think the discussion we *should* be having is not about the mechanics of the API, the logistics of API versioning, developer best practices or roles withing the community. I don't even think it should be about business models, although that's certain a part of it. I think the discussion we should be having is about Twitter Search itself - how it should work to meet the needs of the two classes of users I call seekers and sellers. I posted a call for this discussion on my blog a while back, but haven't had many takers. So here it is again: http://borasky-research.net/2010/03/19/seeker-or-seller-what-do-you-think-about-adding-popularity-to-twitter-search-tweetsearchpop/ If there's enough interest, maybe we can put together an unconference session on this at Chirp. -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
to clarify (from my personal view), what taylor has provided to the team is a clear view into what developers want / think / feel -- basically, a pulse on the developer community. he's doing a fine job. and for these particular issues, not only has he conveyed the feelings of our community, but everybody on the team has also heard it personally. i hope we have more to say about both these topics soon. as you can all imagine, there is a myriad of moving pieces that we are all trying to get to align quickly -- there are technical issues, there are the concerns of our developer and user community, and then, of course, there are the overall objectives of Twitter, Inc. getting them all to align is, at times, ridiculously difficult. On Mon, Apr 5, 2010 at 5:01 PM, Dewald Pretorius dpr...@gmail.com wrote: To be fair to Taylor, we may be expecting too much from his role. When reading the job description of a Twitter Developer Advocate [1], the only traditional advocate responsibility listed there is Represent developer needs when planning new API features and changes. Now, if Taylor conveyed our objections to the Platform team, then he adequately executed that responsibility. I'm sure he did. The rest of the responsibilities all speak in a Twitter to Developer direction, i.e., more a Communicator than an Advocate. In particular, in the About This Job section, it says, it is necessary to have an official voice regularly communicating with the community, which underlines Communicator instead of Advocate. [1] http://dld.bz/7Z On Apr 4, 9:39 pm, funkatron funkat...@gmail.com wrote: Taylor, I'm about to vent. Sorry about this. At some point did you plan on addressing any of the numerous complaints raised against making this anything other than opt-in? Several of us raised this, and you offered no response for 10 days. See http://groups.google.com/group/twitter-development-talk/ browse_thread/thread/983086ae9935d50c/d4a8e0fbc0fee5c0? lnk=gstq=popular+search#d4a8e0fbc0fee5c0 When you *did* post, you didn't actually address any concerns, or say hey, I spoke with the API team. This is why it's going like this. Like, say, an advocate of 3rd party developers would do. I'm not doing Twitter any favors; I realize that. I'm just the developer of a tiny, old open source client whose been hacking away on the API since spring of 2007. I'm not a strategic partner, and I don't bring Twitter any value. No VC funding will be coming my way, I'm afraid, and it doesn't make headlines on TechCrunch when I add a new feature (ping.fm? I supported that in 2007). But what I would like is to be treated with some respect. If you post something, and get significant pushback, I'd expect at *very* least some explanation about why doing it the way you guys want to do it is a great idea. If you are an advocate for 3rd party developers, as I interpreted your title, then doing us the courtesy of not simply ignoring/avoiding the concerns we voice seems like part of your job. It seems like you're doing a lot of selling of changes to *us*. That's not an advocate -- that's an evangelist. If your role there is an evangelist, then fine. You're doing a good job of ignoring the tougher questions and sticking to company lines. The point here is that I used to cut the API crew a lot of slack because I thought they at least weren't feeding us a line. I felt they actually were aiming for transparency, but were just overworked. If this is the way things are gonna go with someone who is, presumably, tasked with being *our* advocate, I think Twitter is losing the thread. Maybe it doesn't matter for you guys financially, and you'll go on and do Very Important Things and lots of people will continue to view Twitter as Game-Changing Technology, but it sure is a bummer for me. -- Ed Finklerhttp://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.comxmpp%3afunkat...@gmail.com On Apr 1, 8:53 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, As indicated a few weeks ago, we're launching our new *beta* enhancements to search.twitter.com and the Search API today -- it's currently rolling out to our servers. Thank you all for your feedback. *Key API Takeaways*: - During the current phase, receiving popular tweets in your API search results is *OPT-IN*. You will not see the new top results in search unless you specify the *result_typ**e* parameter on your search query string. - The result_type parameter takes one of three values: * *mixed* - receive both popular tweets and most recent tweets for the query. This is the equivalent of the future default behavior. * *popular* - receive only popular tweets for the query. * *recent* - receive only recent results for the query. This is the equivalent of the behavior you've come
[twitter-dev] Re: Musings About Twitter Search (was Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available))
On Apr 5, 6:01 pm, Dewald Pretorius dpr...@gmail.com wrote: Ed, Yes, we should talk abour Search. But, I disagree when you say we should not talk about the other stuff. It is very frustrating when developers essentially stand up as one man and tell Twitter, bad idea, don't do it. And they go ahead and do it anyway. You know, it's not like we are their primary customers and consumers of the API. It would be extremely alarming and troubling if they ignored those guys. Well, I don't think that the hundreds / thousands of developers stood up as one man. There wasn't a poll, and there wasn't anything except truth by loudness or truth by repetition. Yes, I personally think major API changes add unnecessary work to a developer's schedule, but I don't think that's as big a problem for Twitter and the developer community as not having a search that meets the needs of seekers and sellers. And I'm not terribly convinced that either the old or new Twitter Search *does* meet the needs of seekers or sellers, because a. Twitter Search isn't the focus of my own use cases, so I wouldn't personally know if it was broken, and b. The blogosphere seems more interested in juicy gossip, the iPad, Facebook privacy, Google vs. China, lawsuits in the mobile space, Foursquare vs. Gowalla, etc. If Twitter comes up at all, it's in reference to Twitter's business model or speculation on growth rates. Twitter Search seems to be low on their list of things to think / talk about. But yes, we should talk about the other stuff. It *is* an inconvenience, and even in agile / scrum shops there are strict rules about change control and change management. That shouldn't be even a discussion topic - it should be something that's in-bred in people who've been working with code for more than six months. We should talk about it, but at the same time, we shouldn't *have* to talk about it. ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now a
to clarify (from my personal view), what taylor has provided to the team is a clear view into what developers want / think / feel -- basically, a pulse on the developer community. he's doing a fine job. and for these particular issues, not only has he conveyed the feelings of our community, but everybody on the team has also heard it personally. i hope we have more to say about both these topics soon. as you can all imagine, there is a myriad of moving pieces that we are all trying to get to align quickly -- there are technical issues, there are the concerns of our developer and user community, and then, of course, there are the overall objectives of Twitter, Inc. getting them all to align is, at times, ridiculously difficult. I appreciate all of that, but the particular issue at hand is only emblematic of what I worry is a greater problem. If nothing else, a message to the list simply saying we're aware you guys don't like it, but we're doing it anyway and here is why would have at least won style points and would have reinforced that you're listening. It's your basketball court, so of course you get to decide how the game is played, but it would be nice to tell the players. (Well, okay, that metaphor gets overused during March Madness.) Seriously, there wasn't a single response back about that from anyone on the API team, and it wasn't for lack of asking. No one would have liked it, but acknowledgment of concerns even without being able to act on them goes a long way. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- It's lonely at the top, but the food is better. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Raffi, one of the things that really stands out for me in what you are saying here is that there are lots of moving pieces that the team is trying to align quickly. The question is, who and what is dictating the schedule? I get the sense that all the recent changes are parts of a bigger picture plan for Twitter, but the reality is that Twitter HQ has not conveyed a real sense of this bigger picture to the developer community - and it certainly hasn't conveyed why these recent changes need to align quickly. So inevitably the situation at hand seems to be that some serious developer concerns effectively need to be pushed aside in order to meet some internal goals of Twitter that have not been made public. I can understand that as a choice that Twitter management might make. What I think would be unreasonable would be for Twitter to expect the developer community to not push back. I think it's pretty clear that the developer advocate concept needs to be fleshed out more, and i'll try to push for that at Chirp. If anyone else is interested in helping make that discussion productive, lets get started :-) On Apr 5, 8:45 pm, Raffi Krikorian ra...@twitter.com wrote: to clarify (from my personal view), what taylor has provided to the team is a clear view into what developers want / think / feel -- basically, a pulse on the developer community. he's doing a fine job. and for these particular issues, not only has he conveyed the feelings of our community, but everybody on the team has also heard it personally. i hope we have more to say about both these topics soon. as you can all imagine, there is a myriad of moving pieces that we are all trying to get to align quickly -- there are technical issues, there are the concerns of our developer and user community, and then, of course, there are the overall objectives of Twitter, Inc. getting them all to align is, at times, ridiculously difficult. On Mon, Apr 5, 2010 at 5:01 PM, Dewald Pretorius dpr...@gmail.com wrote: To be fair to Taylor, we may be expecting too much from his role. When reading the job description of a Twitter Developer Advocate [1], the only traditional advocate responsibility listed there is Represent developer needs when planning new API features and changes. Now, if Taylor conveyed our objections to the Platform team, then he adequately executed that responsibility. I'm sure he did. The rest of the responsibilities all speak in a Twitter to Developer direction, i.e., more a Communicator than an Advocate. In particular, in the About This Job section, it says, it is necessary to have an official voice regularly communicating with the community, which underlines Communicator instead of Advocate. [1]http://dld.bz/7Z On Apr 4, 9:39 pm, funkatron funkat...@gmail.com wrote: Taylor, I'm about to vent. Sorry about this. At some point did you plan on addressing any of the numerous complaints raised against making this anything other than opt-in? Several of us raised this, and you offered no response for 10 days. See http://groups.google.com/group/twitter-development-talk/ browse_thread/thread/983086ae9935d50c/d4a8e0fbc0fee5c0? lnk=gstq=popular+search#d4a8e0fbc0fee5c0 When you *did* post, you didn't actually address any concerns, or say hey, I spoke with the API team. This is why it's going like this. Like, say, an advocate of 3rd party developers would do. I'm not doing Twitter any favors; I realize that. I'm just the developer of a tiny, old open source client whose been hacking away on the API since spring of 2007. I'm not a strategic partner, and I don't bring Twitter any value. No VC funding will be coming my way, I'm afraid, and it doesn't make headlines on TechCrunch when I add a new feature (ping.fm? I supported that in 2007). But what I would like is to be treated with some respect. If you post something, and get significant pushback, I'd expect at *very* least some explanation about why doing it the way you guys want to do it is a great idea. If you are an advocate for 3rd party developers, as I interpreted your title, then doing us the courtesy of not simply ignoring/avoiding the concerns we voice seems like part of your job. It seems like you're doing a lot of selling of changes to *us*. That's not an advocate -- that's an evangelist. If your role there is an evangelist, then fine. You're doing a good job of ignoring the tougher questions and sticking to company lines. The point here is that I used to cut the API crew a lot of slack because I thought they at least weren't feeding us a line. I felt they actually were aiming for transparency, but were just overworked. If this is the way things are gonna go with someone who is, presumably, tasked with being *our* advocate, I think Twitter is losing the thread. Maybe it doesn't matter for you guys financially, and you'll go on and do
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now a
consider this an acknowledgement and a response, then :P these are two pretty big issues (tweet IDs and popular tweets in search). and the silence has been because we're working really hard behind the scenes to make sure we, ourselves, have weighed all the options on the axes i laid out, and we feel, given that, that we got it right. we heard all the concerns and we know that change, especially sizable change, can be painful for all. once we have things finalized, we will definitely be messaging it to the list. On Mon, Apr 5, 2010 at 8:17 PM, Cameron Kaiser spec...@floodgap.com wrote: to clarify (from my personal view), what taylor has provided to the team is a clear view into what developers want / think / feel -- basically, a pulse on the developer community. he's doing a fine job. and for these particular issues, not only has he conveyed the feelings of our community, but everybody on the team has also heard it personally. i hope we have more to say about both these topics soon. as you can all imagine, there is a myriad of moving pieces that we are all trying to get to align quickly -- there are technical issues, there are the concerns of our developer and user community, and then, of course, there are the overall objectives of Twitter, Inc. getting them all to align is, at times, ridiculously difficult. I appreciate all of that, but the particular issue at hand is only emblematic of what I worry is a greater problem. If nothing else, a message to the list simply saying we're aware you guys don't like it, but we're doing it anyway and here is why would have at least won style points and would have reinforced that you're listening. It's your basketball court, so of course you get to decide how the game is played, but it would be nice to tell the players. (Well, okay, that metaphor gets overused during March Madness.) Seriously, there wasn't a single response back about that from anyone on the API team, and it wasn't for lack of asking. No one would have liked it, but acknowledgment of concerns even without being able to act on them goes a long way. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- It's lonely at the top, but the food is better. -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
- Raffi Krikorian ra...@twitter.com wrote: • popular tweets in search - twitter is increasingly being relied upon to be the place for relevant real-time information. most end-users would say that a time indexed search stream is not as valuable. as you all can probably tell, keeping a real time search index operational is hard enough, but imagine keeping a service running that is simultaneously delivering relevant results along with time indexed results. that's significantly harder. Ah, see, *this* is the conversation *I* want! ;-) For example, search marketing is a well-established branch of online marketing, and both Google and Microsoft provide tools for marketers that tell them what people search for. Microsoft even provides tools that do a half-way decent job of distinguishing between people who are just looking and people who are searching with commercial intention. They also measure this internally and use it to tweak their indexing algorithms so they balance the needs of the seekers and the sellers. Maybe it's on Twitter's road map to provide Twitter Search Keyword Tools, and then again, maybe it isn't. Maybe Twitter doesn't want to be a search marketing platform. ;-) All I'm saying is that it isn't just a technical problem - if your data say that Twitter Search users - seekers, since there don't appear to be provisions for sellers yet - that popularity is how they want to rank tweets, and by extension, tweeters, for relevance, then that's what you should go with. Because the third-party monitoring outfits have migrated or will migrate to Streaming and will do the indexing their clients require. And they'll pay Twitter for the access levels they need to meet their clients' requirements. And if you don't *have* data, well ... ;-) -- To unsubscribe, reply using remove me as the subject.
