[twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15
Really excited to be in San Francisco (first time for me there) next week! Quite a long trip from Paris, but I just couldn't miss such an occasion to meet you all :) For those who would be interested, I made a little Chirp page on Twitoaster, threading Attendees' conversations in real time: http://twitoaster.com/twitter-chirp-conference/ See you (very) soon, Arnaud | @twitoaster | http://twitoaster.com On Apr 5, 9:04 pm, 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 tohttp://chirp.twitter.comand register. We hope to see you there! Thanks, Doug http://twitter.com/dougw -- 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, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.comwrote: 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
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
hi dewald. we obviously feel that users want the most relevant tweets first (the use of popular is unfortunate here). and the web interface of search.twitter.com has begun an evolution in that direction. it's still unclear what Twitter is going to do with the API (hence the silence), however, to go with your argument: time indexed search is, potentially, something a third party service could do. we do provide the streaming API to get much-better-than-search-real-time results. On Apr 6, 2010, at 4:28 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.comwrote: 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
[twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Raffi, We obviously feel that users want the most relevant tweets first. Has this been determined and confirmed with user focus groups, or is this just an opinion that originated somewhere in a Twitter office or meeting room? I am one of those users, and I have just told you that I have no interest in seeing old tweets, regardless of how popular or relevant they deem to be by your algorithms. When I search Twitter (and I'm making this statement as a user of search.twitter.com, not as an API consumer) I want to see in real-time what is happening right now. That is why I am using search.twitter.com and not google.com for that purpose. If you're going to rather show relevant tweets, then I will instead use Google because their matching algorithms are far more advanced and mature. On Apr 6, 9:47 am, Raffi Krikorian ra...@twitter.com wrote: hi dewald. we obviously feel that users want the most relevant tweets first (the use of popular is unfortunate here). and the web interface of search.twitter.com has begun an evolution in that direction. it's still unclear what Twitter is going to do with the API (hence the silence), however, to go with your argument: time indexed search is, potentially, something a third party service could do. we do provide the streaming API to get much-better-than-search-real-time results. On Apr 6, 2010, at 4:28 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.comwrote: 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
RE: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
But raffi why do you have to break the old to offer the new? Basically I've just updated MyPostButler to work again after your last unannounced changed the Thursday evening before a holiday break only to open my email this morning and see you are going to modify search api yet again in some undetermined period of time. I understand things need to change from time to time BUT why so often? Why cant you make the new changes opt-in rather than breaking all the previous applications already deployed out there. Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Raffi Krikorian Sent: Tuesday, 6 April 2010 8:48 AM To: twitter-development-talk@googlegroups.com Cc: Twitter Development Talk 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) hi dewald. we obviously feel that users want the most relevant tweets first (the use of popular is unfortunate here). and the web interface of search.twitter.com has begun an evolution in that direction. it's still unclear what Twitter is going to do with the API (hence the silence), however, to go with your argument: time indexed search is, potentially, something a third party service could do. we do provide the streaming API to get much-better-than-search-real-time results. On Apr 6, 2010, at 4:28 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.comwrote: 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
RE: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
I think twitter forget that API developers are there customers as well, not end users. At the end of the day if this make my app unviable then you'll lose this development community as a developer and pretty improbable to ever get us back. I've never funded another application on the Adobe FMS platform after they dropped the 10 seat license and killed the business I funded 7 months of development on. they are dead to me - should I really be adding Twitter to that list? anyone here still developing apps for Friendster? Yes Twitter it can happen that fast. Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Tuesday, 6 April 2010 9:12 AM To: Twitter Development Talk 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, We obviously feel that users want the most relevant tweets first. Has this been determined and confirmed with user focus groups, or is this just an opinion that originated somewhere in a Twitter office or meeting room? I am one of those users, and I have just told you that I have no interest in seeing old tweets, regardless of how popular or relevant they deem to be by your algorithms. When I search Twitter (and I'm making this statement as a user of search.twitter.com, not as an API consumer) I want to see in real-time what is happening right now. That is why I am using search.twitter.com and not google.com for that purpose. If you're going to rather show relevant tweets, then I will instead use Google because their matching algorithms are far more advanced and mature. On Apr 6, 9:47 am, Raffi Krikorian ra...@twitter.com wrote: hi dewald. we obviously feel that users want the most relevant tweets first (the use of popular is unfortunate here). and the web interface of search.twitter.com has begun an evolution in that direction. it's still unclear what Twitter is going to do with the API (hence the silence), however, to go with your argument: time indexed search is, potentially, something a third party service could do. we do provide the streaming API to get much-better-than-search-real-time results. On Apr 6, 2010, at 4:28 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know.
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Doesn't this always happen? Paths diverge (usually around money but sometimes around principle) and then it gives rise to something new? Allan Hoving http://www.thefrequency.tv On Tue, Apr 6, 2010 at 7:28 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.com wrote: 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
Re: [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))
Ed, I would like to re-read your blog post, but it's redirecting me through oAuth into Twitoaster??? On 6 April 2010 01:08, M. Edward (Ed) Borasky zn...@comcast.net wrote: 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.
[twitter-dev] Looking for advice
Hi Guys, just looking for some advice here. For the last half-a-year or so, I've been working on free J2ME Twitter client called PavoMe. It's targeting non-smartfone mobiles such as a less expensive Nokias, SonyEricssons and so on. I'm relatively happy with it and users seem to like it too. However, I find myself running out of steam. I'm sure it wouldn't do any good to a project it I stop adding new features to it, so I'm thinking if I should find a partner who could invest some time in it, grow the user base further and attempt to commercialize it? If so, would anyone be interested? Or perhaps, I should opensource it? It's an interesting mix of tech, with client-side J2ME and server side written in Erlang. Though, I don't think there are many developers interested in J2ME anymore, and not too many Erlang developers yet. So what do you think? http://pavo.me http://tdash.org/stats/client/75 Regards, Anton -- 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)
Dean, sarcasm lines line rel=meSome developers have too much time on their hands./ line lineSo, Twitter make these changes to give them something to do so that they can STFU on these forums, because they are too busy chasing the latest API mod./line /lines /sarcasm On Apr 6, 10:14 am, Dean Collins d...@cognation.net wrote: But raffi why do you have to break the old to offer the new? Basically I've just updated MyPostButler to work again after your last unannounced changed the Thursday evening before a holiday break only to open my email this morning and see you are going to modify search api yet again in some undetermined period of time. I understand things need to change from time to time BUT why so often? Why cant you make the new changes opt-in rather than breaking all the previous applications already deployed out there. Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial).
RE: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Ha ha, love it. I feel sorry for other developers, for me personally I can walk away from my app at anytime as I see fit because I'm not reliant on any single project. lol MyPostButler (or MyTwitterButler as it was known back then) was given away for the first few months - It was just a byproduct for www.LiveBaseballChat.com - it was only when I was flooded for licenses I decided to charge for it. I guess I'm also at a disadvantage as I don't personally code anything and just pay other people to build apps for me so 'any' change is a pita on an roi basis. Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development- t...@googlegroups.com] On Behalf Of Dewald Pretorius Sent: Tuesday, 6 April 2010 9:42 AM To: Twitter Development Talk Subject: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available) Dean, sarcasm lines line rel=meSome developers have too much time on their hands./ line lineSo, Twitter make these changes to give them something to do so that they can STFU on these forums, because they are too busy chasing the latest API mod./line /lines /sarcasm On Apr 6, 10:14 am, Dean Collins d...@cognation.net wrote: But raffi why do you have to break the old to offer the new? Basically I've just updated MyPostButler to work again after your last unannounced changed the Thursday evening before a holiday break only to open my email this morning and see you are going to modify search api yet again in some undetermined period of time. I understand things need to change from time to time BUT why so often? Why cant you make the new changes opt-in rather than breaking all the previous applications already deployed out there. Regards, Dean Collins Cognation Inc d...@cognation.net +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Can't reset application's callback address
It was very reproducible over the weekend... but not today. Maybe OAuth is telling me that I shouldn't work on weekends! BTW, the documentation for the example program refers me to your web site (abrah.am), but when I got there, I get a notice that it's off- line. Is that something that's going to change? I believe there are materials there that would have helped me, at least by convincing me sooner that something out of my ken was happening. -- 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)
- Raffi Krikorian ra...@twitter.com wrote: hi dewald. we obviously feel that users want the most relevant tweets first (the use of popular is unfortunate here). and the web interface of search.twitter.com has begun an evolution in that direction. it's still unclear what Twitter is going to do with the API (hence the silence), however, to go with your argument: time indexed search is, potentially, something a third party service could do. we do provide the streaming API to get much-better-than-search-real-time results. Yes, and the real-time work I'm doing I do with Streaming. Building your own time indexed search on top of Streaming, however, has an *extensive* investment requirement on the part of said third-party services. You've got Firehose-scale bandwidth requirements, Cassandra-scale persistence requirements, and Hadoop-scale algorithmic requirements just for openers. It's an *extremely* competitive marketplace. Hell, there are profitable businesses out there *giving away* Twitter-based services. You've got to be compelling, cheap, correct, pretty and fast out of the box to compete with them. You can't make it work, then make it pretty, go sell it and then make it scale any more. Using Streaming in its current state means duplicating large chunks of Twitter's infrastructure. That's inefficient, and off the top of my head, I can't think of a *single* example of an inefficient business that survived in the long run. -- M. Edward (Ed) Borasky borasky-research.net @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
- Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. +1000 And can we fix Trending Topics too? Give me the Top 100 or Top 200 or even Top 1000 and let me filter out Tiger Woods, Justin Bieber, Lady Gaga and the iPad! ;-) -- M. Edward (Ed) Borasky http://borasky-research.net/smart-at-znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [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))
- Nigel Legg nigel.l...@gmail.com wrote: Ed, I would like to re-read your blog post, but it's redirecting me through oAuth into Twitoaster??? It is? On my web page? Sounds like a bug in the Twitoaster WordPress plugin. There's a Twitoaster widget there, but you should be able to read the blog post directly from the link, and comment with Intense Debate (yet another WordPress plugin - I'm rump-deep in them.) ;-) Try a bit.ly link - maybe it will work better: http://meb.tw/bY0SI8 -- M. Edward (Ed) Borasky borasky-research.net @znmeb 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)
If you have no interest in seeing old tweets then pass the parameter that indicates that you want to strictly see the most recent tweets (the legacy behavior). You get what you want and those who are interested in more signal amongst the ever increasing noise can find out the moderately-less-recent-but-most-popular results associated with their search term. You represent one desired use case. There are others. We are providing a mechanism to get one, the other or both. Choose whichever you like. On Tue, Apr 6, 2010 at 6:11 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, We obviously feel that users want the most relevant tweets first. Has this been determined and confirmed with user focus groups, or is this just an opinion that originated somewhere in a Twitter office or meeting room? I am one of those users, and I have just told you that I have no interest in seeing old tweets, regardless of how popular or relevant they deem to be by your algorithms. When I search Twitter (and I'm making this statement as a user of search.twitter.com, not as an API consumer) I want to see in real-time what is happening right now. That is why I am using search.twitter.com and not google.com for that purpose. If you're going to rather show relevant tweets, then I will instead use Google because their matching algorithms are far more advanced and mature. On Apr 6, 9:47 am, Raffi Krikorian ra...@twitter.com wrote: hi dewald. we obviously feel that users want the most relevant tweets first (the use of popular is unfortunate here). and the web interface of search.twitter.com has begun an evolution in that direction. it's still unclear what Twitter is going to do with the API (hence the silence), however, to go with your argument: time indexed search is, potentially, something a third party service could do. we do provide the streaming API to get much-better-than-search-real-time results. On Apr 6, 2010, at 4:28 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Tweet id is a no-brainer. We understand that an linear incrementing number does not scale because at some point it must cycle back to 1. Search is a different animal. When I do a Twitter search, I expect your system to tell me what is *happening* right now. I am NOT expecting your system to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.comwrote: 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
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
But raffi why do you have to break the old to offer the new? we do our absolute best not to do so. as i mentioned in some previous thread - we do reserve the right to add things to the XML / JSON / etc. outputs -- so, please make sure to have parsers that can handle that. for me, that doesn't break our definition of backwards compatibility. Basically I've just updated MyPostButler to work again after your last unannounced changed the Thursday evening before a holiday break only to open my email this morning and see you are going to modify search api yet again in some undetermined period of time. as a FYI, we now have a policy here on the engineering team at twitter to not deploy any code on fridays (and long weekends and the like) - hopefully this won't happen to you again. but, of course, as with any change, there is a chance for a regression. we do our best to try to make sure that things don't break, and we try to react quickly when they do. please remember that twitter is a constantly evolving platform. I understand things need to change from time to time BUT why so often? Why cant you make the new changes opt-in rather than breaking all the previous applications already deployed out there. again - its an evolving platform. we do our best to make things backwards compatible. i'm happy to provide hints on how to make sure your code can be resilient to forward changes if you want me to. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- 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)
We obviously feel that users want the most relevant tweets first. Has this been determined and confirmed with user focus groups, or is this just an opinion that originated somewhere in a Twitter office or meeting room? twitter does run user studies. yes. I am one of those users, and I have just told you that I have no interest in seeing old tweets, regardless of how popular or relevant they deem to be by your algorithms. When I search Twitter (and I'm making this statement as a user of search.twitter.com, not as an API consumer) I want to see in real-time what is happening right now. That is why I am using search.twitter.com and not google.com for that purpose. If you're going to rather show relevant tweets, then I will instead use Google because their matching algorithms are far more advanced and mature. as i'm sure you can appreciate, twitter has a lot of users / customers you are of course, more than welcome to use google as a search engine for tweets ... :P all in all - i hope a lot of you are coming to chirp, as i would absolutely happy to have this conversation in person over some beers :P -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- 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)
On 6 April 2010 17:27, Raffi Krikorian ra...@twitter.com wrote: our search and relevancy algorithms are constantly changing. we take in a slew of signals like engagement or conversation around tweets, and use that to pull it higher in search results. whether we will provide the exact details of how that algorithm works, i'm not sure. its analogous to google page rankings -- the general notion is well known, but the exact details are constantly changing behind the scenes. we're still trying to figure out things internally regarding these top tweets / popular tweets / relevant tweets, but, as always, one could just connect to the streaming API and get true real time tweets for earthquake. Maybe I could, but my 70 year old other couldn't. I also was talking from a users point of view, not a developers, and even for a develper, you might just want the data a little faster than you could knock up the working code to check the streaming API. At the moment, with 3-4 tweets from popular at the top, it's not too much of a problem, but my worry is that twitter intend to roll out the popularity algorithm to larger and larger chunks of search, thus losing the real time search aspect of which it should be proud. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] How to display local or city wise trending topic into mysite
hi Friends, I have to show current trending topic on my site's home page but they all are belongs to my city or area means I have to show trending topic they all are belong to new york . I read the twitter API but i can' t find solution on my problem. pls help me -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] How to display local or city wise trending topic into mysite
If you need trending topics for cities that are not currently supported you can use the streaming location filter around the city and calculate frequent keywords yourself. http://apiwiki.twitter.com/Streaming-API-Documentation#locations http://apiwiki.twitter.com/Streaming-API-Documentation#locationsAbraham On Tue, Apr 6, 2010 at 09:57, Raffi Krikorian ra...@twitter.com wrote: i'm confused as to what you're asking - are you looking for other local trends to show? you could use these endpoints: http://apiwiki.twitter.com/Twitter-REST-API-Method:-trends-available http://apiwiki.twitter.com/Twitter-REST-API-Method:-trends-available http://apiwiki.twitter.com/Twitter-REST-API-Method:-trends-location On Tue, Apr 6, 2010 at 9:34 AM, millu milindsav...@gmail.com wrote: hi Friends, I have to show current trending topic on my site's home page but they all are belongs to my city or area means I have to show trending topic they all are belong to new york . I read the twitter API but i can' t find solution on my problem. pls help me -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://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: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
On Tue, Apr 6, 2010 at 09:31, Raffi Krikorian ra...@twitter.com wrote: all in all - i hope a lot of you are coming to chirp, as i would absolutely happy to have this conversation in person over some beers :P How about orange juice for those of us who don't drink? :-P Abraham -- 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.
[twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Let's not kid ourselves. This change to relevant tweets is ad revenue related, driven by a fear that Google will siphon off too many search queries. 2 cents. *clink-a-ling* -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Mad about lists and cursors... please help
Has anyone been able to solve this issue? This is still crippling us. Thanks! On Apr 2, 5:25 am, luisfigo rsoeg...@gmail.com wrote: Having the same problem... Triedhttp://api.twitter.com/1/avinashkaushik/lists/memberships.xml and get 0 for cursor. This guy is followed by ton of lists in fact Below is the snapshot of the end result I got... This is screwing up our app right now... . profile_background_image_urlhttp://a1.twimg.com/profile_background_images/79104366/twitter_backgr... /profile_background_image_url profile_background_tilefalse/profile_background_tile notificationsfalse/notifications geo_enabledfalse/geo_enabled verifiedfalse/verified followingfalse/following statuses_count3208/statuses_count langen/lang contributors_enabledfalse/contributors_enabled /user /list /lists next_cursor0/next_cursor previous_cursor0/previous_cursor /lists_list On Apr 1, 6:00 pm, Diego Rin Martin diego@gmail.com wrote: I think it's a API bug, even in the twitter page the paginator doesn't work as expected, sometimes appears, sometines not, and when appears it makes in a random manner. i'm getting cursor 0 from API, using int or string representation, the bug is in the API that sends the cursor 0 randomly. regards, diego. On Thu, Apr 1, 2010 at 2:38 AM, jmathai jmat...@gmail.com wrote: Are you sure you're using the string representation of the cursor instead of the int? The API's cursor exceeds PHP's max integer value (generally). jmathai ~ $ php -r '$x = json_decode(1); echo $x; echo \n; var_dump($x===1); var_dump($x===1.111E+52);' 1.111E+52 bool(false) bool(true) jmathai ~ $ php -r '$x = 1; echo $x; echo \n; var_dump($x===1); var_dump($x===1.111E+52);' 1.111E+52 bool(true) bool(false) On Mar 31, 2:03 am, Diego Rin Martín diego@gmail.com wrote: Hi there, this is my first post to this group, i'm a spanish developer dealing with twitter api surprises, excuse my poor english, i'will do my best to comunicate nicest. So, to the problem, I'm trying to retrieve the lists for a user, via list/memberships get method, and passing cursor as parameter, I'm having got random results, I explain myself, sometimes I made a request (for user edans, that have a huge amount of pages to paginate) and I get one page, I pass cursor -1 and I get cursor 0, sometimes I get one page, I pass cursor -1 i get cursor 1331431515904087602, then I pass it and I get 0, sometimes I get a random number of pages, but never, never, be able to retrieve the total amount of pages. I use php twitter-async classes to comunicate with API, I thought that it could be the cause of the problem, but using direct curl (via php5- curl extension) calls I'm having the same issues. Same using json or xml. I'm always getting 200 responses, so the call finish in a correct way. any clue? I'm turning mad. Thanks in advance. diego. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] How to display local or city wise trending topic into mysite
- Abraham Williams 4bra...@gmail.com wrote: If you need trending topics for cities that are not currently supported you can use the streaming location filter around the city and calculate frequent keywords yourself. http://apiwiki.twitter.com/Streaming-API-Documentation#locations Streaming locations filters only return tweets that are correctly geotagged, and there is a bug which prevents tweets tagged only with the place attribute from being included. You get many more tweets using the Search API with a geocode.
[twitter-dev] xAuth users?
Anyone using xAuth successfully? I'm having trouble getting the process to accept my requests. I can discuss this off list if you prefer. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Seen on hand dryer: Push button for a message from your congressman. - -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] xAuth users?
Several have gotten xAuth to work correctly. I recommend verifying that the following is true: 1) You received approval for use of xAuth -- if you send me a note off-list I can double check if this was granted for you 2) You are using the access_token endpoint with HTTPs: https://api.twitter.com/oauth/access_token 3) Your POST body contains only the x_auth parameters, and the values are URL encoded as POST bodies are supposed to be 4) You're using header-based authentication; query-string based auth will not work for xAuth 5) Your signature base string contains the x_auth parameters just like any other parameters, merged and sorted with the oauth_* parameters, with each value URL escaped. If URL escaping was required to generate a valid POST body string, then the values in your signature base string will likely be double URL encoded. Concrete example: - You are logging in as a user named user1234 with a password abcd+efgh= - Your request URI should be https://api.twitter.com/oauth_access_token - Your POST body should be (order does not matter) x_auth_username=user1234x_auth_password=abcd%2Befgh%3Dx_auth_mode=client_auth - Your signature base string should be something similar to: POSThttps%3A%2F%2Fapi.twitter.com %2Foauth%2Faccess_tokenoauth_consumer_key%3Dri8JxYK2ddwSV5xIUfNNvQ%26oauth_nonce%3D5lReHcSFHYzKb1A4NqHIpoAhX08usNQpzAboyxEdUCI%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1270583500%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dabcd%252Befgh%253D%26x_auth_username%3Duser1234 Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 6, 2010 at 12:28 PM, Cameron Kaiser spec...@floodgap.comwrote: Anyone using xAuth successfully? I'm having trouble getting the process to accept my requests. I can discuss this off list if you prefer. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Seen on hand dryer: Push button for a message from your congressman. - -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] xAuth users?
Using xAuth. I've mobile client, so xAuth is a main auth mode for me. Do you have any particular questions? Regards, Anton On Tue, Apr 6, 2010 at 8:28 PM, Cameron Kaiser spec...@floodgap.com wrote: Anyone using xAuth successfully? I'm having trouble getting the process to accept my requests. I can discuss this off list if you prefer. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Seen on hand dryer: Push button for a message from your congressman. - -- 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)
On 04/06/2010 09:31 AM, Raffi Krikorian wrote: all in all - i hope a lot of you are coming to chirp, as i would absolutely happy to have this conversation in person over some beers :P Black coffee for me, decaf if we're doing this at the hack session / unconference ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
[twitter-dev] Where is the oauth_verifier ?
I'm not seeing it. I'm following the specifications as outlined here: http://tools.ietf.org/html/draft-hammer-oauth-10#section-2 and here: http://oauth.net/core/1.0/#anchor9 I have Application Type set to Browser callbackURL set to my callbakck URL Everything seems to work up until the user clicks Allow Once the user clicks Allow all the callback gets is the oauth_token, I don't see an oauth_verifier. How do I get this? What am I doing wrong? oauth_verifier is not in the GET path it's not in the POST body. The only actual POST is when the user clicks the Allow button and that sends a POST to twitter with an authenticity token and the oauth token but no oauth_verifier anywhere. It's no where. And it's required. What is going on? -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Low latency streaming filter updates
Toby, This is indeed a problem. The ultimate solution, irrespective of practicality, is to arrange to take the entire firehose. Your connections are indeed limited by IP address -- additional accounts, past two, will not help much in this use case. You can, if so motivated, average your new connections over a larger period, allowing lower typical latency. Currently a 10 minute window is configured for IP limiting, but we may change that period without notice. You can connect quite a few times in a 10 minute window before getting limited by IP -- again, subject to change. If you allow, say, 20 connections in 10 minutes, at any velocity, you should stop accepting new predicates, or only update once every 30 seconds until the 10 minute window rolls over. This should allow good liveness for many modest arrival rates and temporal arrival probability distributions. We really need to support updating predicates on live streams to make this use case generally practical, short of taking the firehose. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Apr 6, 2010 at 11:21 AM, Toby Phipps tphi...@gmail.com wrote: Hi, I've been reading a lot in the Twitter Streaming API doc and in this group about techniques to handle filter updates. I've got a good picture of the best practices, but having a hard time applying them to my particular situation. In my case, I've got a filtered stream where the filters will be updated based on the current user activities on my site. The filter updates won't happen that frequently, but when they do, they have to happen with as little latency as possible. This isn't a big problem in probably 80% of the cases where the last filter update happened more than 2 minutes ago, as I can happily disconnect and reconnect immediately and stay within the rules. However when multiple filter updates happen to arrive within the 2 minutes, that's where I have an issue. The unlucky user whose request came in just after a previous update happened gets stuck waiting the full 2 minutes before anything happens for them. They'll get bored, and walk away! The approaches to filter updates in the doc and in this group mainly talk about two concurrent streams - one primary stream with an elevated role and a second interim stream with default elevation. However, this approach works well in allowing filter changes with minimal interruption to the high-volume stream, but it does little or nothing to reduce the update latency. The worst case update latency is still 2 minutes for the poor sucker who came in just after a reconnect on the second (default elevation) stream. Some of the ideas I'm considering are: 1. Running four concurrent streams under four different Twitter accounts and spreading the overall filter criteria between them all (without predicate overlap to prevent wastage). I round-robin any filter changes across the streams, so I should be able to average 4x less latency. This seems within the rules since I'm using four different accounts, but I'm concerned that unless I originate from four different IPs that it'll be seen as a grey area and I risk being banned. 2. Bending the rules a little and bringing my minimum time before reconnect down to 30 seconds, hoping that if 80% or more of the time I respect the 2 minute minimum reconnect interval (and actually stay connected a LOT longer in most cases), I can get away with reconnecting a little more often during edge cases. 3. Running a single stream, and when filter changes are needed and I'm still within the 2 minute reconnect window, faking a stream with multiple queries until the reconnect is allowable at which time I transition to the reconnected stream. While this might be strictly within the rules, I'm convinced that the multiple query hits while waiting for the reconnect window to open would have a higher impact on Twitter than an extra reconnect within the 2 minute window every now and then. Can anyone shed some light on which of these approaches is preferable, or propose a different/better one? The goal for me is being able to adapt the stream criteria to my current user load with the change taking effect as quickly as possible - I can probably wait 30 seconds for an update, but 2 minutes will be tough! Thanks, Toby. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15
First of all, I want to extend an invite to everyone here to the pre- Chirp party we're co-hosting with 140, Klout, LiveIntent, Ellerdale, and Plancast on Tuesday, April 13. See http://tweetvite.com/event/prechirp for all the details. Secondly, is there a wiki or something for coordinating among Chirp Hack Day participants? We're a couple people, but are interested in teaming up with some other folks if it makes sense. So, it would be great to have a central place where people could list hack ideas or areas that interest them and how to get in touch. In the meantime, feel free to reach out to me directly if you want to chat about hack ideas. Hope to see you on Tuesday night, -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 On Apr 6, 3:06 am, Arnaud Meunier arnaud.meun...@twitoaster.com wrote: Really excited to be in San Francisco (first time for me there) next week! Quite a long trip from Paris, but I just couldn't miss such an occasion to meet you all :) For those who would be interested, I made a little Chirppage on Twitoaster, threading Attendees' conversations in real time:http://twitoaster.com/twitter-chirp-conference/ See you (very) soon, Arnaud | @twitoaster |http://twitoaster.com On Apr 5, 9:04 pm, 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 tohttp://chirp.twitter.comandregister. We hope to see you there! Thanks, Doug http://twitter.com/dougw
Re: [twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15
On Tue, Apr 6, 2010 at 15:06, Jonathan Strauss jonat...@snowballfactory.com wrote: Secondly, is there a wiki or something for coordinating among Chirp Hack Day participants? Twitter.com? :-P -- 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.
[twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15
While I typically just lurk here on the Twitter Dev group to keep up to date with changes / etc, I do look forward to meeting everyone out at Chirp. I am hoping I can grab an earlier flight on the 12th which will also allow me to make it to PreChirp as well... (right now sched to get in a little late) See everyone in San Fran... Gonna be a fun 10 days from Chirp to F8... John Twapper Keeper http://twapperkeeper.com http://twitter.com/jobrieniii On Apr 6, 6:30 pm, Abraham Williams 4bra...@gmail.com wrote: On Tue, Apr 6, 2010 at 15:06, Jonathan Strauss jonat...@snowballfactory.com wrote: Secondly, is there a wiki or something for coordinating among Chirp Hack Day participants? Twitter.com? :-P -- 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] Re: Chirp is coming to San Francisco April 14 and 15
Jonathan, Lead the way! I'll happily point to any any efforts you are doing around coordination with the @Chirp account, etc... Thanks, Doug On Tue, Apr 6, 2010 at 3:30 PM, Abraham Williams 4bra...@gmail.com wrote: On Tue, Apr 6, 2010 at 15:06, Jonathan Strauss jonat...@snowballfactory.com wrote: Secondly, is there a wiki or something for coordinating among Chirp Hack Day participants? Twitter.com? :-P -- 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: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Hey everyone, My job title doesn't matter much. I do what I can and what needs to be done, whether that's being a contributing programmer on upcoming platform features, thoroughly testing an API before launch, analyzing implementations for spec compliance, communicating to and with the developer community, working closely with partners, writing documentation, or otherwise. My focus is on making the developer experience a positive one regardless of what bucket you fit into (hobbyist, corporate contributor, research scientist, or entrepreneur, or another lovely bucket). I might do that through building internal tools that make it more efficient and scalable for us to support you, I might do that by helping people out here who have questions, and I certainly might do that by channeling feedback generated in this particular segment of the developer community back to internal teams. When answering questions or engaging in discussions on this forum, I try to answer specific questions that are representative of the whole. I might not answer your specific question, but it's likely I'll answer a similar question with a response that would also apply to your own. Sometimes I will be intentionally obtuse. Often I will be overly verbose. If I don't perceive that I have something meaningful or valuable to add to a conversation or argument, I won't likely respond. We're listening. You're always a factor in the decision making process. Sometimes the community can help change a decision mid-flight (like us deciding to find another way to keep public_timeline alive, despite our desire to deprecate). There will be other times that we'll make a decision that's not in alignment with the perceived popular opinion. All of these things are true. I'll do my best to be transparent on our thought process when it's appropriate to do so; there are times when we won't make our intentions perfectly clear. The Twitter API will change. You I will change with it. This is abstract. This is concrete. This is not a surprise. This is not a pipe. I'm still learning. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 6, 2010 at 12:40 PM, M. Edward (Ed) Borasky zn...@comcast.netwrote: On 04/06/2010 09:31 AM, Raffi Krikorian wrote: all in all - i hope a lot of you are coming to chirp, as i would absolutely happy to have this conversation in person over some beers :P Black coffee for me, decaf if we're doing this at the hack session / unconference ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Taylor, Your job title very much does matter. Any respectable public/open API publisher needs to be concerned with the needs, wants and feelings of their developer community. If you are part of Twitter's effort to address this concern, then you need to be doing certain things. If you are not, then you probably should not be labelled as doing these things in order not to produce misleading expectations among aforementioned developer community. From the sounds of things, you're somewhere between evangelist and client services, but nowhere close to being in the ballpark of developer advocate. I'm not saying you're not doing a good job, I'm just saying you're not doing THAT job. Unfortunately this just contributes to the idea that Twitter doesn't care about the people who enabled its success, that it's grown too big, too fast, to remember the little people, that it's all about the big money and not at all about the community. I'm sure that's driven in large part by Evil Investors, but somewhere at Twitter, someone needs to take a stand and strike a balance. Apparently that's not you. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Tue, Apr 6, 2010 at 7:07 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey everyone, My job title doesn't matter much. I do what I can and what needs to be done, whether that's being a contributing programmer on upcoming platform features, thoroughly testing an API before launch, analyzing implementations for spec compliance, communicating to and with the developer community, working closely with partners, writing documentation, or otherwise. My focus is on making the developer experience a positive one regardless of what bucket you fit into (hobbyist, corporate contributor, research scientist, or entrepreneur, or another lovely bucket). I might do that through building internal tools that make it more efficient and scalable for us to support you, I might do that by helping people out here who have questions, and I certainly might do that by channeling feedback generated in this particular segment of the developer community back to internal teams. When answering questions or engaging in discussions on this forum, I try to answer specific questions that are representative of the whole. I might not answer your specific question, but it's likely I'll answer a similar question with a response that would also apply to your own. Sometimes I will be intentionally obtuse. Often I will be overly verbose. If I don't perceive that I have something meaningful or valuable to add to a conversation or argument, I won't likely respond. We're listening. You're always a factor in the decision making process. Sometimes the community can help change a decision mid-flight (like us deciding to find another way to keep public_timeline alive, despite our desire to deprecate). There will be other times that we'll make a decision that's not in alignment with the perceived popular opinion. All of these things are true. I'll do my best to be transparent on our thought process when it's appropriate to do so; there are times when we won't make our intentions perfectly clear. The Twitter API will change. You I will change with it. This is abstract. This is concrete. This is not a surprise. This is not a pipe. I'm still learning. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 6, 2010 at 12:40 PM, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/06/2010 09:31 AM, Raffi Krikorian wrote: all in all - i hope a lot of you are coming to chirp, as i would absolutely happy to have this conversation in person over some beers :P Black coffee for me, decaf if we're doing this at the hack session / unconference ;-) -- 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)
Very well said, Andrew. Taylor, a Developer Evangelist is supposed to be someone who is paid by Twitter to represent the developers, speak on their behalf in meetings and conversations, represent their interests even when those interests are directly opposed to Twitter's, fight on behalf of the developers, and proactively take actions that will further and protect developer interests. A Developer Advocate is in a way synonymous with a union shop steward. I don't know if this is what you did at LinkedIn as their Developer Advocate. If not, then they (not you) too missed the mark by assigning to you the wrong task list. If this is not what Twitter wants to pay you to do, then fine. Then they must just not pretend to have a Developer Advocate by slapping that title on somebody. Titles matter, but they mean nothing if you're not doing what the title implies. With so many thousands of developers out there, as a true Developer Advocate, you shouldn't have time to do coding, documentation, and whatever else they have you doing. Unfortunately I'm not familiar with Andrew's full employment history and business background. But, I've been in the IT industry since 1980, and I've been at Vice President level of a large IT consulting company. Hence, with some things there is a slight possibility that I may know a little about what I'm talking. On Apr 6, 8:14 pm, Andrew Badera and...@badera.us wrote: Taylor, Your job title very much does matter. Any respectable public/open API publisher needs to be concerned with the needs, wants and feelings of their developer community. If you are part of Twitter's effort to address this concern, then you need to be doing certain things. If you are not, then you probably should not be labelled as doing these things in order not to produce misleading expectations among aforementioned developer community. From the sounds of things, you're somewhere between evangelist and client services, but nowhere close to being in the ballpark of developer advocate. I'm not saying you're not doing a good job, I'm just saying you're not doing THAT job. Unfortunately this just contributes to the idea that Twitter doesn't care about the people who enabled its success, that it's grown too big, too fast, to remember the little people, that it's all about the big money and not at all about the community. I'm sure that's driven in large part by Evil Investors, but somewhere at Twitter, someone needs to take a stand and strike a balance. Apparently that's not you. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Tue, Apr 6, 2010 at 7:07 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey everyone, My job title doesn't matter much. I do what I can and what needs to be done, whether that's being a contributing programmer on upcoming platform features, thoroughly testing an API before launch, analyzing implementations for spec compliance, communicating to and with the developer community, working closely with partners, writing documentation, or otherwise. My focus is on making the developer experience a positive one regardless of what bucket you fit into (hobbyist, corporate contributor, research scientist, or entrepreneur, or another lovely bucket). I might do that through building internal tools that make it more efficient and scalable for us to support you, I might do that by helping people out here who have questions, and I certainly might do that by channeling feedback generated in this particular segment of the developer community back to internal teams. When answering questions or engaging in discussions on this forum, I try to answer specific questions that are representative of the whole. I might not answer your specific question, but it's likely I'll answer a similar question with a response that would also apply to your own. Sometimes I will be intentionally obtuse. Often I will be overly verbose. If I don't perceive that I have something meaningful or valuable to add to a conversation or argument, I won't likely respond. We're listening. You're always a factor in the decision making process. Sometimes the community can help change a decision mid-flight (like us deciding to find another way to keep public_timeline alive, despite our desire to deprecate). There will be other times that we'll make a decision that's not in alignment with the perceived popular opinion. All of these things are true. I'll do my best to be transparent on our thought process when it's appropriate to do so; there are times when we won't make our intentions perfectly clear. The Twitter API will change. You I will change with it. This is abstract. This is concrete. This is not a surprise. This is not a pipe. I'm still learning. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Yikes, of course I meant to write Deveoper Advocate, and not Developer Evangelist. On Apr 6, 8:51 pm, Dewald Pretorius dpr...@gmail.com wrote: Very well said, Andrew. Taylor, a Developer Evangelist is supposed to be someone who is paid by Twitter to represent the developers, speak on their behalf in meetings and conversations, represent their interests even when those interests are directly opposed to Twitter's, fight on behalf of the developers, and proactively take actions that will further and protect developer interests. A Developer Advocate is in a way synonymous with a union shop steward. I don't know if this is what you did at LinkedIn as their Developer Advocate. If not, then they (not you) too missed the mark by assigning to you the wrong task list. If this is not what Twitter wants to pay you to do, then fine. Then they must just not pretend to have a Developer Advocate by slapping that title on somebody. Titles matter, but they mean nothing if you're not doing what the title implies. With so many thousands of developers out there, as a true Developer Advocate, you shouldn't have time to do coding, documentation, and whatever else they have you doing. Unfortunately I'm not familiar with Andrew's full employment history and business background. But, I've been in the IT industry since 1980, and I've been at Vice President level of a large IT consulting company. Hence, with some things there is a slight possibility that I may know a little about what I'm talking. On Apr 6, 8:14 pm, Andrew Badera and...@badera.us wrote: Taylor, Your job title very much does matter. Any respectable public/open API publisher needs to be concerned with the needs, wants and feelings of their developer community. If you are part of Twitter's effort to address this concern, then you need to be doing certain things. If you are not, then you probably should not be labelled as doing these things in order not to produce misleading expectations among aforementioned developer community. From the sounds of things, you're somewhere between evangelist and client services, but nowhere close to being in the ballpark of developer advocate. I'm not saying you're not doing a good job, I'm just saying you're not doing THAT job. Unfortunately this just contributes to the idea that Twitter doesn't care about the people who enabled its success, that it's grown too big, too fast, to remember the little people, that it's all about the big money and not at all about the community. I'm sure that's driven in large part by Evil Investors, but somewhere at Twitter, someone needs to take a stand and strike a balance. Apparently that's not you. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Tue, Apr 6, 2010 at 7:07 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey everyone, My job title doesn't matter much. I do what I can and what needs to be done, whether that's being a contributing programmer on upcoming platform features, thoroughly testing an API before launch, analyzing implementations for spec compliance, communicating to and with the developer community, working closely with partners, writing documentation, or otherwise. My focus is on making the developer experience a positive one regardless of what bucket you fit into (hobbyist, corporate contributor, research scientist, or entrepreneur, or another lovely bucket). I might do that through building internal tools that make it more efficient and scalable for us to support you, I might do that by helping people out here who have questions, and I certainly might do that by channeling feedback generated in this particular segment of the developer community back to internal teams. When answering questions or engaging in discussions on this forum, I try to answer specific questions that are representative of the whole. I might not answer your specific question, but it's likely I'll answer a similar question with a response that would also apply to your own. Sometimes I will be intentionally obtuse. Often I will be overly verbose. If I don't perceive that I have something meaningful or valuable to add to a conversation or argument, I won't likely respond. We're listening. You're always a factor in the decision making process. Sometimes the community can help change a decision mid-flight (like us deciding to find another way to keep public_timeline alive, despite our desire to deprecate). There will be other times that we'll make a decision that's not in alignment with the perceived popular opinion. All of these things are true. I'll do my best to be transparent on our thought process when it's appropriate to do so; there are times when we won't make our
[twitter-dev] Re: Opt-in beta of Popular Tweets for the Search API now available
My oh my, what discussion about advocacy and what not. I think Taylor, Raffi and everybody else from Twitter are doing a great job here and everyone is eager to learn and they know they have ways to go. Let's not get mean. I'm with those who say injecting popular searches into the search API results by Twitter still doesn't entirely make sense, given the way the rollout/communication is handled. Here is the problem/conversation in a nutshell: Twitter: We are going to inject popular search results into the search API results, changing previous behavior that just returned recent results. Developers: Wait a sec, this is a bad idea because of A, B and C. Maybe you can version the API better or some such. ... time passes, nothing happens ... Twitter: Hi, we're starting to roll this out now. I don't particularly care for the popular results either way and I trust Twitter that it is good for users in the grand scheme of things, but the API behavior change is disturbing. It would be great to work against a fixed API target so that those who want search to work in a particular way can just work against a given API version, but with search, this is not an option, you only have one endpoint that's in this kind of flux. What I'm saying is Twitter as a company could just earn more developer street cred and respect here by handling this in a more graceful way. There comes a point in time where the moving parts argument as an excuse to not follow good API practices gets somewhat old. rgds, Jaanus -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] xAuth users?
Hi, I am using auth successfully but I am using an implementation of xAuth in .net not xAuth directly. NB.- You need to send a mail to a...@twitter.com and request them to register your app for xAuth access. On Wed, Apr 7, 2010 at 12:58 AM, Cameron Kaiser spec...@floodgap.comwrote: Anyone using xAuth successfully? I'm having trouble getting the process to accept my requests. I can discuss this off list if you prefer. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Seen on hand dryer: Push button for a message from your congressman. - -- To unsubscribe, reply using remove me as the subject. -- Thanks Regards Rajiv Verma Bangalore E-Mail: rajiv@gmail.com Ph: +91-92430-12766 Go Green, Use minimum natural resources!
[twitter-dev] Mobile view of twitter.com doesn't show This person has protected their tweets message
For the case where I'm trying to view a protected Twitter account profile http://twitter.com/username I'm not signed in or not a follower: - Standard view displays a page with a lock image the message This person has protected their tweets - Mobile view displays a page with a message This functionality is not currently supported in the mobile site. This is coming soon. Thanks for your patience! This occurs in FF, IE, Chrome Opera. This is confusing to users of the app I'm developing, which renders a mobile-optimised webpage with links to http://m.twitter.com/username. Is this likely to be fixed any time soon? Thanks -- Richard Barnett -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15
On 04/06/2010 05:21 PM, Jonathan Strauss wrote: Ok, I just threw this together super quickly: http://chirphackday.pbworks.com/ Preliminary sections: * List of participants + areas of interests * Ideas + interested developers * Non-Twitter APIs that might be useful /shameless plug It's currently open to anyone to edit. Hopefully folks will find it useful and/or improve on it. @Doug: It would be great to have any more details about the Hack Day process (i.e. rules, etc) that are currently available added in the general info section at the top. I thought we were using Plancast for that. I don't have a problem with your site, but if we're using yours instead of Plancast, I'll delete my Plancast account - I've got way too many social media gizmo logins as it is. ;-) -- 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.
