[twitter-dev] Re: Some thoughts leading up to Chirp
Justyn, Trust me, this has nothing to do with negativity. When Ryan sets the clear expectation of, My promise is that ... we will be sincere and honest in our communication with you, and in the same breath expects us to believe that Tweetie was acquired primarily or solely to avoid confusion in the app store, I go, Now wait a second... No, man, don't do this. Not in the same breath. Tweetie really, honestly, wasn't acquired to own the iPhone / iPad eyeballs, capture the bulk of future ad (and other) revenue on that platform, and form an intellectual property base to extend to Android and other mobile platforms to own those eyeballs and revenue? On Apr 12, 12:58 am, Justyn justyn.how...@gmail.com wrote: Regardless of the companies position moving forward, there are great people working at Twitter who sincerely care about the developer community, including Ryan. If things are unfair, you can bet they feel it too. They're still figuring it out. I don't see them implementing any of the stuff your software does, so I don't understand the constant negativity. You complained that they weren't communicating, and when they do you call it BS. Life's too short man. The whole situation the last few days reminds me a lot of this clip:http://www.youtube.com/watch?v=KLni3wbndls Justyn On Apr 11, 8:05 pm, Dewald Pretorius dpr...@gmail.com wrote: Ryan, Thanks for attempting to step into an emotionally charged environment and clarifying things. However, to be quite frank, the argument about confusion in the Apple app store gives off a distinct spinning sound. Very loud, in fact. It may be one of the reasons for acquiring Tweetie, but to cite it as the primary and only reason immediately sets of all flavors of BS alarms.- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Some thoughts leading up to Chirp
When will Twitter answer: 1) Why did Twitter acquire Tweetie? 2) What is Twitter planning to do with Tweetie? On Apr 12, 10:22 am, Ryan Sarver rsar...@twitter.com wrote: I wanted to email everyone and share my thoughts on the acquisition from Friday, the communication around it and where we are going from here. We're incredibly excited about Chirp, and I think an open dialogue going into it is important. I look forward to meeting many of you there and continuing the discussion. We love the Twitter ecosystem and work hard every day to help support you and make the platform you are building on as successful as it can be for everyone involved. We love the variety that developers have built around the Twitter experience and it's a big part of the success we've seen. However when we dug in a little bit we realized that it was causing massive confusion among user's who had an iPhone and were looking to use Twitter for the first time. They would head to the App Store, search for Twitter and would see results that included a lot of apps that had nothing to do with Twitter and a few that did, but a new user wouldn't find what they were looking for and give up. That is a lost user for all of us. This means that we were missing out an opportunity to grow the userbase which is beneficial for the health of the entire ecosystem. Focus on growing and serving the userbase is beneficial to everyone in the ecosystem and more opportunities become available with a larger audience. We believe strongly that the ecosystem is critical to our success and this move doesn't change that. We have analytics that show our most engaged users are ones that use SMS, twitter.com AND a 3rd-party application. It further proves that there are different audiences and needs that we can never meet on our own and we all need to work together to provide what is best for the users. Once I understood the long-term view I strongly believed it was not only the right thing to do for users, but the right thing to do for the ecosystem as a whole. To be clear, we are going to work hard to improve our product, add new functionality, make acquisitions when it's in the best interest of users and the whole ecosystem at large. Each one of those things has the potential to upset a company or developer that may have been building in that space and they then have to look for new ways to create value for users. My promise is that we will be consistent in always focusing on what's best for the user and the ecosystem as a whole and we will be sincere and honest in our communication with you. To the point that we can, we will try to give more certainty about the areas where we think we can maximize benefit to users. We will continue to focus on what is best for users and we will work together to make sure that we are creating more opportunities for the ecosystem on the whole. We will also admit our mistakes when they are made and the Blackberry client should never have been labeled official. It has since been changed and you won't see that language used with Twitter clients in the future. This week will hopefully show that we are focused on building a platform that no longer just mirrors twitter.com functionality, but offers you raw utility that provides much greater opportunities to innovate and build durable, valuable businesses. I also want this week to be an opportunity for us to get together and discuss the future of the platform and how we can improve our communication, responsiveness and clarity. We have an open office hours at 10:15am on Thursday at the Hack Day and I invite all of you to come by for a discussion to talk about the future of the platform and help us craft a working relationship that is beneficial for both of us. I will provide a free ticket to anyone from this list that is unable to afford the current price so that they can be part of that discussion. Just email me directly. For those of you who can't make it to Chirp, it will be live streamed so you can tune in from home -- where ever home might be. As always, you can reach me by email or by phone, 617 763 9904. I am here to listen and provide clarity when possible and you should know we are committed to working with you on this. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] OAuth 2.0
Raffi, Is there a spot where one can read the draft specs of OAuth 2.0? I don't see it on oauth.net. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Retweet rules. What I'm missing?
I'm having lots of strange problems with retweets. Sometimes it works, sometimes don't. Appart of that, the error messages comming from Twitter are not 100% clear. I'm reenginering my mind simply asking to everybody: What are the retweets rules and/or conditions to succed or fail? I mean: what can be retweeted? what cannot be retweeted? Is there any common list of error messages on retweeting? Thank you very much for your help! Regards, Herman Gomez. Spain. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter Stream crossdomain.xml
To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp://groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp://groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we can provide a few more features (oAuth, etc.), provide sufficient capacity, and fully isolate desktop traffic from integration traffic. A single Hosebird process can pump out a lot of data. A cluster of them is a bit like a bull in a china shop. We want to avoid a success catastrophe where a set of popular clients releases all at once and inadvertently overwhelms the service and potentially knocks integrations and/or non-trivial slice of www traffic offline. This would be bad for everyone, including open experimental access. So, among a dozen other disabled features,crossdomain.xml is also off on stream.twitter.com. We're working on this right now. Please have patience. Thecrossdomain.xml policy on other endpoints is the doing of others, and I don't remember all the details. Please trust that the policies chosen were made with user privacy and user security as the primary concerns. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 19, 2010 at 8:55 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Am I interpreting this correct as saying out of capacity concern we're currently blocking Flash developers? Thecrossdomain.xml issue has been extremely frustrating across all of Twitter's service endpoints and if I'm interpreting this post correctly this just adds to a series of poor choices Twitter has made in regard to Flash developers in my opinion. If this service needs to be limited for capacity reasons it should be limited in the same way regardless of what technology you are using to make requests of the API. -Orian Marx Flex Developer On Mar 17, 1:50 pm, John Kalucki j...@twitter.com wrote: It's in the code, but turned off out of an abundance of caution for capacity reasons. Given our current plans, it's going to be a little while longer before we can turn this on. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 17, 2010 at 10:29 AM, TarGz julien.ter...@gmail.com wrote: hi, I have prevriuosly work on twittearth.com and now I work a project that use the stream API. The stream API work very well, it is very responsive and powerfull and help me build a realtime geolocated search tool... The bad sing is that my Flash app only work offline because of the lak ofcrossdomain.xml Did you have plan to put ahttp://sream.twitter.com/crossdomain.xml file live soon ? because I love to share my tools with the world. Thank per advance for your answer(s) Looking forward for your reply To unsubscribe from this
[twitter-dev] Re: Twitter API - users/search - Help Required
OK I got it. thanks for the support :) On Apr 11, 10:06 pm, Raffi Krikorian ra...@twitter.com wrote: ok - sorry - i was thrown off by ipad. the results should change, but the velocity of change may depend. name search results are ordered so the best results are further up -- new users who get added to the system may not make the top 1000 users that namesearch can return. as users are active in the system, use twitter, engage people, etc., their ranking in name search will move up. does that answer the question? On Sun, Apr 11, 2010 at 11:39 AM, Jimmy breathlo...@gmail.com wrote: Raffi and Nic, thanks for replying :) Yes, I'm concerned with the user search and by mistake I wrote ipad, I should have written some name! Now please let me know whether the result should be changed or I'll keep getting the stale result. I reckon twitter keep getting new users every next minute then why API returns the same old result and that is also to some extend. Does API result change ? On Apr 11, 5:28 pm, Nic Ross iamurdest...@gmail.com wrote: Ok don't take it here an example for ipad may be it was his mistake. Lets say take an example for any common names like James or Chang or Chen don't you expect there will be far more results than 1000 So, the point he is making here is will twitter keep the same result of 1000 users for every an authenticated user for any particular time duration or unlimitedly ? I think Jimmy can put some more light on the issue :) On Apr 11, 10:15 pm, Raffi Krikorian ra...@twitter.com wrote: Well, with name search the users are not going to change much. How many users do you expect to have the name ipad (even with the rate that users are being created). Am I confused? On Apr 11, 2010, at 1:01 PM, Nic Ross iamurdest...@gmail.com wrote: Sorry I didn't see my last reply so I am posting it again @Raffi Krikorian I think Jimmy is asking for searching users not tweets. Look at his URLs they contain users/search and also users/search API call limits the result to 1000 (20 result each page) which he is mentioning. The search API which you are suggestion is used to search Tweets not users. Regards Nic On Apr 11, 9:39 pm, Raffi Krikorian ra...@twitter.com wrote: do you mean to be using name search, or the general search API? Try using the search endpoint at search.twitter.con. On Apr 11, 2010, at 11:48 AM, Jimmy breathlo...@gmail.com wrote: Hi, I'm working on search api and and came across a problem. Here is my query: http://api.twitter.com/1/users/search.json?q=ipadpage=1 The result which I got is constant and never changes. I checked the result after some span of time like: after 1-2 hours but I got the same result. As per API we can only retrieve first 1000 matches in 50 pages(20 result each page) so does it mean that for life long I will keep getting the same result for the same query? I mean that is weird! I also matched the result of second and third page http://api.twitter.com/1/users/search.json?q=ipadpage=2 http://api.twitter.com/1/users/search.json?q=ipadpage=3 within the span of 1-2 hours but the result was same each time. Any kind of help will be appreciatable. -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Twitter API - users/search - Help Required
Oh! I forgot to say thanks to Nic Ross. Thanks to you also. On Apr 11, 10:06 pm, Raffi Krikorian ra...@twitter.com wrote: ok - sorry - i was thrown off by ipad. the results should change, but the velocity of change may depend. name search results are ordered so the best results are further up -- new users who get added to the system may not make the top 1000 users that namesearch can return. as users are active in the system, use twitter, engage people, etc., their ranking in name search will move up. does that answer the question? On Sun, Apr 11, 2010 at 11:39 AM, Jimmy breathlo...@gmail.com wrote: Raffi and Nic, thanks for replying :) Yes, I'm concerned with the user search and by mistake I wrote ipad, I should have written some name! Now please let me know whether the result should be changed or I'll keep getting the stale result. I reckon twitter keep getting new users every next minute then why API returns the same old result and that is also to some extend. Does API result change ? On Apr 11, 5:28 pm, Nic Ross iamurdest...@gmail.com wrote: Ok don't take it here an example for ipad may be it was his mistake. Lets say take an example for any common names like James or Chang or Chen don't you expect there will be far more results than 1000 So, the point he is making here is will twitter keep the same result of 1000 users for every an authenticated user for any particular time duration or unlimitedly ? I think Jimmy can put some more light on the issue :) On Apr 11, 10:15 pm, Raffi Krikorian ra...@twitter.com wrote: Well, with name search the users are not going to change much. How many users do you expect to have the name ipad (even with the rate that users are being created). Am I confused? On Apr 11, 2010, at 1:01 PM, Nic Ross iamurdest...@gmail.com wrote: Sorry I didn't see my last reply so I am posting it again @Raffi Krikorian I think Jimmy is asking for searching users not tweets. Look at his URLs they contain users/search and also users/search API call limits the result to 1000 (20 result each page) which he is mentioning. The search API which you are suggestion is used to search Tweets not users. Regards Nic On Apr 11, 9:39 pm, Raffi Krikorian ra...@twitter.com wrote: do you mean to be using name search, or the general search API? Try using the search endpoint at search.twitter.con. On Apr 11, 2010, at 11:48 AM, Jimmy breathlo...@gmail.com wrote: Hi, I'm working on search api and and came across a problem. Here is my query: http://api.twitter.com/1/users/search.json?q=ipadpage=1 The result which I got is constant and never changes. I checked the result after some span of time like: after 1-2 hours but I got the same result. As per API we can only retrieve first 1000 matches in 50 pages(20 result each page) so does it mean that for life long I will keep getting the same result for the same query? I mean that is weird! I also matched the result of second and third page http://api.twitter.com/1/users/search.json?q=ipadpage=2 http://api.twitter.com/1/users/search.json?q=ipadpage=3 within the span of 1-2 hours but the result was same each time. Any kind of help will be appreciatable. -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Some thoughts leading up to Chirp
Ryan, Great post. Thank you for taking the time to clarify some of Twitters recent actions and future direction. Hopefully this thread will not get derailed... Looking forward to seeing you and all the Twitter folks in a few days to continue the discussion. And maybe at the oneforty PreChip party? :) RE Mike's comment... Yea what's the deal with Tweetie for Mac man? I need my Tweetie fix. ;) M On Apr 11, 8:22 pm, Ryan Sarver rsar...@twitter.com wrote: I wanted to email everyone and share my thoughts on the acquisition from Friday, the communication around it and where we are going from here. We're incredibly excited about Chirp, and I think an open dialogue going into it is important. I look forward to meeting many of you there and continuing the discussion. We love the Twitter ecosystem and work hard every day to help support you and make the platform you are building on as successful as it can be for everyone involved. We love the variety that developers have built around the Twitter experience and it's a big part of the success we've seen. However when we dug in a little bit we realized that it was causing massive confusion among user's who had an iPhone and were looking to use Twitter for the first time. They would head to the App Store, search for Twitter and would see results that included a lot of apps that had nothing to do with Twitter and a few that did, but a new user wouldn't find what they were looking for and give up. That is a lost user for all of us. This means that we were missing out an opportunity to grow the userbase which is beneficial for the health of the entire ecosystem. Focus on growing and serving the userbase is beneficial to everyone in the ecosystem and more opportunities become available with a larger audience. We believe strongly that the ecosystem is critical to our success and this move doesn't change that. We have analytics that show our most engaged users are ones that use SMS, twitter.com AND a 3rd-party application. It further proves that there are different audiences and needs that we can never meet on our own and we all need to work together to provide what is best for the users. Once I understood the long-term view I strongly believed it was not only the right thing to do for users, but the right thing to do for the ecosystem as a whole. To be clear, we are going to work hard to improve our product, add new functionality, make acquisitions when it's in the best interest of users and the whole ecosystem at large. Each one of those things has the potential to upset a company or developer that may have been building in that space and they then have to look for new ways to create value for users. My promise is that we will be consistent in always focusing on what's best for the user and the ecosystem as a whole and we will be sincere and honest in our communication with you. To the point that we can, we will try to give more certainty about the areas where we think we can maximize benefit to users. We will continue to focus on what is best for users and we will work together to make sure that we are creating more opportunities for the ecosystem on the whole. We will also admit our mistakes when they are made and the Blackberry client should never have been labeled official. It has since been changed and you won't see that language used with Twitter clients in the future. This week will hopefully show that we are focused on building a platform that no longer just mirrors twitter.com functionality, but offers you raw utility that provides much greater opportunities to innovate and build durable, valuable businesses. I also want this week to be an opportunity for us to get together and discuss the future of the platform and how we can improve our communication, responsiveness and clarity. We have an open office hours at 10:15am on Thursday at the Hack Day and I invite all of you to come by for a discussion to talk about the future of the platform and help us craft a working relationship that is beneficial for both of us. I will provide a free ticket to anyone from this list that is unable to afford the current price so that they can be part of that discussion. Just email me directly. For those of you who can't make it to Chirp, it will be live streamed so you can tune in from home -- where ever home might be. As always, you can reach me by email or by phone, 617 763 9904. I am here to listen and provide clarity when possible and you should know we are committed to working with you on this. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Some thoughts leading up to Chirp
On Apr 12, 2:44 am, Jason Rundell jason.rund...@gmail.com wrote: When will Twitter answer: 1) Why did Twitter acquire Tweetie? 2) What is Twitter planning to do with Tweetie? Since when does Twitter owe you or any of us any sort of explanation for their business practices? Lemme get this straight. Twitter is FREE. The Twitter API is public, well documented, and FREE. Our privilege is to build tools and businesses on top of Twitter's FREE services. Twitter doesn't want a cut of your business. They don't require approval of your apps. But for some reason you (and others) feel entitled to an explanation, or details somehow outlining their strategy and practices? The tone of this group never ceases to amaze me. Get back to coding and building cool stuff. @notinfluential -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Some thoughts leading up to Chirp
Tweetie 2 for Mac is still alive, folks! http://www.macheist.com/forums/viewtopic.php?pid=370710#p370710 --Robby On Apr 12, 7:33 am, Michael Macasek mich...@oneforty.com wrote: Ryan, Great post. Thank you for taking the time to clarify some of Twitters recent actions and future direction. Hopefully this thread will not get derailed... Looking forward to seeing you and all the Twitter folks in a few days to continue the discussion. And maybe at the oneforty PreChip party? :) RE Mike's comment... Yea what's the deal with Tweetie for Mac man? I need my Tweetie fix. ;) M On Apr 11, 8:22 pm, Ryan Sarver rsar...@twitter.com wrote: I wanted to email everyone and share my thoughts on the acquisition from Friday, the communication around it and where we are going from here. We're incredibly excited about Chirp, and I think an open dialogue going into it is important. I look forward to meeting many of you there and continuing the discussion. We love the Twitter ecosystem and work hard every day to help support you and make the platform you are building on as successful as it can be for everyone involved. We love the variety that developers have built around the Twitter experience and it's a big part of the success we've seen. However when we dug in a little bit we realized that it was causing massive confusion among user's who had an iPhone and were looking to use Twitter for the first time. They would head to the App Store, search for Twitter and would see results that included a lot of apps that had nothing to do with Twitter and a few that did, but a new user wouldn't find what they were looking for and give up. That is a lost user for all of us. This means that we were missing out an opportunity to grow the userbase which is beneficial for the health of the entire ecosystem. Focus on growing and serving the userbase is beneficial to everyone in the ecosystem and more opportunities become available with a larger audience. We believe strongly that the ecosystem is critical to our success and this move doesn't change that. We have analytics that show our most engaged users are ones that use SMS, twitter.com AND a 3rd-party application. It further proves that there are different audiences and needs that we can never meet on our own and we all need to work together to provide what is best for the users. Once I understood the long-term view I strongly believed it was not only the right thing to do for users, but the right thing to do for the ecosystem as a whole. To be clear, we are going to work hard to improve our product, add new functionality, make acquisitions when it's in the best interest of users and the whole ecosystem at large. Each one of those things has the potential to upset a company or developer that may have been building in that space and they then have to look for new ways to create value for users. My promise is that we will be consistent in always focusing on what's best for the user and the ecosystem as a whole and we will be sincere and honest in our communication with you. To the point that we can, we will try to give more certainty about the areas where we think we can maximize benefit to users. We will continue to focus on what is best for users and we will work together to make sure that we are creating more opportunities for the ecosystem on the whole. We will also admit our mistakes when they are made and the Blackberry client should never have been labeled official. It has since been changed and you won't see that language used with Twitter clients in the future. This week will hopefully show that we are focused on building a platform that no longer just mirrors twitter.com functionality, but offers you raw utility that provides much greater opportunities to innovate and build durable, valuable businesses. I also want this week to be an opportunity for us to get together and discuss the future of the platform and how we can improve our communication, responsiveness and clarity. We have an open office hours at 10:15am on Thursday at the Hack Day and I invite all of you to come by for a discussion to talk about the future of the platform and help us craft a working relationship that is beneficial for both of us. I will provide a free ticket to anyone from this list that is unable to afford the current price so that they can be part of that discussion. Just email me directly. For those of you who can't make it to Chirp, it will be live streamed so you can tune in from home -- where ever home might be. As always, you can reach me by email or by phone, 617 763 9904. I am here to listen and provide clarity when possible and you should know we are committed to working with you on this. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] OAuth 2.0
*http://github.com/theRazorBlade/draft-ietf-oauth* * * like i said before, as this is just a draft, i rather not our mailing list turn into a discussion of it just yet (once we start implementing it, then all bets are off :P). if there are questions and/or comments, just feel free to reach out to me directly. On Mon, Apr 12, 2010 at 6:22 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Is there a spot where one can read the draft specs of OAuth 2.0? I don't see it on oauth.net. -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Twitter Stream crossdomain.xml
- there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.comwrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we can provide a few more features (oAuth, etc.), provide sufficient capacity, and fully isolate desktop traffic from integration traffic. A single Hosebird process can pump out a lot of data. A cluster of them is a bit like a bull in a china shop. We want to avoid a success catastrophe where a set of popular clients releases all at once and inadvertently overwhelms the service and potentially knocks integrations and/or non-trivial slice of www traffic offline. This would be bad for everyone, including open experimental access. So, among a dozen other disabled features,crossdomain.xml is also off on stream.twitter.com. We're working on this right now. Please have patience. Thecrossdomain.xml policy on other endpoints is the doing of others, and I don't remember all the details. Please trust that the policies chosen were made with user privacy and user security as the primary concerns. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 19, 2010 at 8:55 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Am I interpreting this correct as saying out of capacity concern we're currently blocking Flash developers? Thecrossdomain.xml issue has been extremely frustrating across all of Twitter's service endpoints and if I'm interpreting this post correctly this just adds to a series of poor choices Twitter has made in regard to Flash developers in my opinion. If this service needs to be limited for capacity reasons it should be limited in the same way regardless of what technology you are using to make requests of the API. -Orian Marx Flex Developer On Mar 17, 1:50 pm, John Kalucki j...@twitter.com wrote: It's in the code, but turned off out of an abundance of caution for capacity reasons.
[twitter-dev] Re: Some thoughts leading up to Chirp
Not only do we feel entitled, we ARE entitled to an open and honest explanation when open and honest communication is offered and promised to us. There are two possible paths to follow: a) Give us spin, and don't promise open and honest communication. b) Promise us open and honest communication, and give us exactly that, not spin. Those are the two paths that do not undermine credibility, because then we know what to expect, and we get what we expect. On Apr 12, 10:34 am, notinfluential notinfluent...@gmail.com wrote: On Apr 12, 2:44 am, Jason Rundell jason.rund...@gmail.com wrote: When will Twitter answer: 1) Why did Twitter acquire Tweetie? 2) What is Twitter planning to do with Tweetie? Since when does Twitter owe you or any of us any sort of explanation for their business practices? Lemme get this straight. Twitter is FREE. The Twitter API is public, well documented, and FREE. Our privilege is to build tools and businesses on top of Twitter's FREE services. Twitter doesn't want a cut of your business. They don't require approval of your apps. But for some reason you (and others) feel entitled to an explanation, or details somehow outlining their strategy and practices? The tone of this group never ceases to amaze me. Get back to coding and building cool stuff. @notinfluential -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] What's happening with Tweetie for Mac
One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan
[twitter-dev] Re: OAuth 2.0
Thanks. Just want to get a sense of what's coming up. The spec is an awesome piece of work. On Apr 12, 10:59 am, Raffi Krikorian ra...@twitter.com wrote: *http://github.com/theRazorBlade/draft-ietf-oauth* * * like i said before, as this is just a draft, i rather not our mailing list turn into a discussion of it just yet (once we start implementing it, then all bets are off :P). if there are questions and/or comments, just feel free to reach out to me directly. On Mon, Apr 12, 2010 at 6:22 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, Is there a spot where one can read the draft specs of OAuth 2.0? I don't see it on oauth.net. -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] What's happening with Tweetie for Mac
So if I got this right, Twitter is going to distribute both Tweetie for iPhone and Tweetie for Mac for free, thus competing with its developer community in the Twitter desktop and mobile client space with free products? And all those other desktop and mobile apps that helped put Twitter on the map, well they're just SOL? And somehow Twitter believes this move is going to encourage developers to continue to develop for a platform that will eventually compete against all but one of them with predatory free pricing? Sounds like you must be looking for developers from the Las Vegas School of Business, not business partners within a symbiotic ecosystem. On Mon, Apr 12, 2010 at 9:40 AM, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan
[twitter-dev] Re: Twitter Stream crossdomain.xml
I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off of www.twitter.com malicious Flash code could potentially get at user's cookies from any browser sessions from visiting www.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.html http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.comwrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we can provide a few more features (oAuth, etc.), provide sufficient capacity, and fully isolate desktop traffic from integration traffic. A single Hosebird process can pump out a lot of data. A cluster of them is a bit like a bull in a china shop. We want to avoid a success catastrophe where a set of popular clients releases all at once and inadvertently overwhelms the service and potentially knocks integrations and/or non-trivial slice of www traffic offline. This would be bad for everyone, including open experimental access. So, among a dozen other disabled features,crossdomain.xml is
Re: [twitter-dev] Re: Twitter Stream crossdomain.xml
as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off of www.twitter.com malicious Flash code could potentially get at user's cookies from any browser sessions from visiting www.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.html http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we
Re: [twitter-dev] What's happening with Tweetie for Mac
Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] What's happening with Tweetie for Mac
There are a number of people that would like Twitter to consider open sourcing Tweetie for Mac: http://act.ly/1w1 http://act.ly/1w1There is much to be gained such as community contributed patches, a more competitive environment on the Mac, (just to name a few) and little to lose. I hope Twitter will consider this option in earnest. Abraham On Mon, Apr 12, 2010 at 07:40, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- Abraham Williams | Developer for hire | 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] users/lookup and OAuthed Signed requests
I'm having a heck of a time getting the users/lookup to work. I keep getting an invalid signature response, however if I try hitting other urls that require authentication (such as statuses/ home_timeline) I get the proper response. The only difference that I can see is that the users/lookup requires a comma separated screen_name param. An example of a call I'm making is as follows: http://api.twitter.com/1/users/lookup.json?screen_name=Ditton,THEO_BROWN,jeff_phillipsoauth_consumer_key=[WITHHELD]oauth_nonce=3702675319114583140oauth_signature=Bjm61%2F0dNQ1YY%2B6DZrKfluh3brk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088234oauth_token=[WITHHELD]oauth_version=1.0 The above produces a 401. I though perhaps it's because the commas need to be encoded (however the examples I've seen that doesn't seem to be the case). Even if I tried sending up only 1 screen_name, however, it still fails with a 401. http://api.twitter.com/1/users/lookup.json?screen_name=Dittonoauth_consumer_key=[WITHHELD]oauth_nonce=12427699099383609456oauth_signature=gKSz6qPOiPKrJX6NqLuP7HjBkJ4%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088019oauth_token=[WITHHELD]oauth_version=1.0 Like I said, if I hit up the statuses/home_timeline endpoint it works fine. http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=[WITHHELD]oauth_nonce=4782314729649271771oauth_signature=LGfzsFEyzfHOszTPx1GPSzj%2BTN8%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271086839oauth_token=[WITHHELD]oauth_version=1.0 Anybody have any idears? Thanks!
Re: [twitter-dev] What's happening with Tweetie for Mac
I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] users/lookup and OAuthed Signed requests
creating oauth signatures is annoyingly subtle, isn't it? i would suggest playing with http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/and verifying the signature base string and signature you're generating to what that emits. On Mon, Apr 12, 2010 at 9:10 AM, ryan baldwin ryanbald...@gmail.com wrote: I'm having a heck of a time getting the users/lookup to work. I keep getting an invalid signature response, however if I try hitting other urls that require authentication (such as statuses/ home_timeline) I get the proper response. The only difference that I can see is that the users/lookup requires a comma separated screen_name param. An example of a call I'm making is as follows: http://api.twitter.com/1/users/lookup.json?screen_name=Ditton,THEO_BROWN,jeff_phillipsoauth_consumer_key=[WITHHELD]oauth_nonce=3702675319114583140oauth_signature=Bjm61%2F0dNQ1YY%2B6DZrKfluh3brk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088234oauth_token=[WITHHELD]oauth_version=1.0 The above produces a 401. I though perhaps it's because the commas need to be encoded (however the examples I've seen that doesn't seem to be the case). Even if I tried sending up only 1 screen_name, however, it still fails with a 401. http://api.twitter.com/1/users/lookup.json?screen_name=Dittonoauth_consumer_key=[WITHHELD]oauth_nonce=12427699099383609456oauth_signature=gKSz6qPOiPKrJX6NqLuP7HjBkJ4%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088019oauth_token=[WITHHELD]oauth_version=1.0 Like I said, if I hit up the statuses/home_timeline endpoint it works fine. http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=[WITHHELD]oauth_nonce=4782314729649271771oauth_signature=LGfzsFEyzfHOszTPx1GPSzj%2BTN8%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271086839oauth_token=[WITHHELD]oauth_version=1.0 Anybody have any idears? Thanks! -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Twitter lists fails
Sorry my english, this is an automatic Google Translate: For at least 2 weeks and stopped working the lists of Twitter. El fallo está a la hora de ver la lista de listas (valga la redundancia). The ruling is the time to see the list of lists (forgive the redundancy). Fail both the API and the Twitter interface. Twitter lists are recovered through lists 20 pages each, at the end of each page, Twitter returns a cursor that will be used to request the next and so on until you run out (cursor = 0).Twitter Now only return the 1st page, nothing more, but it does randomly, sometimes returns a page more. If you are over 20 lists you can check yourself on Twitter.com, shows you there is no page 20 for more. We have reported to support the API for days but has not yet been solved. If anyone knows anything about this and want to share is appreciated.
Re: [twitter-dev] What's happening with Tweetie for Mac
I second Abraham's view on this. On 12 Apr 2010, at 17:04, Abraham Williams wrote: There are a number of people that would like Twitter to consider open sourcing Tweetie for Mac: http://act.ly/1w1 There is much to be gained such as community contributed patches, a more competitive environment on the Mac, (just to name a few) and little to lose. I hope Twitter will consider this option in earnest. Abraham smime.p7s Description: S/MIME cryptographic signature
[twitter-dev] Re: Twitter Stream crossdomain.xml
Totally understood. You shouldn't be relaxing any security on anything you're not convinced will remain secure. Just remember you and I started this conversation six months ago ;) http://groups.google.com/group/twitter-development-talk/browse_frm/thread/d3230be66c27c88e On Apr 12, 11:43 am, Raffi Krikorian ra...@twitter.com wrote: as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off ofwww.twitter.commalicious Flash code could potentially get at user's cookies from any browser sessions from visitingwww.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote:
Re: [twitter-dev] Re: Twitter Stream crossdomain.xml
yup - totally :P just giving you an update that its been low on our priority list :P twitter now has a dedicated security manager, so i have just elevated this to his attention. On Mon, Apr 12, 2010 at 9:27 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Totally understood. You shouldn't be relaxing any security on anything you're not convinced will remain secure. Just remember you and I started this conversation six months ago ;) http://groups.google.com/group/twitter-development-talk/browse_frm/thread/d3230be66c27c88e On Apr 12, 11:43 am, Raffi Krikorian ra...@twitter.com wrote: as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off ofwww.twitter.commalicious Flash code could potentially get at user's cookies from any browser sessions from visitingwww.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.. .. http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash
[twitter-dev] Issue on Follow feature
Hi all, I have been struggling to get Follow feature working on a Java API that I am working on. For every request I am getting the error bellow: hash request/1/notifications/follow/ernandesmjr.xml/request errorThere was a problem following the specified user./error /hash According to the feature's spec, I just need a simple post request to a given user, e.g., http://api.twitter.com/1/notifications/follow/ernandesmjr.xml. To perform a quick and straighforward test, I created this HTML file: html head titleFollow Usertitle /head body form action= http://api.twitter.com/1/notifications/follow/ernandesmjr.xml; method=post input type=submit/ /form /body /html Either way, I get the same error as I get with Java. Any idea? Am I missing something? Thanks in advance. Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets.
Re: [twitter-dev] users/lookup and OAuthed Signed requests
That's the link I was looking for. Will play around and figure some of this stuff out. Thanks Raffi! - ryan. On Mon, Apr 12, 2010 at 10:14 AM, Raffi Krikorian ra...@twitter.com wrote: creating oauth signatures is annoyingly subtle, isn't it? i would suggest playing with http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/and verifying the signature base string and signature you're generating to what that emits. On Mon, Apr 12, 2010 at 9:10 AM, ryan baldwin ryanbald...@gmail.comwrote: I'm having a heck of a time getting the users/lookup to work. I keep getting an invalid signature response, however if I try hitting other urls that require authentication (such as statuses/ home_timeline) I get the proper response. The only difference that I can see is that the users/lookup requires a comma separated screen_name param. An example of a call I'm making is as follows: http://api.twitter.com/1/users/lookup.json?screen_name=Ditton,THEO_BROWN,jeff_phillipsoauth_consumer_key=[WITHHELD]oauth_nonce=3702675319114583140oauth_signature=Bjm61%2F0dNQ1YY%2B6DZrKfluh3brk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088234oauth_token=[WITHHELD]oauth_version=1.0 The above produces a 401. I though perhaps it's because the commas need to be encoded (however the examples I've seen that doesn't seem to be the case). Even if I tried sending up only 1 screen_name, however, it still fails with a 401. http://api.twitter.com/1/users/lookup.json?screen_name=Dittonoauth_consumer_key=[WITHHELD]oauth_nonce=12427699099383609456oauth_signature=gKSz6qPOiPKrJX6NqLuP7HjBkJ4%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271088019oauth_token=[WITHHELD]oauth_version=1.0 Like I said, if I hit up the statuses/home_timeline endpoint it works fine. http://api.twitter.com/1/statuses/home_timeline.json?oauth_consumer_key=[WITHHELD]oauth_nonce=4782314729649271771oauth_signature=LGfzsFEyzfHOszTPx1GPSzj%2BTN8%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1271086839oauth_token=[WITHHELD]oauth_version=1.0 Anybody have any idears? Thanks! -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Help required using OAuth
I am new to twitter API and also to web hosting and stuff. I have installed a WAMP and use localhost to run my PHP scripts. Now I want to register my app on Twitter and I require a callback URL which must be the URL to your “profile-page.php” file. Do I need a web host for this (kindly suggest a free web hosting service...I am a student :) just doing this for learning purposes) or can I still do this from localhost (using some hack) -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Introduce yourself!
Hi, I'm Amit Nanda. Just released an app called twextter: http://twitdom.com/twextter/ which we developed for marketing folk to run SMS contests/campaigns on Twitter (http://www.slideshare.net/ cellzapp/twextter-use-twitter-to-run-sms-contests-campaigns). We need to get elevated streaming access. @amit_nanda -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter Stream crossdomain.xml
w00t On Apr 12, 12:29 pm, Raffi Krikorian ra...@twitter.com wrote: yup - totally :P just giving you an update that its been low on our priority list :P twitter now has a dedicated security manager, so i have just elevated this to his attention. On Mon, Apr 12, 2010 at 9:27 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Totally understood. You shouldn't be relaxing any security on anything you're not convinced will remain secure. Just remember you and I started this conversation six months ago ;) http://groups.google.com/group/twitter-development-talk/browse_frm/th... On Apr 12, 11:43 am, Raffi Krikorian ra...@twitter.com wrote: as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off ofwww.twitter.commaliciousFlash code could potentially get at user's cookies from any browser sessions from visitingwww.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.. .. http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire
Re: [twitter-dev] What's happening with Tweetie for Mac
sorry for being cranky, but i just spent a year building a tweetie competitor. you can't fault a guy for saying ouch while your knife is still sticking out of his back, right? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 9:10 AM, Jesse Stay wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] What's happening with Tweetie for Mac
Fred Thompson? What's Law Order got to do with anything? (Wilson?) --ab On Mon, Apr 12, 2010 at 12:10 PM, Jesse Stay jesses...@gmail.com wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Issue on Follow feature
You can use http://twitter4j.org for your app. It's an open source API for Java. Has an awesome community around it as well and the developer Yusuke is smart and helpful! On Apr 12, 9:29 pm, Ernandes Jr. ernan...@gmail.com wrote: Hi all, I have been struggling to get Follow feature working on a Java API that I am working on. For every request I am getting the error bellow: hash request/1/notifications/follow/ernandesmjr.xml/request errorThere was a problem following the specified user./error /hash According to the feature's spec, I just need a simple post request to a given user, e.g.,http://api.twitter.com/1/notifications/follow/ernandesmjr.xml. To perform a quick and straighforward test, I created this HTML file: html head titleFollow Usertitle /head body form action=http://api.twitter.com/1/notifications/follow/ernandesmjr.xml; method=post input type=submit/ /form /body /html Either way, I get the same error as I get with Java. Any idea? Am I missing something? Thanks in advance. Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Some thoughts leading up to Chirp
Thanks, Ryan! I'm looking forward to Thursday's discussion. I think that as 3rd party Twitter developers, we think of ourselves existing somewhere in the highest bracket of engaged users. Whether it's a valid concern remains to be proven, but a lot of folks (myself included) are now wondering if maximize benefit to users is inclusive of us too. Is it inclusive of developers? Is it inclusive of our existing users? Is it inclusive of the user base we're trying to grow? I hope it is. Twitter's developer-centric nature is what got me excited about supporting the platform in the first place. We all have a joint interest in creating the best possible end-user experience. What I'd love to see from Twitter is an open commitment to supporting 3rd party developers in their attempts at achieving this goal. I'm less concerned about Twitter creating or purchasing applications with the same functionality as my own. What I do worry about, however, is if Twitter's applications will have access to private APIs or exclusive features that prevent 3rd-party developers from creating a competitive or superior experience. I also wonder whether the goal is to improve access to data services like the search and stream APIs (scalability permitting) to a larger audience, or if the plan is to continue to develop exclusive partnerships that have premier access. I could be wrong, but an ongoing commitment to open-data and non- exclusive APIs should lead to the best applications and the most diverse Twitter ecosystem--an ecosystem that allows users to decide, by their use of both official and 3rd-party products, where maximized value lies. See you all at Chirp! @jmstriegel -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What's happening with Tweetie for Mac
Ryan, Great news thanks for the update! Jesse, Well said. On Apr 12, 10:40 am, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan
Re: [twitter-dev] Re: Issue on Follow feature
In fact, I am developing a mobile Java API, not an app, which I am attempting to get this feature working. Anyway, I will take a look at twitter4j source code to see which magic it performs. :) On Mon, Apr 12, 2010 at 2:19 PM, nischalshetty nischalshett...@gmail.comwrote: You can use http://twitter4j.org for your app. It's an open source API for Java. Has an awesome community around it as well and the developer Yusuke is smart and helpful! On Apr 12, 9:29 pm, Ernandes Jr. ernan...@gmail.com wrote: Hi all, I have been struggling to get Follow feature working on a Java API that I am working on. For every request I am getting the error bellow: hash request/1/notifications/follow/ernandesmjr.xml/request errorThere was a problem following the specified user./error /hash According to the feature's spec, I just need a simple post request to a given user, e.g., http://api.twitter.com/1/notifications/follow/ernandesmjr.xml. To perform a quick and straighforward test, I created this HTML file: html head titleFollow Usertitle /head body form action= http://api.twitter.com/1/notifications/follow/ernandesmjr.xml; method=post input type=submit/ /form /body /html Either way, I get the same error as I get with Java. Any idea? Am I missing something? Thanks in advance. Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets. -- To unsubscribe, reply using remove me as the subject. -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets.
[twitter-dev] Re: What's happening with Tweetie for Mac
Ryan, Thanks for clarifying, finally, at least. Rebranded Twitter or not, Tweetie as owned and developed by Twitter basically reinforces and confirms everything that we posted on the Nambu blog this morning: Twitter will take anything significant built around Twitter for itself, 100%. Twitter is now officially developing native applications on three platforms: iPhone OS, OSX and Blackberry, all free. Simply brutal. But I am not nearly affected as the iPhone developers. They should be rightfully livid that Twitter moved to wipe them out and take all advertising revenue (iAd and other stuff) on the iPhone and iPad for themselves rather than share it, as almost all other platforms do. Pretty sad. Make no mistake, Twitter for iPhone will take all significant market share, and there is nothing any of the developers there that have done great work can do about it. If you do not see this, you do not understand the basics of business. Making Tweetie free is pretty brutal as well, but only because Twitter is doing it. Everyone else should be put on notice that you will be next, as we have been. Mr. Wilson and Twitter, with these moves, and have basically told everyone of competence that they must accept their development efforts as only ending up as a nice lifestyle business. Anything more, and Twitter will move to take it from you, simple as that. --ejw Eric Woodward Email: e...@nambuc.om On Apr 12, 10:39 am, Michael Macasek mich...@oneforty.com wrote: Ryan, Great news thanks for the update! Jesse, Well said. On Apr 12, 10:40 am, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Some thoughts leading up to Chirp
Absolutely right but then the comment, it's dangerous to be a Twitter only client comes to mind. The formula then becomes to develop for other networks (StatusNet?). Good for the end user and other networks but ultimately good for Twitter? The argument could be made that it's good for everyone...or maybe counter-productive since the wheel is being reinvented? Twitter, help us find another formula to continue to help you... On Apr 12, 6:34 am, notinfluential notinfluent...@gmail.com wrote: On Apr 12, 2:44 am, Jason Rundell jason.rund...@gmail.com wrote: When will Twitter answer: 1) Why did Twitter acquire Tweetie? 2) What is Twitter planning to do with Tweetie? Since when does Twitter owe you or any of us any sort of explanation for their business practices? Lemme get this straight. Twitter is FREE. The Twitter API is public, well documented, and FREE. Our privilege is to build tools and businesses on top of Twitter's FREE services. Twitter doesn't want a cut of your business. They don't require approval of your apps. But for some reason you (and others) feel entitled to an explanation, or details somehow outlining their strategy and practices? The tone of this group never ceases to amaze me. Get back to coding and building cool stuff. @notinfluential -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What's happening with Tweetie for Mac
While this is bad news to handful of iPhone based app developers, it's a great news for millions of iphone users who will be able to get Twitter app for free. On Apr 12, 2:46 pm, Eric Woodward e...@nambu.com wrote: Ryan, Thanks for clarifying, finally, at least. Rebranded Twitter or not, Tweetie as owned and developed by Twitter basically reinforces and confirms everything that we posted on the Nambu blog this morning: Twitter will take anything significant built around Twitter for itself, 100%. Twitter is now officially developing native applications on three platforms: iPhone OS, OSX and Blackberry, all free. Simply brutal. But I am not nearly affected as the iPhone developers. They should be rightfully livid that Twitter moved to wipe them out and take all advertising revenue (iAd and other stuff) on the iPhone and iPad for themselves rather than share it, as almost all other platforms do. Pretty sad. Make no mistake, Twitter for iPhone will take all significant market share, and there is nothing any of the developers there that have done great work can do about it. If you do not see this, you do not understand the basics of business. Making Tweetie free is pretty brutal as well, but only because Twitter is doing it. Everyone else should be put on notice that you will be next, as we have been. Mr. Wilson and Twitter, with these moves, and have basically told everyone of competence that they must accept their development efforts as only ending up as a nice lifestyle business. Anything more, and Twitter will move to take it from you, simple as that. --ejw Eric Woodward Email: e...@nambuc.om On Apr 12, 10:39 am, Michael Macasek mich...@oneforty.com wrote: Ryan, Great news thanks for the update! Jesse, Well said. On Apr 12, 10:40 am, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Some thoughts leading up to Chirp
I have much to do before my flight tomorrow so this is rough and should be read as such. Even in light of recent events Chirp is looking to be a good time that will hopefully result in fruitful dialog from all. Considering the magnitude of the issue it would have been, in my mind, pertinent to have had this email ready to go on Friday for what must have been expected pushback. Leaving the overactive imaginations of netizens to fester is rarely helpful. I think many of us understand the reasons but are now feeling threatened because space previously understood to be of little direct interest from Twitter is now very much squarely in Twitter's targets. Usability is always a concern and the explanation of Twitter has always been difficult at best, but I think there were better ways to handle this they would have resulted in less developer duress. I find it slightly ironic that some of the blame is Twitter's restrictions on the use of trademark design and terms, though I realized Twitter has it's interests to protect and so I won't fault you on that. Suddenly announcing stepping into the developer space seems like the easy fix for you. But at what cost? I've been developing on the Twitter platform for a long time and I'm not going to think twice about future projects where before I didn't. Many other new and experienced developers are along the same thought process. Maybe you should have worked with developers to smooth over the onboarding process instead. A good start would have been design documentation to present users with a more consistent experience. Here is the text you should present new users, here is the icon you should use for retweets, etc. Much could have been done without impeding the creativity of developers while still making it easier for users. Would users still get lost looking for an Official app? Probably, but I would argue it would have been a better result than the distrust now implanted in all developers thoughts. The loss of a user is the loss of a single user but the loss of a developer could be the loss of thousands of users. The communication between Twitter and developers has look more and more like this: Twitter: We are rolling out this change. Devs: Wait! What? Twitter: ... Devs: Wait! What? Twitter: ... Devs: Wait! What? Twitter: Ok. we took your feed back and will tweak it a little. Devs: But what about this? Twitter: ... Yes this is an exaggeration but the idea holds true. There has been less of an ongoing dialog and more of Twitter dictating changes. Is it Twitter's right? Yes. Is it our right to bitch and move to other platforms? Yes. Smaller issues seem to have much better dialog between individual Twitter developers working on the specific subsystem which is great but the small issues also screws less developers when things change. Sometimes I feel sorry for the platform team (who are all true hackers at heart) for being stuck between the business side of Twitter and the third-party developers. We can't seed the business side telling you no the the nifty features I'm sure you would love to developer for us. All we just see you saying no. There is a level of transparency that I want from Twitter which is understandably not an option for the majority of startups. (*cough* *cough* @dacort) That dream of transparency is reminiscent of a time when the API group felt more like an open source project where the platform team seemed more like overworked committers then employees of an multi-million dollar corporation. I would also like to point you to @funkatron's heartfelt blog post much of which holds true for me: http://funkatron.com/site/comments/my-friend-twitter/ Many of you will see me at Chirp of which I am looking forward to, but Chirp no longer has the shiny luster it once had and as Twitter overshadows the community more and more I too will look more and more to other platform and other communities. I hope we didn't use up all your minutes Ryan. :-P @Abraham On Sun, Apr 11, 2010 at 17:22, Ryan Sarver rsar...@twitter.com wrote: I wanted to email everyone and share my thoughts on the acquisition from Friday, the communication around it and where we are going from here. We're incredibly excited about Chirp, and I think an open dialogue going into it is important. I look forward to meeting many of you there and continuing the discussion. We love the Twitter ecosystem and work hard every day to help support you and make the platform you are building on as successful as it can be for everyone involved. We love the variety that developers have built around the Twitter experience and it's a big part of the success we've seen. However when we dug in a little bit we realized that it was causing massive confusion among user's who had an iPhone and were looking to use Twitter for the first time. They would head to the App Store, search for Twitter and would see results that included a lot of apps that had nothing to do with Twitter and a few that did, but
Re: [twitter-dev] How to find the frequency of messages exchanged between 2 users
You will have to pull the direct messages and mentions from both users and correlate the data yourself. Abraham On Mon, Apr 12, 2010 at 12:04, Dushyant dushyantaror...@gmail.com wrote: I am a beginner in twitter API. I wish to count the number of tweets and direct messages exchanged by 2 people. Is there a field which can directly show me this. What should I do? -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] What's happening with Tweetie for Mac
Not at all - I've spent 3 years building features constantly replaced by Twitter (or killed due to Twitter changing the TOS). I've been there, and had plenty of my share of crankiness - I guess I'm used to it now, and I realize that's just a part of writing apps for the ecosystem (or any 3rd party ecosystem for that matter). The more Twitter can be transparent about things like this, the happier I am. I'm glad they're starting to open up on where they stand. I hope this continues. Jesse On Mon, Apr 12, 2010 at 11:12 AM, Isaiah Carew isa...@me.com wrote: sorry for being cranky, but i just spent a year building a tweetie competitor. you can't fault a guy for saying ouch while your knife is still sticking out of his back, right? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 9:10 AM, Jesse Stay wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What's happening with Tweetie for Mac
Eric, I disagree. This just means they've put us on notice that if our apps completely revolve around Twitter we risk going into competition with them. I don't think there's anything wrong with that, although it is frustrating, I agree (this is nothing new - they've been doing this for the last 3 years). The way to succeed on the Twitter platform is to build apps that don't rely on Twitter, but instead use Twitter as a complement to their own ecosystem. Your app should be its own platform, relying on other platforms to complement it, not the other way around. I think that's what Twitter is trying to iterate here, and we see that with the coming advent of @anywhere. I love that they're finally being clear on this, as frustrating as it is for those it affects directly (although the writing's been on the wall for awhile now - I certainly have complained many times about this). Jesse On Mon, Apr 12, 2010 at 12:46 PM, Eric Woodward e...@nambu.com wrote: Ryan, Thanks for clarifying, finally, at least. Rebranded Twitter or not, Tweetie as owned and developed by Twitter basically reinforces and confirms everything that we posted on the Nambu blog this morning: Twitter will take anything significant built around Twitter for itself, 100%. Twitter is now officially developing native applications on three platforms: iPhone OS, OSX and Blackberry, all free. Simply brutal. But I am not nearly affected as the iPhone developers. They should be rightfully livid that Twitter moved to wipe them out and take all advertising revenue (iAd and other stuff) on the iPhone and iPad for themselves rather than share it, as almost all other platforms do. Pretty sad. Make no mistake, Twitter for iPhone will take all significant market share, and there is nothing any of the developers there that have done great work can do about it. If you do not see this, you do not understand the basics of business. Making Tweetie free is pretty brutal as well, but only because Twitter is doing it. Everyone else should be put on notice that you will be next, as we have been. Mr. Wilson and Twitter, with these moves, and have basically told everyone of competence that they must accept their development efforts as only ending up as a nice lifestyle business. Anything more, and Twitter will move to take it from you, simple as that. --ejw Eric Woodward Email: e...@nambuc.om On Apr 12, 10:39 am, Michael Macasek mich...@oneforty.com wrote: Ryan, Great news thanks for the update! Jesse, Well said. On Apr 12, 10:40 am, Ryan Sarver rsar...@twitter.com wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Help required using OAuth
Whilst I personally use a more technical solution, I believe if you put 127.0.0.1 in place of localhost in the Application callback url it works - eg instead of http://localhost/path/to/your/callback/file put http://127.0.0.1/path/to/your/callback/file. It's possible that doesn't work any longer, I've not tested it in a while, but it certainly used to from memory. On Apr 12, 5:34 pm, Dushyant dushyantaror...@gmail.com wrote: I am new to twitter API and also to web hosting and stuff. I have installed a WAMP and use localhost to run my PHP scripts. Now I want to register my app on Twitter and I require a callback URL which must be the URL to your “profile-page.php” file. Do I need a web host for this (kindly suggest a free web hosting service...I am a student :) just doing this for learning purposes) or can I still do this from localhost (using some hack) -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] What's happening with Tweetie for Mac
What? They're not the same person? All this time... ;-) Yes, I meant Wilson. On Mon, Apr 12, 2010 at 11:15 AM, Andrew Badera and...@badera.us wrote: Fred Thompson? What's Law Order got to do with anything? (Wilson?) --ab On Mon, Apr 12, 2010 at 12:10 PM, Jesse Stay jesses...@gmail.com wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Retweet rules. What I'm missing?
What error are you getting back from Twitter? You can retweet public statuses that are not your own and that you have not retweeted already. I don't know of any other restrictions other then probably some rate limit. Abraham On Sun, Apr 11, 2010 at 23:51, hgc2002 herman.go...@gmail.com wrote: I'm having lots of strange problems with retweets. Sometimes it works, sometimes don't. Appart of that, the error messages comming from Twitter are not 100% clear. I'm reenginering my mind simply asking to everybody: What are the retweets rules and/or conditions to succed or fail? I mean: what can be retweeted? what cannot be retweeted? Is there any common list of error messages on retweeting? Thank you very much for your help! Regards, Herman Gomez. Spain. -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] OAuth Revoke Token?
This seems like to much of an edge case for Twitter to spend resources on. Abraham On Thu, Apr 8, 2010 at 12:23, Mike Repass mike.rep...@gmail.com wrote: A scenario for justifying invalidateToken: - User visits AwesomeApp and wants to connect his Twitter account - AwesomeApp redirects to Twitter's OAuth flow - User fails to notice that someone else, UserX, is already logged in to Twitter in the current browser and clicks through - AwesomeApp detects (somehow, perhaps later) that the wrong Twitter user is connected. They can be a good citizen and revoke the token completely, then send the user back through a full OAuth flow that asks for username/password regardless of sign-in state. Just my $0.02, Mike On Thu, Apr 8, 2010 at 12:06 PM, Josh Roesslein jroessl...@gmail.comwrote: There is no API endpoint that I know of and don't think one should exist. Users should not trust thirdparties to self-revoke access to their accounts. Users should know how to do it from twitter.com via the connections page. It might be nice if we could generate a redirect link to a page on twitter.com where the user can then revoke the access (sort of like the authorization page). Josh On Wed, Apr 7, 2010 at 11:59 PM, Ryan Amos amos.r...@gmail.com wrote: Is there anyway to send a request to revoke a token completely without requiring the user goto their connections page on twitter? We allow our users to revoke access via our application, but that only revokes it on our side. The application would still show up on their twitter.com connections page. Google has one by sending a request to: https://www.google.com/accounts/accounts/AuthSubRevokeToken -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] OAuth Revoke Token?
This seems like too much of an edge case for Twitter to spend resources on. You can always include force_login=true to always prompt the user for credentials. Abraham On Thu, Apr 8, 2010 at 12:23, Mike Repass mike.rep...@gmail.com wrote: A scenario for justifying invalidateToken: - User visits AwesomeApp and wants to connect his Twitter account - AwesomeApp redirects to Twitter's OAuth flow - User fails to notice that someone else, UserX, is already logged in to Twitter in the current browser and clicks through - AwesomeApp detects (somehow, perhaps later) that the wrong Twitter user is connected. They can be a good citizen and revoke the token completely, then send the user back through a full OAuth flow that asks for username/password regardless of sign-in state. Just my $0.02, Mike On Thu, Apr 8, 2010 at 12:06 PM, Josh Roesslein jroessl...@gmail.comwrote: There is no API endpoint that I know of and don't think one should exist. Users should not trust thirdparties to self-revoke access to their accounts. Users should know how to do it from twitter.com via the connections page. It might be nice if we could generate a redirect link to a page on twitter.com where the user can then revoke the access (sort of like the authorization page). Josh On Wed, Apr 7, 2010 at 11:59 PM, Ryan Amos amos.r...@gmail.com wrote: Is there anyway to send a request to revoke a token completely without requiring the user goto their connections page on twitter? We allow our users to revoke access via our application, but that only revokes it on our side. The application would still show up on their twitter.com connections page. Google has one by sending a request to: https://www.google.com/accounts/accounts/AuthSubRevokeToken -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] OAuth Revoke Token?
additionally, in oauth 2.0 we will have the ability to set expiration dates for tokens, so after a certain time periods, tokens could just automatically expire. i rather not have an actual API that would expire a token as that seems like an interesting attack vector. On Mon, Apr 12, 2010 at 12:53 PM, Abraham Williams 4bra...@gmail.comwrote: This seems like too much of an edge case for Twitter to spend resources on. You can always include force_login=true to always prompt the user for credentials. Abraham On Thu, Apr 8, 2010 at 12:23, Mike Repass mike.rep...@gmail.com wrote: A scenario for justifying invalidateToken: - User visits AwesomeApp and wants to connect his Twitter account - AwesomeApp redirects to Twitter's OAuth flow - User fails to notice that someone else, UserX, is already logged in to Twitter in the current browser and clicks through - AwesomeApp detects (somehow, perhaps later) that the wrong Twitter user is connected. They can be a good citizen and revoke the token completely, then send the user back through a full OAuth flow that asks for username/password regardless of sign-in state. Just my $0.02, Mike On Thu, Apr 8, 2010 at 12:06 PM, Josh Roesslein jroessl...@gmail.comwrote: There is no API endpoint that I know of and don't think one should exist. Users should not trust thirdparties to self-revoke access to their accounts. Users should know how to do it from twitter.com via the connections page. It might be nice if we could generate a redirect link to a page on twitter.com where the user can then revoke the access (sort of like the authorization page). Josh On Wed, Apr 7, 2010 at 11:59 PM, Ryan Amos amos.r...@gmail.com wrote: Is there anyway to send a request to revoke a token completely without requiring the user goto their connections page on twitter? We allow our users to revoke access via our application, but that only revokes it on our side. The application would still show up on their twitter.com connections page. Google has one by sending a request to: https://www.google.com/accounts/accounts/AuthSubRevokeToken -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] How to find the frequency of messages exchanged between 2 users
On 04/12/2010 12:20 PM, Abraham Williams wrote: You will have to pull the direct messages and mentions from both users and correlate the data yourself. Abraham Moreover, accessing the direct messages of *two* users involves authenticating as *both* of them. It is highly unlikely you will be permitted to do so by people who don't have a legal contract with you. And that agreement should *clearly* specify * what is permitted and forbidden, and * *penalties* for breaking that agreement. That's the world we now live in - get used to it. This whole click this here button and get nifty stuff for free attitude is starting to unravel. -- M. Edward (Ed) Borasky http://borasky-research.net/m-edward-ed-borasky/ @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
[twitter-dev] Re: Twitter lists fails
We are seeing the same issue with list cursors not working and have also reported it and heard nothing back. Very frustrating since we've done a lot of work to properly support lists in our App. Would love it if someone at Twitter could give us an idea of when this might be fixed? On Apr 12, 8:49 am, fdelpozo iprox...@gmail.com wrote: Sorry my english, this is an automatic Google Translate: For at least 2 weeks and stopped working the lists of Twitter. El fallo está a la hora de ver la lista de listas (valga la redundancia). The ruling is the time to see the list of lists (forgive the redundancy). Fail both the API and the Twitter interface. Twitter lists are recovered through lists 20 pages each, at the end of each page, Twitter returns a cursor that will be used to request the next and so on until you run out (cursor = 0).Twitter Now only return the 1st page, nothing more, but it does randomly, sometimes returns a page more. If you are over 20 lists you can check yourself on Twitter.com, shows you there is no page 20 for more. We have reported to support the API for days but has not yet been solved. If anyone knows anything about this and want to share is appreciated.
[twitter-dev] Thoughts moving forward
I'm looking forward to Chirp and the dialogs that will happen. The Coop session on the second day looks to be the best time to have a heart to heart between third-party developers and the platform team. I think it would be good to have the third-party developers meet before then have a discussion about what we want and what our priorities are. I'm not sure when the best time would be. During the afternoon break or at 9pm on the first day seem like good times. I also think it would be respectful of Twitter employees to not attend this gathering so developers can be frank and honest. There will be many other opportunities. Abraham -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Thoughts moving forward
This was the conclusion to my email to Ryan... a few actionable points: Immediate term: * Carve out a block during the Chirp hack day to engage with the developer community with the specific intent of figuring out ways to make the issue tracker and forums more effective. (The conference shouldn't be an entirely push experience for the Twitter team) * Carve out a block during the Chirp hack day to review the open issues in the issue tracker and reset priorities on open issues as a collaborative effort between the community and Twitter. (You will never have a better opportunity to do this in one shot) * Work *with the developers* to define the role of Developer Advocate. (I don't think there will be a better opportunity than Chirp for this one as well) Longer term: * Fill the newly defined Developer Advocate role. Provide a mechanism for the community to formally review the Developer Advocate's performance over time. (this is not about Taylor, he sounds like an awesome member of the team) * Scrap the V2 roadmap and replace it whatever kind of roadmap can have realistic estimates, and update the roadmap and its estimates as they change. If you need help figuring out how to build a better roadmap, I'm sure there are lots of folks with ideas they'd love to contribute. * Have upper management issue reflections on their respective areas of the company. Talk about what the company is doing well and what it's still struggling with. Don't b.s. these. It would be great, for example, to hear from you about whether or not new roles need to be filled and why. On Apr 12, 4:31 pm, Abraham Williams 4bra...@gmail.com wrote: I'm looking forward to Chirp and the dialogs that will happen. The Coop session on the second day looks to be the best time to have a heart to heart between third-party developers and the platform team. I think it would be good to have the third-party developers meet before then have a discussion about what we want and what our priorities are. I'm not sure when the best time would be. During the afternoon break or at 9pm on the first day seem like good times. I also think it would be respectful of Twitter employees to not attend this gathering so developers can be frank and honest. There will be many other opportunities. Abraham -- Abraham Williams | Developer for hire |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: Thoughts moving forward
Maybe we should get Twitter to extend the conference a few days... :-P BTW I will be in SF until the 22 if anybody wants to continue the conversations or just wants to get together. Abraham On Mon, Apr 12, 2010 at 13:39, Orian Marx (@orian) or...@orianmarx.comwrote: This was the conclusion to my email to Ryan... a few actionable points: Immediate term: * Carve out a block during the Chirp hack day to engage with the developer community with the specific intent of figuring out ways to make the issue tracker and forums more effective. (The conference shouldn't be an entirely push experience for the Twitter team) * Carve out a block during the Chirp hack day to review the open issues in the issue tracker and reset priorities on open issues as a collaborative effort between the community and Twitter. (You will never have a better opportunity to do this in one shot) * Work *with the developers* to define the role of Developer Advocate. (I don't think there will be a better opportunity than Chirp for this one as well) Longer term: * Fill the newly defined Developer Advocate role. Provide a mechanism for the community to formally review the Developer Advocate's performance over time. (this is not about Taylor, he sounds like an awesome member of the team) * Scrap the V2 roadmap and replace it whatever kind of roadmap can have realistic estimates, and update the roadmap and its estimates as they change. If you need help figuring out how to build a better roadmap, I'm sure there are lots of folks with ideas they'd love to contribute. * Have upper management issue reflections on their respective areas of the company. Talk about what the company is doing well and what it's still struggling with. Don't b.s. these. It would be great, for example, to hear from you about whether or not new roles need to be filled and why. On Apr 12, 4:31 pm, Abraham Williams 4bra...@gmail.com wrote: I'm looking forward to Chirp and the dialogs that will happen. The Coop session on the second day looks to be the best time to have a heart to heart between third-party developers and the platform team. I think it would be good to have the third-party developers meet before then have a discussion about what we want and what our priorities are. I'm not sure when the best time would be. During the afternoon break or at 9pm on the first day seem like good times. I also think it would be respectful of Twitter employees to not attend this gathering so developers can be frank and honest. There will be many other opportunities. Abraham -- Abraham Williams | Developer for hire |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. -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: What's happening with Tweetie for Mac
I've spent eight months on a new Twitter client myself, and I had planned to start showing it at Chirp. Mine is in-browser so I suppose it's not quite the same situation, but in reality I do think they are all, for the most part, in competition with each other - no? On Apr 12, 1:12 pm, Isaiah Carew isa...@me.com wrote: sorry for being cranky, but i just spent a year building a tweetie competitor. you can't fault a guy for saying ouch while your knife is still sticking out of his back, right? isaiahhttp://twitter.com/isaiah On Apr 12, 2010, at 9:10 AM, Jesse Stay wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan
Re: [twitter-dev] Re: Twitter lists fails
I believe we confirmed this - we're looking into it. On Apr 12, 2010, at 3:49 PM, Spraycode joey.fernan...@gmail.com wrote: We are seeing the same issue with list cursors not working and have also reported it and heard nothing back. Very frustrating since we've done a lot of work to properly support lists in our App. Would love it if someone at Twitter could give us an idea of when this might be fixed? On Apr 12, 8:49 am, fdelpozo iprox...@gmail.com wrote: Sorry my english, this is an automatic Google Translate: For at least 2 weeks and stopped working the lists of Twitter. El fallo está a la hora de ver la lista de listas (valga la redundancia). The ruling is the time to see the list of lists (forgive the redundancy). Fail both the API and the Twitter interface. Twitter lists are recovered through lists 20 pages each, at the end of each page, Twitter returns a cursor that will be used to request the next and so on until you run out (cursor = 0).Twitter Now only return the 1st page, nothing more, but it does randomly, sometimes returns a page more. If you are over 20 lists you can check yourself on Twitter.com, shows you there is no page 20 for more. We have reported to support the API for days but has not yet been solved. If anyone knows anything about this and want to share is appreciated. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter lists fails
Correct. We've actually identified the issue, are working on a fix and will deploy as soon as possible. Unfortunately that probably means early next week. ---Mark http://twitter.com/mccv On Mon, Apr 12, 2010 at 2:00 PM, Raffi Krikorian ra...@twitter.com wrote: I believe we confirmed this - we're looking into it. On Apr 12, 2010, at 3:49 PM, Spraycode joey.fernan...@gmail.com wrote: We are seeing the same issue with list cursors not working and have also reported it and heard nothing back. Very frustrating since we've done a lot of work to properly support lists in our App. Would love it if someone at Twitter could give us an idea of when this might be fixed? On Apr 12, 8:49 am, fdelpozo iprox...@gmail.com wrote: Sorry my english, this is an automatic Google Translate: For at least 2 weeks and stopped working the lists of Twitter. El fallo está a la hora de ver la lista de listas (valga la redundancia). The ruling is the time to see the list of lists (forgive the redundancy). Fail both the API and the Twitter interface. Twitter lists are recovered through lists 20 pages each, at the end of each page, Twitter returns a cursor that will be used to request the next and so on until you run out (cursor = 0).Twitter Now only return the 1st page, nothing more, but it does randomly, sometimes returns a page more. If you are over 20 lists you can check yourself on Twitter.com, shows you there is no page 20 for more. We have reported to support the API for days but has not yet been solved. If anyone knows anything about this and want to share is appreciated. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Thoughts moving forward
I have to fly out on Friday morning, but I'd love to participate in the discussion. I'm still pretty new to the Twitter developer club, but I'm really looking forward to meeting you all. Jason @jmstriegel -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] How to find the frequency of messages exchanged between 2 users
Direct messages are by nature supposed to be private between sender and receiver (and vice versa). My understanding is that they cannot be accessed by anyone apart from those authorised to access them (account holders). If I am worng in this assumption, I have two years worth of scurrilous if not libellous DMs to clear up fast. @mentions are another matter, but there is no api call to find them. On 12 April 2010 21:04, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/12/2010 12:20 PM, Abraham Williams wrote: You will have to pull the direct messages and mentions from both users and correlate the data yourself. Abraham Moreover, accessing the direct messages of *two* users involves authenticating as *both* of them. It is highly unlikely you will be permitted to do so by people who don't have a legal contract with you. And that agreement should *clearly* specify * what is permitted and forbidden, and * *penalties* for breaking that agreement. That's the world we now live in - get used to it. This whole click this here button and get nifty stuff for free attitude is starting to unravel. -- M. Edward (Ed) Borasky http://borasky-research.net/m-edward-ed-borasky/ @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] Re: What's happening with Tweetie for Mac
On 04/12/2010 01:58 PM, Orian Marx (@orian) wrote: I've spent eight months on a new Twitter client myself, and I had planned to start showing it at Chirp. Mine is in-browser so I suppose it's not quite the same situation, but in reality I do think they are all, for the most part, in competition with each other - no? Yes, there is a competition - two competitions, in fact: 1. Clients that interface only to Twitter, and 2. Clients that interface to Twitter and other services. If we narrow the field to Twitter-only clients, the stats are very clear: http://twitter.com has the lion's share of the tweet count, with uberTwitter a distant second and TweetDeck third. See http://tdash.org/stats/clients for the numbers. Tweetie is number 11 on the list - *1.39%* of all the tweets posted come from Tweetie! In short, Twitter clients are jockeying for position in a crowded field with 39.31% of the usage already subtracted out by Twitter's main web page. See Which Twitter Clients Do People Actually Use? http://meb.tw/9iRfxU for some analysis. -- M. Edward (Ed) Borasky http://borasky-research.net/m-edward-ed-borasky/ @znmeb I've always regarded nature as the clothing of God. ~Alan Hovhaness -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Chirp tracking on MadChat
On 04/12/2010 02:53 PM, Chad Etzel wrote: Hi all, I have setup a special Chirp tweet tracking page on MadChat (an as of yet unreleased site I've been working on) so folks who are not at the conference (or even if you are) can easily read all of the Chirp chatter. It is intentionally minimally designed to look like a chatroom and have no avatars, so you get the max text-per-screen ratio. Bonus points if you use the Terminal Skin under Settings. The url is http://madch.at/chirp It is tracking the #chirp hashtag as well as all @chirp mentions. There is little happening there right now, but I wanted to get the word out. It's using the Streaming API, so it feels just like a chatroom. To reply to a tweet, just click on the username on the lefthand side of the chatroom to link the reply to that tweet. Stuff you type will be tweeted out once you hit Enter, so be mindful of that. Anyway, hope this helps some people be able to monitor the backchannel of tweets and is another cool example of what you can do with the Streaming API. chirpity chirp, -Chad There is also TweetChat and TwapperKeeper for hashtag-mediated chats and archiving, respectively. I think the TwapperKeeper developer said he was coming to Chirp, but I don't know about TweetChat. But let's use yours ;-) -- 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] High frequency of search API timeouts
Is anybody else seeing a high frequency of search timeouts? I have a periodic search with 6 keyword ORs and 3 negating attributes (i.e. -from=, -source=, -RT) Seemed to be working fine until yesterday. Here's the weird part though. First case: - execute complex search directly in browser and it times out like my app gets on App Engine Second case: - run a simple, single word, search in a browser - then run the complex search immediately after and it works It's almost like it has to be primed? It also seems like the -source parameter is the problem, but that could just be anecdotal and clouded by my second case example above. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Fred Wilson article on Twitter API
*I'm extremely unsettled. *I'm agreeing with Dewald Pretorius's comments above... Here's an earlier related story: I was the first to market with a drag drop interface for Windows...Yes: back in the stone ages of windows 2.x and windows 3.0 there was no such thing. And soon after HP, Xerox, and some other companies (Norton = Symantec, Central Point) all started to play in that arena. And after a longer while Microsoft said, sorry folks, this is going to be our playground... and wiped us all out of there... I swore I would not ride someone's coattails again, but I have (it's not possible to not ride on someone's coattails)... But in this case Twitter didn't seem so predatory, and I want to believe in the good side of social vs it's just business, and I've met Ev and some twitter folk (before twitter) and was impressed with them as people. So I'm extremely unsettled by the lack of clarity on Twitter's business intent. I would appreciate some clarity on Twitter biz direction. Fred Wilson's post on top of other things that have been said by Twitter, and the dialogs between Arrington and Loic are extremely unsettling. I'd rather fail quickly, than go through a long, slow, and expensive death. With that said, if I were in your shoes holding the cards, even if you're a kind player, I cannot imagine doing anything much different. And if it were my business you were purchasing, I'd be elated, and sympathetic to everyone else. You're more likely figuring it all out, just as we are. I'll live with being unsettled, but if you can clarify, it would be appreciated. jeffrey greenberg http://www.tweettronics.com http://www.jeffrey-greenberg.com On Sun, Apr 11, 2010 at 7:14 AM, Dewald Pretorius dpr...@gmail.com wrote: You are also free and welcome to express your opinions, even when hiding behind a veil of anonymity. On Apr 11, 9:03 am, notinfluential notinfluent...@gmail.com wrote: Totally over-dramatic. And way beyond annoying at this point. Dewald, quit your whining and either get back to coding and doing something productive, or maybe you should aim your posts at this group instead: http://groups.google.com/group/delusional-socialist-development-talk @notinfluential On Apr 10, 11:05 am, Raffi Krikorian ra...@twitter.com wrote: Twitter has now displayed a distinctive predatorial stance towards the developer ecosystem. That's incredibly overdramatic, I think. We have, and continue to maintain a platform that will allow for a vibrant ecosystem. We want everybody to succeed.- Hide quoted text - - Show quoted text - -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter lists fails
Thanks guys. Really appreciate it. On Apr 12, 2:02 pm, Mark McBride mmcbr...@twitter.com wrote: Correct. We've actually identified the issue, are working on a fix and will deploy as soon as possible. Unfortunately that probably means early next week. ---Mark http://twitter.com/mccv On Mon, Apr 12, 2010 at 2:00 PM, Raffi Krikorian ra...@twitter.com wrote: I believe we confirmed this - we're looking into it. On Apr 12, 2010, at 3:49 PM, Spraycode joey.fernan...@gmail.com wrote: We are seeing the same issue with list cursors not working and have also reported it and heard nothing back. Very frustrating since we've done a lot of work to properly support lists in our App. Would love it if someone at Twitter could give us an idea of when this might be fixed? On Apr 12, 8:49 am, fdelpozo iprox...@gmail.com wrote: Sorry my english, this is an automatic Google Translate: For at least 2 weeks and stopped working the lists of Twitter. El fallo está a la hora de ver la lista de listas (valga la redundancia). The ruling is the time to see the list of lists (forgive the redundancy). Fail both the API and the Twitter interface. Twitter lists are recovered through lists 20 pages each, at the end of each page, Twitter returns a cursor that will be used to request the next and so on until you run out (cursor = 0).Twitter Now only return the 1st page, nothing more, but it does randomly, sometimes returns a page more. If you are over 20 lists you can check yourself on Twitter.com, shows you there is no page 20 for more. We have reported to support the API for days but has not yet been solved. If anyone knows anything about this and want to share is appreciated. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What's happening with Tweetie for Mac
I seem to remember some debate over how uberTwitter comes out with such a large share in that analysis, but either way everything I have seen has pointed to 40% of tweets posted coming from Twitter.com. In my mind it would be smart for people to think about how to get market share from that piece of the pie. I'm not sure I see a significant distinction between Twitter-only clients and clients that aggregate other services in terms of whether or not they are in competition with each other. On Apr 12, 6:37 pm, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/12/2010 01:58 PM, Orian Marx (@orian) wrote: I've spent eight months on a new Twitter client myself, and I had planned to start showing it at Chirp. Mine is in-browser so I suppose it's not quite the same situation, but in reality I do think they are all, for the most part, in competition with each other - no? Yes, there is a competition - two competitions, in fact: 1. Clients that interface only to Twitter, and 2. Clients that interface to Twitter and other services. If we narrow the field to Twitter-only clients, the stats are very clear:http://twitter.comhas the lion's share of the tweet count, with uberTwitter a distant second and TweetDeck third. Seehttp://tdash.org/stats/clientsfor the numbers. Tweetie is number 11 on the list - *1.39%* of all the tweets posted come from Tweetie! In short, Twitter clients are jockeying for position in a crowded field with 39.31% of the usage already subtracted out by Twitter's main web page. See Which Twitter Clients Do People Actually Use?http://meb.tw/9iRfxUfor some analysis. -- M. Edward (Ed) Boraskyhttp://borasky-research.net/m-edward-ed-borasky/@znmeb I've always regarded nature as the clothing of God. ~Alan Hovhaness -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What's happening with Tweetie for Mac
On Mon, Apr 12, 2010 at 4:44 PM, Orian Marx (@orian) or...@orianmarx.com wrote: I seem to remember some debate over how uberTwitter comes out with such a large share in that analysis, ... I've always been amazed by this, actually... check out: http://search.twitter.com/search?q=tweetphoto+source:ubertwitterresult_type=recent The rate at which people are just posting photos with UberTwitter is astounding, nevermind plain tweets. -Chad -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Chirp tracking on MadChat
Nice! But... I couldn't miss this opportunity to share my own version of Chirp tweet tracking page, focused on conversations! :p http://twitoaster.com/twitter-chirp-conference/ It threads in real time all attendees' conversations, displaying their discussions rather than disjointed tweets. Arnaud - http://twitter.com/twitoaster On Apr 12, 11:53 pm, Chad Etzel jazzyc...@gmail.com wrote: Hi all, I have setup a special Chirp tweet tracking page on MadChat (an as of yet unreleased site I've been working on) so folks who are not at the conference (or even if you are) can easily read all of the Chirp chatter. It is intentionally minimally designed to look like a chatroom and have no avatars, so you get the max text-per-screen ratio. Bonus points if you use the Terminal Skin under Settings. The url ishttp://madch.at/chirp It is tracking the #chirp hashtag as well as all @chirp mentions. There is little happening there right now, but I wanted to get the word out. It's using the Streaming API, so it feels just like a chatroom. To reply to a tweet, just click on the username on the lefthand side of the chatroom to link the reply to that tweet. Stuff you type will be tweeted out once you hit Enter, so be mindful of that. Anyway, hope this helps some people be able to monitor the backchannel of tweets and is another cool example of what you can do with the Streaming API. chirpity chirp, -Chad
Re: [twitter-dev] Re: What's happening with Tweetie for Mac
On 04/12/2010 04:44 PM, Orian Marx (@orian) wrote: I seem to remember some debate over how uberTwitter comes out with such a large share in that analysis, but either way everything I have seen has pointed to 40% of tweets posted coming from Twitter.com. In my mind it would be smart for people to think about how to get market share from that piece of the pie. I'm not sure I see a significant distinction between Twitter-only clients and clients that aggregate other services in terms of whether or not they are in competition with each other. The distinction isn't really Twitter-only vs. Twitter-plus. I probably shouldn't have segmented the market that way. If you subtract out desktop Twitter.com via a browser, the market segments are * social media CRM tools, into which class I put HootSuite, CoTweet, and Salesforce.com and SugarCRM with social media access plugins. They're distinguished by accessing multiple services, call tracking, integration with email and analytics, scheduling of tweets, campaign management, etc. * mobile Twitter clients, where uberTwitter and Twitter for iPhone reside, and I think mobile.twitter.com. People just talking to Twitter on a mobile device. After I get back from Chirp, I'll probably look over Fred Wilson's categories of Twitter applications again, because I'm not sure exactly how he's segmented the market, and I think I'll have a different take once I understand his. In any event, the social CRM tool market segment is one that so far has been fairly well served IMHO by third parties, and mostly because they've recognized that they need to work with all the platforms - render unto Twitter that which is Twitter's, render unto Facebook and LinkedIn, etc. -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What's happening with Tweetie for Mac
- Chad Etzel jazzyc...@gmail.com wrote: On Mon, Apr 12, 2010 at 4:44 PM, Orian Marx (@orian) or...@orianmarx.com wrote: I seem to remember some debate over how uberTwitter comes out with such a large share in that analysis, ... I've always been amazed by this, actually... check out: http://search.twitter.com/search?q=tweetphoto+source:ubertwitterresult_type=recent The rate at which people are just posting photos with UberTwitter is astounding, nevermind plain tweets. -Chad -- To unsubscribe, reply using remove me as the subject. Yeah, @sheamus thought uberTwitter wasn't that popular either. But I know a fair number of power tweeters that have had a Blackberry for a long time, so maybe there just aren't any other good BB clients. So - I missed the whole Blackberry story in all the iPhone brouhaha - is the new Twitter Blackberry client something Twitter bought, or are they building it?
Re: [twitter-dev] What's happening with Tweetie for Mac
On Mon, Apr 12, 2010 at 11:54 AM, Isaiah Carew isa...@me.com wrote: 1. You're decimating the client market on every platform but Windows. The iPhone and Mac versions of Tweetie have been a) dominant and b) free (ad-supported). If your app was set to compete with Tweetie 2 on the Mac and iPhone before this, it still is. If it wasn't, it still isn't. Also, you've had a LOT of time to compete against Tweetie on the Mac. If you missed the window, well, sorry. 2. You're killing any potential for innovation or investment. Oh, baloney. Ask BareBones how BBEdit has done competing against the free version of TextEdit. In 2010, you are going to compete with free. That sucks, but it's the reality of the situation. You'd better have a plan in place for it. I'm still giving EchoFon for Mac and iPhone a serious look. Why? Because it has features Tweetie doesn't. I'd start with looking at what Tweetie doesn't offer. What does it make too difficult? really wish i knew why so many twitter clients are against keyboard navigation and proper highlighting http://twitter.com/bynkii/status/12026843737 (21 hours ago… Via Tweetie) Tweetie breaks several Mac UI principles (click to select a word comes to mind). A good UI for filtering tweets based on strings (SXSW comes to mind). Sync between Mac and iPhone. Push notifications for mentions. Push notifications for mentions only for people who follow you. Push notifications for mentions only for people you follow. Push notifications of new posts by only a select group of people (like SMS notifications, but without SMS). I'm still waiting for someone to build a big enough database to get relationship data in-app (x person is also followed by these people you follow, as one example). There are a half-dozen ideas off the top of my head. 3. You have no clear (public) plan for any innovation yourself. Have you published your plan for innovation somewhere? I'm under the impression that *most* companies keep their future plans a fairly well guarded secret. (Well, except for Microsoft, who tell you what they are going to do and then do 1/100th of it 4 years later.) TjL -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: How to find the frequency of messages exchanged between 2 users
Thanks for the answer allI am just a beginner in twitter APII am not afraid to do the grind work if I have to :) On Apr 13, 1:04 am, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/12/2010 12:20 PM, Abraham Williams wrote: You will have to pull the direct messages and mentions from both users and correlate the data yourself. Abraham Moreover, accessing the direct messages of *two* users involves authenticating as *both* of them. It is highly unlikely you will be permitted to do so by people who don't have a legal contract with you. And that agreement should *clearly* specify * what is permitted and forbidden, and * *penalties* for breaking that agreement. That's the world we now live in - get used to it. This whole click this here button and get nifty stuff for free attitude is starting to unravel. -- M. Edward (Ed) Boraskyhttp://borasky-research.net/m-edward-ed-borasky/@znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] What's happening with Tweetie for Mac
hey look, i'm not looking for a flame war here. what twitter did just seemed a bit less than nice to me, that's all. this is the forum for developer feedback, if i'm not mistaken. i was feeding back. you've got a lot of valid points, and maybe a few stretched analogies, too. if you'd like my thoughts on this i posted a nicer, more thought out article: http://yourhead.tumblr.com/post/516626319/le-roi-est-mort-vive-le-roi i'd be happy to continue to debate via email or at chirp (yes, i'm going, i'm a glutton for punishment, shoot me). see you guys tomorrow, isaiah http://twitter.com/isaiah On Apr 12, 2010, at 6:08 PM, TjL wrote: On Mon, Apr 12, 2010 at 11:54 AM, Isaiah Carew isa...@me.com wrote: 1. You're decimating the client market on every platform but Windows. The iPhone and Mac versions of Tweetie have been a) dominant and b) free (ad-supported). If your app was set to compete with Tweetie 2 on the Mac and iPhone before this, it still is. If it wasn't, it still isn't. Also, you've had a LOT of time to compete against Tweetie on the Mac. If you missed the window, well, sorry. 2. You're killing any potential for innovation or investment. Oh, baloney. Ask BareBones how BBEdit has done competing against the free version of TextEdit. In 2010, you are going to compete with free. That sucks, but it's the reality of the situation. You'd better have a plan in place for it. I'm still giving EchoFon for Mac and iPhone a serious look. Why? Because it has features Tweetie doesn't. I'd start with looking at what Tweetie doesn't offer. What does it make too difficult? really wish i knew why so many twitter clients are against keyboard navigation and proper highlighting http://twitter.com/bynkii/status/12026843737 (21 hours ago… Via Tweetie) Tweetie breaks several Mac UI principles (click to select a word comes to mind). A good UI for filtering tweets based on strings (SXSW comes to mind). Sync between Mac and iPhone. Push notifications for mentions. Push notifications for mentions only for people who follow you. Push notifications for mentions only for people you follow. Push notifications of new posts by only a select group of people (like SMS notifications, but without SMS). I'm still waiting for someone to build a big enough database to get relationship data in-app (x person is also followed by these people you follow, as one example). There are a half-dozen ideas off the top of my head. 3. You have no clear (public) plan for any innovation yourself. Have you published your plan for innovation somewhere? I'm under the impression that *most* companies keep their future plans a fairly well guarded secret. (Well, except for Microsoft, who tell you what they are going to do and then do 1/100th of it 4 years later.) TjL -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: How to find the frequency of messages exchanged between 2 users
On 04/12/2010 09:11 PM, Dushyant wrote: Thanks for the answer allI am just a beginner in twitter APII am not afraid to do the grind work if I have to :) It's not just grind work you have to do - you have to have legal counsel on retainer and a business plan. Messing with other peoples' DM streams isn't something you just bang out in code. On Apr 13, 1:04 am, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/12/2010 12:20 PM, Abraham Williams wrote: You will have to pull the direct messages and mentions from both users and correlate the data yourself. Abraham Moreover, accessing the direct messages of *two* users involves authenticating as *both* of them. It is highly unlikely you will be permitted to do so by people who don't have a legal contract with you. And that agreement should *clearly* specify * what is permitted and forbidden, and * *penalties* for breaking that agreement. That's the world we now live in - get used to it. This whole click this here button and get nifty stuff for free attitude is starting to unravel. -- M. Edward (Ed) Boraskyhttp://borasky-research.net/m-edward-ed-borasky/@znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- 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] What's happening with Tweetie for Mac
On Mon, Apr 12, 2010 at 6:08 PM, TjL luo...@gmail.com wrote: Push notifications for mentions. Push notifications for mentions only for people who follow you. Push notifications for mentions only for people you follow. Push notifications of new posts by only a select group of people (like SMS notifications, but without SMS). See http://push.ly/ for points 1 and 4. The cool thing is that anyone can use the http://notifo.com/ API to accomplish the notification piece and build similar services. -Chad -- To unsubscribe, reply using remove me as the subject.
