Re: [twitter-dev] Storing information from the API
Have you read the EULA(s) ? In legal matters it's usually best to do your own footwork on the fine print first and foremost, rather than trusting a list of Internet strangers. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Apr 8, 2010 at 8:56 PM, P L homerthesimp...@gmail.com wrote: Hi, I'm trying to a pull in a user's profile picture and use it as their profile picture on my site. Am I allowed to store the URL in my database (until the user deletes the account/removes the image)? Or are there terms in the Twitter API which suggests that I'm not allowed to store information obtained from the API? Thanks -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
On Thu, Apr 08, 2010 at 05:03:29PM -0700, Naveen wrote: However, I wanted to be clear and feel it should be made obvious that with this change, there is a possibility that a tweet may not be delivered to client if the implementation of how since_id is currently used is not updated to cover the case. I still envision the situation as more likely than you seem to believe and figure as tweet velocity increases, the likelihood will also increase; But I am assuming have better data to support your viewpoint than I and shall defer. Maybe I'm just missing something here, but it seems trivial to fix on Twitter's side (enough so that I assume it's what they've been planning from the start to do): Only return tweets from closed buckets. We are guaranteed that the buckets will be properly ordered. The order will only be randomized within a bucket. Therefore, by only returning tweets from buckets which are no longer receiving new tweets, since_id works and will never miss a tweet. And, yes, this does mean a slight delay in getting the tweets out because they have to wait a few milliseconds for their bucket to close before being exposed to calls which can use since_id, plus maybe a little longer for the contents of that bucket to be distributed to multiple servers. That's still going to only take time comparable to round-trip times for an HTTP request to fetch the data for display to a user and be far, far less than the average refresh delay required by those clients which fall under the API rate limit. I submit, therefore, that any such delay caused by waiting for buckets to close will be inconsequential. -- Dave Sherohman
[twitter-dev] Re: Attending Chirp? Let's get to know each other better, Before the Conference!
Hi Jonathan, Great thing you're organizing there! I still don't know how long I'll be able to stay in SF after Chirp (waiting an answer for one of my client's project) but we will meet each other for sure starting from the 13th! Arnaud - http://twitter.com/twitoaster Twitoaster - http://twitoaster.com On 8 avr, 21:08, Jonathan Markwell j.l.markw...@inuda.com wrote: Hi Arnaud All I'm also making the trip across the Atlantic with a group of Brits under the heading of the Developer Mission:http://developermission.com Please get in touch with me off list if any of you are also travelling a long way to get to San Francisco. We have a bunch of activities planned including meetups, campus tours and meals between 12th and 19th and we have room for a few more to join us. We just released the first wave of ticket's to Europe's Unofficial Twitter Developer Unconference in London on the 8th and 9th of May. They were all allocated in under an hour but we'll be releasing more soon. Details athttp://warblecamp.eventbrite.com Also coming up on the evening 20th of April is the 8th Twitter Developer Nest in London. More details and free tickets available athttp://twitterdevelopernest.com I'm particularly looking forward to the hackday part of Chirp and the opportunity to hear about what other people in the ecosystem are working on. I'm looking at building a one page app that we can use to get a quick daily snap shot of all the things going on in the Twitter developer ecosystem from this Google Group, to GitHub, StackOverflow and Twitter. If I get the chance I'll also be adding some refinements to a soon to be launched app I'm woking on -http://smidgn.com See you next week! Jonhttp://twitter.com/jot On Thu, Apr 8, 2010 at 7:13 PM, Arnaud Meunier arnaud.meun...@twitoaster.com wrote: Dear Developers, I'm sure we’re a lot - in this group - to have our ticket for Chirp, and I wanted to launch a thread so we could know each other a little better, before the conference starts. The conference looks very promising on a technical side: we’re going to learn from the expert, practice during the hack day... Now, I don't know for you, but as great as it looks like, another reason that pushed me to do this 6,000 miles trip (coming from Paris), is actually to meet YOU guys! So I would love to learn more about my fellow Chirp attendees the official website is mentioning! Where are you coming from? Which projects are you working on? What are you interested in (concerning the conference and/or in general)? We’re going to be a lot there (something like 800 people if I remember well), but for a short time and in a very busy schedule. That’s why I thought it would be interesting to start the conversation, presentation and “who’s who” game before. On my side, I’m a 26 years old French Engineer and I created my own company to focus on IT consulting and (mainly on) Twitoaster (http:// twitoaster.com). It will be my first time in San Francisco, and I’d love to meet other developers to chat around Twitter projects, talk about our experiences, exchange ideas... I’ll arrive the 13th (will do my best to be at pre-chirp conf) and I’ll stay at the Orchard Hotel. Concerning the conference, I’m particularly curious about the Monetization part; and the Media Ecosystem development (but this part recently disappeared from the schedule). I’m also wondering how I’ll manage to stay awake for 48h+ :) Arnaud Meunier -http://twitter.com/twitoaster Twitoaster -http://twitoaster.com PS: For those who would have missed them, here are a couple of links about the conference: - Pre Chirp Conference:http://bit.ly/akOk0R - Hack day collaboration:http://bit.ly/cD3KAJ - Attendees list:http://bit.ly/9IeEmohttp://bit.ly/byKOjS - Attendees conversations:http://bit.ly/98nvAr - Questions for the speakers:http://bit.ly/aakPUN -- To unsubscribe, reply using remove me as the subject. -- Jonathan Markwell Engineer | Founder | Connector Inuda Innovations Ltd, Brighton, UK Web application development support Twitter Facebook integration specialistshttp://inuda.com Organising the world's first events for the Twitter developer Communityhttp://TwitterDeveloperNest.com Providing a nice little place to work in the middle of Brighton -http://theskiff.org Measuring your brand's visibility on the social web -http://HowSociable.com mob: 07766 021 485 | tel: 01273 704 549 | fax: 01273 376 953 skype: jlmarkwell | twitter:http://twitter.com/jot
[twitter-dev] Re: Fred Wilson article on Twitter API
With Fred being a Twitter board member, and with the enthusiasm for the article that was displayed by Twitter employees: 1) Do we all need to stop right now with developing any further gap filler type of functionality or apps? 2) Is there only a future in the ecosystem for the very minute handful of developers who happen to chance upon the idea of a killer app? 3) Can we now expect Twitter to drive most of us out of business or existence by building into Twitter the functionality that we built into our apps? -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Details on the Chirp Hack Day Showcase
I'd love to resent, but can't make it to Chirp. Maybe next year. On 9 April 2010 07:11, Doug Williams d...@twitter.com wrote: Hi all -- The Hack Day at Chirp is a remarkable opportunity for the Twitter Platform. It is the first time that the ecosystem and Twitter's extended team will meet under one roof. We are excited to collaborate at such a deep level; answering questions face-to-face while updating the Twitter team on the innovation ongoing in the ecosystem. It is cool to think that the Hack Day will represent the largest pool of ecosystem companies and projects in the same room. To celebrate, we are hosting a Showcase to demo several apps developed during the event in addition to nascent companies beginning to gain traction. Here are some of the ideas we will we will look for: * Commerce: tools for marketers, consumer analytics and consumer insights. * Engagement: platforms for social good and government, leveraging Twitter to drive engagement. * Consumption: tools that surface relevant content, vertical integrations, leveraging geotagged tweets, innovative mobile experiences, user discovery, and media curation. * Infrastructure: tools for developers, and application marketing and distribution. The Showcase will feature demos of select products and a panel to discuss the opportunities explored by these budding projects. The only rules: projects must be less than one years old, must have less than one million dollars in funding and someone must be at the Chirp Hack Day on April 15th to present. To apply to demo at the Hack Day Showcase, please apply here [1] by 3PM on April 15th, 2010. 1. http://bit.ly/chirpshowcase Thanks, Doug http://twitter.com/dougw -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: help with xAuth
On Apr 9, 7:23 am, John munz...@gmail.com wrote: Well I changed my code to use a library rather than try to do it manually and I got it to work. Coward ;-) Now for all subsequent requests am I suppose to sign requests using the oauth_token_secret that was returned? Yes. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Fred Wilson article on Twitter API
There will always be room for developers on the fringes, and novel ways of using twitter. I would hope that twitter will concentrate on the maintenance and development of the core system, and allow us to add the bells and whistles as required by our own set of users. On 9 April 2010 13:56, Dewald Pretorius dpr...@gmail.com wrote: With Fred being a Twitter board member, and with the enthusiasm for the article that was displayed by Twitter employees: 1) Do we all need to stop right now with developing any further gap filler type of functionality or apps? 2) Is there only a future in the ecosystem for the very minute handful of developers who happen to chance upon the idea of a killer app? 3) Can we now expect Twitter to drive most of us out of business or existence by building into Twitter the functionality that we built into our apps? -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Nearest Tweets using Geo
Hi I am trying to retrieve nearest tweets on iPhone. To retrieve results I requested on http://search.twitter.com/search.json? geocode=38.9951%2C-76.9276%2C5mirpp=2 The problem is everything works correct, But I want each result should return latitude, longitude so further use but every results in JSON, property geo returns null. So to retrieve latitude, longitude, what should I do. Thanks Jignesh Brahmkhatri -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Nearest Tweets using Geo
search uses a variety of different signals to determine whether a tweet should be placed near a specific latitude and longitude -- a geotag is just one of them. so, when querying the search API, you may receive more than just geotagged tweets. your best best is to just discard those which are not explicitly geocoded. in addition, i'm not sure whether the search representation includes place objects (neighborhoods, and cities). On Fri, Apr 9, 2010 at 8:00 AM, Jigu jignesh.brahmkha...@gmail.com wrote: Hi I am trying to retrieve nearest tweets on iPhone. To retrieve results I requested on http://search.twitter.com/search.json? geocode=38.9951%2C-76.9276%2C5mirpp=2 The problem is everything works correct, But I want each result should return latitude, longitude so further use but every results in JSON, property geo returns null. So to retrieve latitude, longitude, what should I do. Thanks Jignesh Brahmkhatri -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Fred Wilson article on Twitter API
100% On Fri, Apr 9, 2010 at 7:11 AM, Nigel Legg nigel.l...@gmail.com wrote: There will always be room for developers on the fringes, and novel ways of using twitter. I would hope that twitter will concentrate on the maintenance and development of the core system, and allow us to add the bells and whistles as required by our own set of users. On 9 April 2010 13:56, Dewald Pretorius dpr...@gmail.com wrote: With Fred being a Twitter board member, and with the enthusiasm for the article that was displayed by Twitter employees: 1) Do we all need to stop right now with developing any further gap filler type of functionality or apps? 2) Is there only a future in the ecosystem for the very minute handful of developers who happen to chance upon the idea of a killer app? 3) Can we now expect Twitter to drive most of us out of business or existence by building into Twitter the functionality that we built into our apps? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Bulk User Relationship Lookup?
That's awesome. I'm putting it to use this weekend. (fully understanding the caveat that it might change) On Apr 9, 12:17 pm, Raffi Krikorian ra...@twitter.com wrote: at the risk of introducing features instead of fixing bugs, this endpoint may also be of use -- its a work in progress, and a few details of it may change: http://api.twitter.com/1/friendships/lookup.xml?user_id=813286,783214 On Wed, Mar 31, 2010 at 8:02 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I would certainly be interested in such a list, but no I don't think Twitter will be providing one. On Mar 30, 9:26 pm, mcfnord mcfn...@gmail.com wrote: Hi, Abraham, and everyone. I'm crawling twitter. (But who isn't, right?) Us social graph geeks have our own advantages, and our own set of challenges. For example, I would not want to manage the vastness of tweet volumes. But I do get neck-deep in social graph data. Which means I crawl with this:http://twitter.com/friends/ids.xml/?user_id=12345 x20,000/hr. so far i've discovered existance of 51 million accounts, and examined 13 million of these. if i need two scrapes to determine account activity, then i've got just 89 million captures to go! that's 6 months at full speed. inactive accounts can live with a vastly slower refresh cycle. so really what would benefit me (and twitter, as i see it) is a cheat sheet of active vs. inactive accounts. download the file, and know the integers within it are active accounts. in one move, through occasional publication of one file, twitter saves 6 months of scrapes for anyone who can leverage a quick-start list of which accounts are active, and which are inactive. i imagine people could, in many scenarios, limit their entire set of inquiries to these active accounts, saving millions of calls to twitter's api. maybe it's bad p.r. to state explicitly which accounts merit resources and which are dead. i guess once it's over i won't look back and perhaps it is i who can publish this dataset to some other newbie. but what a great efficiency for twitter to avoid this for everyone in my shoes. which are small shoes, i accept. best regards, john On Mar 23, 11:56 am, Abraham Williams 4bra...@gmail.com wrote: Bulk lookup of social graphs seems like it would be a pretty resource intensive call. I would not hold my breath for Twitter to implement it. Abraham On Tue, Mar 23, 2010 at 08:21,OrianMarx (@orian) or...@orianmarx.com wrote: Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/READMEAbraham On Mon, Mar 22, 2010 at 19:41,OrianMarx (@orian) or...@orianmarx.com wrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.- Hide quoted text - - Show quoted text - -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: Bulk User Relationship Lookup?
the items which may change include the way you specify users (right now, i think, it only supports user_ids), and perhaps a small change on the XML representation. i think the JSON one will stay stable (ish). On Fri, Apr 9, 2010 at 10:00 AM, Orian Marx (@orian) or...@orianmarx.comwrote: That's awesome. I'm putting it to use this weekend. (fully understanding the caveat that it might change) On Apr 9, 12:17 pm, Raffi Krikorian ra...@twitter.com wrote: at the risk of introducing features instead of fixing bugs, this endpoint may also be of use -- its a work in progress, and a few details of it may change: http://api.twitter.com/1/friendships/lookup.xml?user_id=813286,783214 On Wed, Mar 31, 2010 at 8:02 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I would certainly be interested in such a list, but no I don't think Twitter will be providing one. On Mar 30, 9:26 pm, mcfnord mcfn...@gmail.com wrote: Hi, Abraham, and everyone. I'm crawling twitter. (But who isn't, right?) Us social graph geeks have our own advantages, and our own set of challenges. For example, I would not want to manage the vastness of tweet volumes. But I do get neck-deep in social graph data. Which means I crawl with this:http://twitter.com/friends/ids.xml/?user_id=12345 x20,000/hr. so far i've discovered existance of 51 million accounts, and examined 13 million of these. if i need two scrapes to determine account activity, then i've got just 89 million captures to go! that's 6 months at full speed. inactive accounts can live with a vastly slower refresh cycle. so really what would benefit me (and twitter, as i see it) is a cheat sheet of active vs. inactive accounts. download the file, and know the integers within it are active accounts. in one move, through occasional publication of one file, twitter saves 6 months of scrapes for anyone who can leverage a quick-start list of which accounts are active, and which are inactive. i imagine people could, in many scenarios, limit their entire set of inquiries to these active accounts, saving millions of calls to twitter's api. maybe it's bad p.r. to state explicitly which accounts merit resources and which are dead. i guess once it's over i won't look back and perhaps it is i who can publish this dataset to some other newbie. but what a great efficiency for twitter to avoid this for everyone in my shoes. which are small shoes, i accept. best regards, john On Mar 23, 11:56 am, Abraham Williams 4bra...@gmail.com wrote: Bulk lookup of social graphs seems like it would be a pretty resource intensive call. I would not hold my breath for Twitter to implement it. Abraham On Tue, Mar 23, 2010 at 08:21,OrianMarx (@orian) or...@orianmarx.com wrote: Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/README Abraham On Mon, Mar 22, 2010 at 19:41,OrianMarx (@orian) or...@orianmarx.com wrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth
[twitter-dev] Re: Fred Wilson article on Twitter API
Thanks Raffi, though I doubt your comment will make headlines :) -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Fred Wilson article on Twitter API
story of my life. On Fri, Apr 9, 2010 at 10:29 AM, mikawhite mikawh...@me.com wrote: Thanks Raffi, though I doubt your comment will make headlines :) -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Storing information from the API
I heard from my cousin that it was cool... On Fri, Apr 9, 2010 at 01:43, Andrew Badera and...@badera.us wrote: Have you read the EULA(s) ? In legal matters it's usually best to do your own footwork on the fine print first and foremost, rather than trusting a list of Internet strangers. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Apr 8, 2010 at 8:56 PM, P L homerthesimp...@gmail.com wrote: Hi, I'm trying to a pull in a user's profile picture and use it as their profile picture on my site. Am I allowed to store the URL in my database (until the user deletes the account/removes the image)? Or are there terms in the Twitter API which suggests that I'm not allowed to store information obtained from the API? Thanks -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
RE: [twitter-dev] Storing information from the API
Come on Andy, he’s asking the Twitter Dev list , a highly appropriate place to ask if he couldn’t find the answer elsewhere. Hardly random strangers, this question must have come up before. Regards, Dean Collins Live Chat Concepts Inc d...@livechatconcepts.com mailto:d...@livechatconcepts.com +1-212-203-4357 New York +61-2-9016-5642 (Sydney in-dial). +44-20-3129-6001 (London in-dial). On Fri, Apr 9, 2010 at 01:43, Andrew Badera and...@badera.us wrote: Have you read the EULA(s) ? In legal matters it's usually best to do your own footwork on the fine print first and foremost, rather than trusting a list of Internet strangers. ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Thu, Apr 8, 2010 at 8:56 PM, P L homerthesimp...@gmail.com wrote: Hi, I'm trying to a pull in a user's profile picture and use it as their profile picture on my site. Am I allowed to store the URL in my database (until the user deletes the account/removes the image)? Or are there terms in the Twitter API which suggests that I'm not allowed to store information obtained from the API? Thanks -- To unsubscribe, reply using remove me as the subject. -- Abraham Williams | Community Advocate | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private.
RE: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
John, Thank you. That was one of the most informative emails on the Twitter API I have seen on the list. Basically, even now, an application should not use an ID of a tweet for since_id if the tweet is less than 10 seconds old, ignoring service abnormalities. Probably a larger threshold (30 seconds or even a minute) would be better, especially when you take into consideration the likelihood of clock skew between the servers that generate the timestamps. I think this is information that would be useful to have added to the API documentation, as I know many applications are taking a much more naive approach to pagination. Thanks again, Brian From: twitter-development-talk@googlegroups.com On Behalf Of John Kalucki Sent: Friday, April 09, 2010 1:20 PM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced Folks are making a lot of incorrect assumptions about the Twitter architecture, especially around how we materialize and present timeline vectors and just what QoS we're really offering. This new scheme does not significantly, or perhaps even observably, make the existing issues around since_id any better or any worse. And I'm being very precise here. The since_id situation is such that the few milliseconds skew possible in Snowflake are practically irrelevant and lost in the noise of a 4 to 6 orders-of-magnitude misconception. (That's a very big misconception.) If you do not know the rough ordering of our event stream as it applied to the materialized timeline vectors and also the expected rate of change on the timeline in question, you cannot make good choices about making since_id perfect. But, neither you should you try to make it perfect, nor should you have to worry about this. If you insist upon worrying about this, here's my slight salting of Mark's advice: In the existing continuously increasing id generation scheme on the Twitter.com API, I'd subtract about 5000 ids from since_id to ensure sufficient overlap in nearly all cases, but even this could be lossy in the face of severe operational issues -- issues of a type that we haven't seen in many many months. The search API has a different K in its rough ordering, so you might need more like 10,000 ids. In the new Snowflake scheme, I'd overlap by about 5000 milliseconds for twitter.com APIs and 10,000 ms for search APIs. Despite all this, things still could go wrong. An engineer here is known for pointing out that even things that almost never ever happen, happen all the time on the Twitter system. Now, just because they are happening, to someone, all the time, doesn't mean that they'll ever ever happen to you or your users in a thousand years -- but some's getting hit with it, somewhere, a few times a day. The above schemes no longer treat the id as an opaque unique ordered identifier. And woe lies in wait for you as changes are made to these ids. Woe. You also need to deduplicate. Be very careful and understand fully what you summon by breaking this semantic contract. In the end, since_id issues go away on the Streaming API, and other than around various start-up discontinuities, you can ignore this issue. I'll be talking about Rough Ordering, among other things Streaming, at the Chirp conference. Come geek out. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 9, 2010 at 1:58 AM, Dave Sherohman d...@fishtwits.com wrote: On Thu, Apr 08, 2010 at 05:03:29PM -0700, Naveen wrote: However, I wanted to be clear and feel it should be made obvious that with this change, there is a possibility that a tweet may not be delivered to client if the implementation of how since_id is currently used is not updated to cover the case. I still envision the situation as more likely than you seem to believe and figure as tweet velocity increases, the likelihood will also increase; But I am assuming have better data to support your viewpoint than I and shall defer. Maybe I'm just missing something here, but it seems trivial to fix on Twitter's side (enough so that I assume it's what they've been planning from the start to do): Only return tweets from closed buckets. We are guaranteed that the buckets will be properly ordered. The order will only be randomized within a bucket. Therefore, by only returning tweets from buckets which are no longer receiving new tweets, since_id works and will never miss a tweet. And, yes, this does mean a slight delay in getting the tweets out because they have to wait a few milliseconds for their bucket to close before being exposed to calls which can use since_id, plus maybe a little longer for the contents of that bucket to be distributed to multiple servers. That's still going to only take time comparable to round-trip times for an HTTP request to fetch the data for display to a user and be far, far less than the average refresh delay required by those clients which fall under
Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
Your second paragraph doesn't quite make sense. The period between your next poll and the timestamp of the last status is irrelevant. The issue is solely the magnitude of K on the roughly sorted stream of events that are applied to the materialized timeline vector. As K varies, so do the odds, however infinitesimally small, that you will miss a tweet using the last status id returned. The period between your polls of the API does not affect this K. My recommendation is to ignore this issue in nearly every use case. If you are, however, polling high velocity timelines (including search queries) and attempting to approximate an Exactly Once QoS, you should, basically, stop doing that. You are probably wasting resources and you'll probably never get Exactly Once behavior anyway. Use the Streaming API instead. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 9, 2010 at 12:20 PM, Brian Smith br...@briansmith.org wrote: John, Thank you. That was one of the most informative emails on the Twitter API I have seen on the list. Basically, even now, an application should not use an ID of a tweet for since_id if the tweet is less than 10 seconds old, ignoring service abnormalities. Probably a larger threshold (30 seconds or even a minute) would be better, especially when you take into consideration the likelihood of clock skew between the servers that generate the timestamps. I think this is information that would be useful to have added to the API documentation, as I know many applications are taking a much more naive approach to pagination. Thanks again, Brian *From:* twitter-development-talk@googlegroups.com *On Behalf Of *John Kalucki *Sent:* Friday, April 09, 2010 1:20 PM *To:* twitter-development-talk@googlegroups.com *Subject:* Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced Folks are making a lot of incorrect assumptions about the Twitter architecture, especially around how we materialize and present timeline vectors and just what QoS we're really offering. This new scheme does not significantly, or perhaps even observably, make the existing issues around since_id any better or any worse. And I'm being very precise here. The since_id situation is such that the few milliseconds skew possible in Snowflake are practically irrelevant and lost in the noise of a 4 to 6 orders-of-magnitude misconception. (That's a very big misconception.) If you do not know the rough ordering of our event stream as it applied to the materialized timeline vectors and also the expected rate of change on the timeline in question, you cannot make good choices about making since_id perfect. But, neither you should you try to make it perfect, nor should you have to worry about this. If you insist upon worrying about this, here's my slight salting of Mark's advice: In the existing continuously increasing id generation scheme on the Twitter.com API, I'd subtract about 5000 ids from since_id to ensure sufficient overlap in nearly all cases, but even this could be lossy in the face of severe operational issues -- issues of a type that we haven't seen in many many months. The search API has a different K in its rough ordering, so you might need more like 10,000 ids. In the new Snowflake scheme, I'd overlap by about 5000 milliseconds for twitter.com APIs and 10,000 ms for search APIs. Despite all this, things still could go wrong. An engineer here is known for pointing out that even things that almost never ever happen, happen all the time on the Twitter system. Now, just because they are happening, to someone, all the time, doesn't mean that they'll ever ever happen to you or your users in a thousand years -- but some's getting hit with it, somewhere, a few times a day. The above schemes no longer treat the id as an opaque unique ordered identifier. And woe lies in wait for you as changes are made to these ids. Woe. You also need to deduplicate. Be very careful and understand fully what you summon by breaking this semantic contract. In the end, since_id issues go away on the Streaming API, and other than around various start-up discontinuities, you can ignore this issue. I'll be talking about Rough Ordering, among other things Streaming, at the Chirp conference. Come geek out. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 9, 2010 at 1:58 AM, Dave Sherohman d...@fishtwits.com wrote: On Thu, Apr 08, 2010 at 05:03:29PM -0700, Naveen wrote: However, I wanted to be clear and feel it should be made obvious that with this change, there is a possibility that a tweet may not be delivered to client if the implementation of how since_id is currently used is not updated to cover the case. I still envision the situation as more likely than you seem to believe and figure as tweet velocity increases, the likelihood will also increase; But I am assuming have
[twitter-dev] Re: Fred Wilson article on Twitter API
Raffi, It will be wise of Twitter to release an official statement regarding continued developer support. Perhaps in the form of an Evan blog post. When you read the commentary on tech blogs following Fred's post, it should be clear that it is not only developers who see the threat of Twitter now screwing them by taking ideas they came up with and implemented, and building those ideas into the Twitter core. On Apr 9, 12:33 pm, Raffi Krikorian ra...@twitter.com wrote: 100% On Fri, Apr 9, 2010 at 7:11 AM, Nigel Legg nigel.l...@gmail.com wrote: There will always be room for developers on the fringes, and novel ways of using twitter. I would hope that twitter will concentrate on the maintenance and development of the core system, and allow us to add the bells and whistles as required by our own set of users. On 9 April 2010 13:56, Dewald Pretorius dpr...@gmail.com wrote: With Fred being a Twitter board member, and with the enthusiasm for the article that was displayed by Twitter employees: 1) Do we all need to stop right now with developing any further gap filler type of functionality or apps? 2) Is there only a future in the ecosystem for the very minute handful of developers who happen to chance upon the idea of a killer app? 3) Can we now expect Twitter to drive most of us out of business or existence by building into Twitter the functionality that we built into our apps? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi- Hide quoted text - - Show quoted text -
RE: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
John, I am not polling. I am simply trying to implement a basic refresh feature like every desktop/mobile Twitter app has. Basically, I just want to let users scroll through their timelines, and be reasonably sure that I am presenting them with an accurate complete view of the timeline, while using as little bandwidth as possible. When I said 10 seconds old/30 seconds old/etc. I was referring to I was referring to the age at the time the page of tweets was generated. So, basically, if the tweet's timestamp - the response's Last-Modified time more than 10,000 ms (from what you said below), you are almost definitely getting At Least Once behavior if Twitter is operating normally, and you can use that information to get At Least Once behavior that emulates Exactly Once behavior with little (usually no) overhead. Is that a correct interpretation of what you were saying? Thanks, Brian From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of John Kalucki Sent: Friday, April 09, 2010 3:31 PM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced Your second paragraph doesn't quite make sense. The period between your next poll and the timestamp of the last status is irrelevant. The issue is solely the magnitude of K on the roughly sorted stream of events that are applied to the materialized timeline vector. As K varies, so do the odds, however infinitesimally small, that you will miss a tweet using the last status id returned. The period between your polls of the API does not affect this K. My recommendation is to ignore this issue in nearly every use case. If you are, however, polling high velocity timelines (including search queries) and attempting to approximate an Exactly Once QoS, you should, basically, stop doing that. You are probably wasting resources and you'll probably never get Exactly Once behavior anyway. Use the Streaming API instead. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Apr 9, 2010 at 12:20 PM, Brian Smith br...@briansmith.org wrote: John, Thank you. That was one of the most informative emails on the Twitter API I have seen on the list. Basically, even now, an application should not use an ID of a tweet for since_id if the tweet is less than 10 seconds old, ignoring service abnormalities. Probably a larger threshold (30 seconds or even a minute) would be better, especially when you take into consideration the likelihood of clock skew between the servers that generate the timestamps. I think this is information that would be useful to have added to the API documentation, as I know many applications are taking a much more naive approach to pagination. Thanks again, Brian From: twitter-development-talk@googlegroups.com On Behalf Of John Kalucki Sent: Friday, April 09, 2010 1:20 PM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Re: Upcoming changes to the way status IDs are sequenced Folks are making a lot of incorrect assumptions about the Twitter architecture, especially around how we materialize and present timeline vectors and just what QoS we're really offering. This new scheme does not significantly, or perhaps even observably, make the existing issues around since_id any better or any worse. And I'm being very precise here. The since_id situation is such that the few milliseconds skew possible in Snowflake are practically irrelevant and lost in the noise of a 4 to 6 orders-of-magnitude misconception. (That's a very big misconception.) If you do not know the rough ordering of our event stream as it applied to the materialized timeline vectors and also the expected rate of change on the timeline in question, you cannot make good choices about making since_id perfect. But, neither you should you try to make it perfect, nor should you have to worry about this. If you insist upon worrying about this, here's my slight salting of Mark's advice: In the existing continuously increasing id generation scheme on the Twitter.com API, I'd subtract about 5000 ids from since_id to ensure sufficient overlap in nearly all cases, but even this could be lossy in the face of severe operational issues -- issues of a type that we haven't seen in many many months. The search API has a different K in its rough ordering, so you might need more like 10,000 ids. In the new Snowflake scheme, I'd overlap by about 5000 milliseconds for twitter.com APIs and 10,000 ms for search APIs. Despite all this, things still could go wrong. An engineer here is known for pointing out that even things that almost never ever happen, happen all the time on the Twitter system. Now, just because they are happening, to someone, all the time, doesn't mean that they'll ever ever happen to you or your users in a thousand years -- but some's getting hit with it, somewhere, a few times a day.
[twitter-dev] Re: Fred Wilson article on Twitter API
Libraries and examples. Understanding authentication isn't a prerequisite for building valuable apps. If a developer wants to understand OAuth then there is plenty of documentation out there for that. I think the biggest barrier is the complexity of beginning to understand the OAuth dance. If there was an interface of examples that libraries could implement then it would go a long way. Right now every library has it's own examples and it makes it difficult for users get up and running with something as basic as authentication. I'm thinking Hello world type examples that each library can provide in a consistent manner. On Apr 7, 3:30 pm, Raffi Krikorian ra...@twitter.com wrote: i would love to know how we can make oauth simpler for people. should we provide better documentation? examples? libraries? On Wed, Apr 7, 2010 at 3:07 PM, Lil Peck lilp...@gmail.com wrote: On Wed, Apr 7, 2010 at 1:53 PM, Mike Champion mike.champ...@gmail.com wrote: I'd be curious to hear what folks think. For me, the appeal of Twitter is its brevity and its simplicity for integration with one's website. I worry that once basic authentication is discontinued, that I will have to stop using Twitter in my web based apps. Seems to me that oauth is needlessly too complicated and bloated for many Twitter uses. I like it that Twitter has been a very simple service, and that because of the limit of its scope, there are opportunities for indepedent developers to create extensions for it. I am not at all enchanted by Facebook and whatever I do with Facebook is out of sheer necessity. -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Hello all, Question about multi gets
I'm calling statuses/user_timeline http://api.twitter.com/1/statuses/user_timeline.format for a few users one by one. Is there a way to call the api and get a few users with one call? Thanks -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Twitter buying Tweetie
Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Twitter buying Tweetie
There is also an official blackberry app coming. http://mobile.blog.twitter.com/2010/04/official-twitter-for-blackberry-app-now.html On Fri, Apr 9, 2010 at 18:41, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- 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] Re: Twitter buying Tweetie
It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Fred Wilson article on Twitter API
And so it's time for Twitter and its developer ecosystem to work together to create entirely new things that will shape the Internet in the coming years. I'm excited to see it happen. Because Twitter's gonna be taking over all the shit you've been doing so far! Welp, like used to say 3 years ago: you don't have a legal contract with Twitter, so don't build a business on it. Good thing no one here did that! Right? -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 9, 5:01 pm, Dewald Pretorius dpr...@gmail.com wrote: Raffi, It will be wise of Twitter to release an official statement regarding continued developer support. Perhaps in the form of an Evan blog post. When you read the commentary on tech blogs following Fred's post, it should be clear that it is not only developers who see the threat of Twitter now screwing them by taking ideas they came up with and implemented, and building those ideas into the Twitter core. On Apr 9, 12:33 pm, Raffi Krikorian ra...@twitter.com wrote: 100% On Fri, Apr 9, 2010 at 7:11 AM, Nigel Legg nigel.l...@gmail.com wrote: There will always be room for developers on the fringes, and novel ways of using twitter. I would hope that twitter will concentrate on the maintenance and development of the core system, and allow us to add the bells and whistles as required by our own set of users. On 9 April 2010 13:56, Dewald Pretorius dpr...@gmail.com wrote: With Fred being a Twitter board member, and with the enthusiasm for the article that was displayed by Twitter employees: 1) Do we all need to stop right now with developing any further gap filler type of functionality or apps? 2) Is there only a future in the ecosystem for the very minute handful of developers who happen to chance upon the idea of a killer app? 3) Can we now expect Twitter to drive most of us out of business or existence by building into Twitter the functionality that we built into our apps? -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi-Hide quoted text - - Show quoted text -
[twitter-dev] Re: Twitter buying Tweetie
I am also happy for Loren, he deserves it based purely on the quality of his product. I would like some clarification on the intended future of Tweetie for OS X. The plans for the iPhone and iPad have been made very very clear: stay away. Please clarify the plans for OS X. But at this point I don't really expect a response, but I need to ask. --ejw Eric Woodward Email: e...@nambu.com -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
Dewald, I'm surprised that you failed to mention that Twitter can also advertise the heck out of it on Twitter.com and via tweets etc - millions for further development - and very significant marketing resources available too. I disagree with your sentiment though. Twitter's free to build or buy whatever they want to. As a third party developer it's one of the risks you take on when you start building on someone else's platform. If you don't acknowledge that, you're being naive. Sure it's going to suck if they do something to harm Favstar, but I'm aware it's a risk - and I'm going to try and keep innovating to keep Favstar useful for users regardless. Tim. On Sat, Apr 10, 2010 at 2:18 PM, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter buying Tweetie
Twitter did this to BB clients too, today. You think this is the last platform they'll do an Official Client on? Take a look at the OS X music playback app market to see the future of Twitter clients. Here's the shirt for the Chirp keynote: http://spaz.spreadshirt.com/ Have fun in SF next week, everybody! -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 9, 10:18 pm, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim.
Re: [twitter-dev] Re: Twitter buying Tweetie
Congrats, As a twitter user I'm intrigued. As a twitter developer I'm not hoping that you are really close to a statement to reassure us all its ok and maintaining an even playing field. Although renaming it Tweetie to Twitter for iPhone is a hurtful (being THE twitter client relegates the others to second instantly in what was an even playing field). So as a Tweetie user, please add sign up API so my mom and dad can get on Twitter from directly on the iPhone. Please add iPad support. Please also make a purchase of Windows based company to even out Tweetie for Mac venture so Twitter doesn't seem Mac happy, and please buy a Android company to even that side out too. See you all at Chrip! I'm sure this will be a lively debate so: INB4 insanity Zac Bowling On Fri, Apr 9, 2010 at 7:18 PM, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
Loren, congrats man. I think the best man won. Hard work and dedication to perfection paid off in spades. You deserve the accolades (and the $$$). Oh and everyone else? Thanks for playing. I'll catch you all next week on the Facebook forums. Anyone have the odds on who Twitter will pick as the winners on the other platforms? Isaiah On Apr 9, 2010, at 7:25 PM, Tim Haines tmhai...@gmail.com wrote: Dewald, I'm surprised that you failed to mention that Twitter can also advertise the heck out of it on Twitter.com and via tweets etc - millions for further development - and very significant marketing resources available too. I disagree with your sentiment though. Twitter's free to build or buy whatever they want to. As a third party developer it's one of the risks you take on when you start building on someone else's platform. If you don't acknowledge that, you're being naive. Sure it's going to suck if they do something to harm Favstar, but I'm aware it's a risk - and I'm going to try and keep innovating to keep Favstar useful for users regardless. Tim. On Sat, Apr 10, 2010 at 2:18 PM, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
I am also happy for Loren, he deserves it based purely on the quality of his product. I would like some clarification on the intended future of Tweetie for OS X. The plans for the iPhone and iPad have been made very very clear: stay away. Please clarify the plans for OS X. Let's just say that I think Nambu is now worth more as the next Sea World whale's name than an OS X Twitter client. Fortunately, I inhabit the command line and Mac OS 9 markets, so I'm pretty sure I'm safe. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- I use my C128 because I am an ornery, stubborn, retro grouch. -- Bob Masse - -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
On 04/09/2010 07:44 PM, Cameron Kaiser wrote: I am also happy for Loren, he deserves it based purely on the quality of his product. I would like some clarification on the intended future of Tweetie for OS X. The plans for the iPhone and iPad have been made very very clear: stay away. Please clarify the plans for OS X. Let's just say that I think Nambu is now worth more as the next Sea World whale's name than an OS X Twitter client. Fortunately, I inhabit the command line and Mac OS 9 markets, so I'm pretty sure I'm safe. Uh ... market implies that people will actually *pay* for something. I haven't found that to be the case for command line tools. ;-) Don't know about OS 9, though - last time I was asked to use one of those (summer 2004), I politely declined and did everything on my dual-booted Windows XP / Linux laptop. ;-) But that does raise an interesting question - I'm not overly impressed with any of the open-source GUI Twitter clients, and I won't run an AIR application on my Linux desktop - AIR is a resource hog (and closed). So I stick with web-based clients like the Twitter home page, HootSuite or CoTweet. Is there any energy out there for a *really good* open source Twitter GUI client that would run on Linux, Mac and Windows? And the congratulations belong to *both* Loren and Twitter! ;-) -- M. Edward (Ed) Borasky borasky-research.net/ @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
Uh ... market implies that people will actually *pay* for something. I haven't found that to be the case for command line tools. ;-) Don't know about OS 9, though - last time I was asked to use one of those (summer 2004), I politely declined and did everything on my dual-booted Windows XP / Linux laptop. ;-) Thanks so much for clarifying. :-P -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- TODAY'S DUMB TRUE HEADLINE: Plane Too Close to Ground, Crash Probe Told -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Hello all, Question about multi gets
Add the users to a list. http://apiwiki.twitter.com/Twitter-REST-API-Method:-GET-list-statuses Abraham On Fri, Apr 9, 2010 at 17:47, adamjamesdrew theikl...@gmail.com wrote: I'm calling statuses/user_timeline http://api.twitter.com/1/statuses/user_timeline.format for a few users one by one. Is there a way to call the api and get a few users with one call? Thanks -- 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] Re: Twitter buying Tweetie
Congrats Loren. As for Tweetie for Mac. I would like to see it open sourced: http://act.ly/1w1 http://act.ly/1w1Abraham On Fri, Apr 9, 2010 at 20:22, funkatron funkat...@gmail.com wrote: On Apr 9, 10:58 pm, M. Edward (Ed) Borasky zn...@comcast.net wrote: But that does raise an interesting question - I'm not overly impressed with any of the open-source GUI Twitter clients, and I won't run an AIR application on my Linux desktop - AIR is a resource hog (and closed). So I stick with web-based clients like the Twitter home page, HootSuite or CoTweet. Is there any energy out there for a *really good* open source Twitter GUI client that would run on Linux, Mac and Windows? Define energy. Spaz has been out there and FOSS since mid 2007. Moving off AIR and doing lots of other good things have been in my plans for a long time, but open source in no way means people want to help you. No one will be even close to your own interest level. FWIW, I'm leaning towards deploying Spaz as a hosted FOSS web app -- that is, you could use my server, or DL and host it yourself. It would focus on providing a good experience for touch-based clients particularly. When that will happen is pretty much dictated by who else takes interest. Integrating well with StatusNet's server software seems pretty appealing right now. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.comxmpp%3afunkat...@gmail.com -- 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] What happened, happened.
Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. No one Twitter experience will ever define Twitter. No one app will ever define a platform. Not all use cases, analytical opportunities, clients, redefinitions, evolutions of, extrapolations on, libraries for the API of, insights for, integrations of, thoughts on, run-on-sentences-written-about, financial opportunities, or choices offered to consumers in the Twitter universe have been explored. @episod -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What happened, happened.
It would be awesome if some of those opportunities were offered to people who aren't able to afford to travel to SF. Of course, a lot of things would be awesome, but I'm not optimistic about them. Alas. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 9, 11:26 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. No one Twitter experience will ever define Twitter. No one app will ever define a platform. Not all use cases, analytical opportunities, clients, redefinitions, evolutions of, extrapolations on, libraries for the API of, insights for, integrations of, thoughts on, run-on-sentences-written-about, financial opportunities, or choices offered to consumers in the Twitter universe have been explored. @episod
Re: [twitter-dev] What happened, happened.
It would be great if Twitter would clarify things online. I'm sure I'm not the only one who thinks that it's time to cut losses and move on - starting with Chirp. Frankly I'm not sure I see much point in attending Chirp any more. Isaiah On Apr 9, 2010, at 8:26 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. No one Twitter experience will ever define Twitter. No one app will ever define a platform. Not all use cases, analytical opportunities, clients, redefinitions, evolutions of, extrapolations on, libraries for the API of, insights for, integrations of, thoughts on, run-on-sentences-written-about, financial opportunities, or choices offered to consumers in the Twitter universe have been explored. @episod
Re: [twitter-dev] What happened, happened.
Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. ... except on the iPhone. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Jesus loves you, and I'm trying to. -- Jack Thompson ---
[twitter-dev] Re: What happened, happened.
It looks like it will be great if you want to have VCs and pundits talk to you for several hours. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 9, 11:36 pm, Isaiah isa...@me.com wrote: It would be great if Twitter would clarify things online. I'm sure I'm not the only one who thinks that it's time to cut losses and move on - starting with Chirp. Frankly I'm not sure I see much point in attending Chirp any more. Isaiah On Apr 9, 2010, at 8:26 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. No one Twitter experience will ever define Twitter. No one app will ever define a platform. Not all use cases, analytical opportunities, clients, redefinitions, evolutions of, extrapolations on, libraries for the API of, insights for, integrations of, thoughts on, run-on-sentences-written-about, financial opportunities, or choices offered to consumers in the Twitter universe have been explored. @episod -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] What happened, happened.
Sorry, but you #LOST me... -Chad On Apr 9, 2010, at 20:26, Taylor Singletary taylorsinglet...@twitter.com wrote: Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. No one Twitter experience will ever define Twitter. No one app will ever define a platform. Not all use cases, analytical opportunities, clients, redefinitions, evolutions of, extrapolations on, libraries for the API of, insights for, integrations of, thoughts on, run-on- sentences-written-about, financial opportunities, or choices offered to consumers in the Twitter universe have been explored. @episod -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
On 04/09/2010 08:22 PM, funkatron wrote: Define energy. Spaz has been out there and FOSS since mid 2007. Moving off AIR and doing lots of other good things have been in my plans for a long time, but open source in no way means people want to help you. No one will be even close to your own interest level. Open source depends on the fact that it is in the interest of major corporations like IBM, Novell, Oracle, Google, Dell and others to support it. I quite frankly don't know why some other large corporations don't join the party - there are just so many wheels you can re-invent before your bottom line goes to Hell in a hand-basket. FWIW, I'm leaning towards deploying Spaz as a hosted FOSS web app -- that is, you could use my server, or DL and host it yourself. It would focus on providing a good experience for touch-based clients particularly. When that will happen is pretty much dictated by who else takes interest. I should look at Spaz, I guess, although I'm dead-set against ever installing AIR again. I loaded one of the AIR-based Twitter desktops - I don't remember which one - and the process was brutal. The client itself sucked too, so there was no reason to keep it or AIR. I'm not sure I'd use a web-based client other than Twitter's at this point. HootSuite and CoTweet are moving towards being marketing / CRM add-ons to all the social networks. If that was what I was doing, I'd simply use SugarCRM (another fine open-source corporate project) with Twitter and Facebook plug-ins. ;-) Integrating well with StatusNet's server software seems pretty appealing right now. Yeah, I keep meaning to look at StatusNet, although I'm not sure when I'll find the time. They've got a huge wall to climb. -- M. Edward (Ed) Borasky borasky-research.net @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter buying Tweetie
StatusNet is in an interesting position. They can't, and I don't think have to, compete directly with Twitter. Offering both SAAS and self- hosted opportunities is compelling, and they have a pretty strong dev community. They already have Twitter and Facebook two-way bridges built in, which means you can run your own thing and still interact with both of those services. I'm interested in the idea of complementing StatusNet in a similar fashion on the client side, as a true FOSS tool, extensible via a plugin architecture. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 9, 11:42 pm, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/09/2010 08:22 PM, funkatron wrote: Define energy. Spaz has been out there and FOSS since mid 2007. Moving off AIR and doing lots of other good things have been in my plans for a long time, but open source in no way means people want to help you. No one will be even close to your own interest level. Open source depends on the fact that it is in the interest of major corporations like IBM, Novell, Oracle, Google, Dell and others to support it. I quite frankly don't know why some other large corporations don't join the party - there are just so many wheels you can re-invent before your bottom line goes to Hell in a hand-basket. FWIW, I'm leaning towards deploying Spaz as a hosted FOSS web app -- that is, you could use my server, or DL and host it yourself. It would focus on providing a good experience for touch-based clients particularly. When that will happen is pretty much dictated by who else takes interest. I should look at Spaz, I guess, although I'm dead-set against ever installing AIR again. I loaded one of the AIR-based Twitter desktops - I don't remember which one - and the process was brutal. The client itself sucked too, so there was no reason to keep it or AIR. I'm not sure I'd use a web-based client other than Twitter's at this point. HootSuite and CoTweet are moving towards being marketing / CRM add-ons to all the social networks. If that was what I was doing, I'd simply use SugarCRM (another fine open-source corporate project) with Twitter and Facebook plug-ins. ;-) Integrating well with StatusNet's server software seems pretty appealing right now. Yeah, I keep meaning to look at StatusNet, although I'm not sure when I'll find the time. They've got a huge wall to climb. -- M. Edward (Ed) Borasky borasky-research.net @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Attending Chirp? Let's get to know each other better, Before the Conference!
Hope you'll all join the very large developer gathering the evening of 4/13 that emerged out of our hey let's get beer pizza before the conf starts: http://tweetvite.com/event/prechirp ALL are welcome. There will be beer, wine, pizza, photobooth, etc. See you in SF Warmly, Laura Fitton (@pistachio/@oneforty)
Re: [twitter-dev] What happened, happened.
On 04/09/2010 08:26 PM, Taylor Singletary wrote: Let there be no doubt that not only will Chirp be an opportunity for developers to learn and talk to platform developers Twitter employees directly about what will obviously be a hot topic on everyone's mind, but Chirp will also in itself be a platform for Twitter to clarify existing capabilities and introduce new platform opportunities available to our obviously instrumental developer community. No one Twitter experience will ever define Twitter. No one app will ever define a platform. Not all use cases, analytical opportunities, clients, redefinitions, evolutions of, extrapolations on, libraries for the API of, insights for, integrations of, thoughts on, run-on-sentences-written-about, financial opportunities, or choices offered to consumers in the Twitter universe have been explored. Or, to quote G. Spencer Brown: What is not allowed is forbidden. ;-) Interesting thought: Twitter is the *only* major API I'm aware of that does *not* require a per-user or per-company API key. Sure, there's the oAuth *application* keys, but there's no API key that tells Twitter this activity is coming from Ed Borasky, regardless of IP address or account or application. It would make my life as a developer simpler if a user of applications I create had to have an API key from Twitter to use them. Would it complicate Twitter's life substantially to do that? Do I need to bring a copy of I Ching to Chirp? Is there a favored translation? The postings from Twitter on this mailing list quite often appear to have been composed by a similar process. ;-) -- M. Edward (Ed) Borasky borasky-research.net @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: Twitter buying Tweetie
the way that i usually explain twitter.com (the web site) is that it embodies one particular experience of twitter. twitter.com needs to implement almost every feature that twitter builds, and needs to implement it in a way that is easy to use for the* lowest common denominator of user*. this now also holds for the iphone. so, one possible answer for how to innovate and do potentially interesting/lucrative/creative things is to simply not target the lowest common denominator user anymore. find a particular need, and not the generic need, and blow it out of the water. what i am most interested in seeing is apps that break out of the mold and do things differently. ever since i joined the twitter platform, our team has built APIs that directly mirror the twitter.com experience -- 3rd party developers have taken those, and mimicked the twitter.com experience. for example, countless apps simply fetch timelines from the API and just render them. can we start to do more creative things? i don't have any great potentials off the top of my head (its midnight where i am now, and i flew in on a red-eye last night), but here are a few potential ones. i'm sure more creative application developers can come up with more. i want to see applications for people that: - don't have time to sit and watch twitter 24/7/365. while i love to scan through my timeline, frankly, that's a lot of content. can you summarize it for me? can you do something better than chronological sort? - want to understand what's going on around them. how do i discover people talking about the place i currently am? how do i know this restaurant is good? this involves user discovery, place discovery, content analysis, etc. - want to see what people are talking about a particular tv show, news article, or any piece of live-real-world content in real time. how can twitter be a second/third/fourth screen to the world? perhaps the OS X music playback app market is a poor example? sure itunes is a dominant app, but last.fm, spotify, etc., all exist and are doing things that itunes can't do. On Fri, Apr 9, 2010 at 7:26 PM, funkatron funkat...@gmail.com wrote: Twitter did this to BB clients too, today. You think this is the last platform they'll do an Official Client on? Take a look at the OS X music playback app market to see the future of Twitter clients. Here's the shirt for the Chirp keynote: http://spaz.spreadshirt.com/ Have fun in SF next week, everybody! -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.comxmpp%3afunkat...@gmail.com On Apr 9, 10:18 pm, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before anyone rants, let me say congratulations Loren, and congratulations Twitter. Awesome! Totally awesome! :-) Tim. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] What happened, happened.
Interesting thought: Twitter is the *only* major API I'm aware of that does *not* require a per-user or per-company API key. Sure, there's the oAuth *application* keys, but there's no API key that tells Twitter this activity is coming from Ed Borasky, regardless of IP address or account or application. It would make my life as a developer simpler if a user of applications I create had to have an API key from Twitter to use them. Would it complicate Twitter's life substantially to do that? i'm confused what you're asking for? it seems to me that with oauth does? with 3-legged oauth, as the requests are signed with an access token the access token is tied to a user at some point, no? Do I need to bring a copy of I Ching to Chirp? Is there a favored translation? The postings from Twitter on this mailing list quite often appear to have been composed by a similar process. ;-) you just got way too smart for me. i'm just a lowly engineer. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter buying Tweetie
It is, of course, possible to find niches here, and we can of course come up with ideas that could work. I certainly am not debating that. But you have to admit that this is a big, big bomb to drop in the development community; bigger than anything since *maybe* the Summize acquisition, and the whole shebang was a lot smaller then. And Summize was doing work that most developers couldn't do, because of the technical issues involved. And I might also suggest that choice and diversity is generally a good thing, even in areas you personally find boring. But perhaps not in the financial sense for Twitter, which is why stuff like this happens. It's not really just what was done, but *how* it was done that was most disappointing. And I bet you didn't have anything to do with that, so not much to say there. Actually, I suspect iTunes is a great analogy, even with the other apps you suggest. iTunes did destroy any competition in the primary music playback app market, and I believe (anecdotally though) that it dominates the lowest common denominator market -- also the largest part of the market. I'll be happy to buy you a drink when Spotify and and last.fm combined hit 50% of iTunes usage. They are the niche apps along the lines you suggest we should be making. -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 10, 12:20 am, Raffi Krikorian ra...@twitter.com wrote: the way that i usually explain twitter.com (the web site) is that it embodies one particular experience of twitter. twitter.com needs to implement almost every feature that twitter builds, and needs to implement it in a way that is easy to use for the* lowest common denominator of user*. this now also holds for the iphone. so, one possible answer for how to innovate and do potentially interesting/lucrative/creative things is to simply not target the lowest common denominator user anymore. find a particular need, and not the generic need, and blow it out of the water. what i am most interested in seeing is apps that break out of the mold and do things differently. ever since i joined the twitter platform, our team has built APIs that directly mirror the twitter.com experience -- 3rd party developers have taken those, and mimicked the twitter.com experience. for example, countless apps simply fetch timelines from the API and just render them. can we start to do more creative things? i don't have any great potentials off the top of my head (its midnight where i am now, and i flew in on a red-eye last night), but here are a few potential ones. i'm sure more creative application developers can come up with more. i want to see applications for people that: - don't have time to sit and watch twitter 24/7/365. while i love to scan through my timeline, frankly, that's a lot of content. can you summarize it for me? can you do something better than chronological sort? - want to understand what's going on around them. how do i discover people talking about the place i currently am? how do i know this restaurant is good? this involves user discovery, place discovery, content analysis, etc. - want to see what people are talking about a particular tv show, news article, or any piece of live-real-world content in real time. how can twitter be a second/third/fourth screen to the world? perhaps the OS X music playback app market is a poor example? sure itunes is a dominant app, but last.fm, spotify, etc., all exist and are doing things that itunes can't do. On Fri, Apr 9, 2010 at 7:26 PM, funkatron funkat...@gmail.com wrote: Twitter did this to BB clients too, today. You think this is the last platform they'll do an Official Client on? Take a look at the OS X music playback app market to see the future of Twitter clients. Here's the shirt for the Chirp keynote:http://spaz.spreadshirt.com/ Have fun in SF next week, everybody! -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.comxmpp%3afunkat...@gmail.com On Apr 9, 10:18 pm, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for everything you've done in the past, but now, screw you. This would not have been such a huge deal if the developer ecosystem did not play such a huge role in propelling Twitter to where it is today. Please correct me if I'm wrong. On Apr 9, 10:41 pm, Tim Haines tmhai...@gmail.com wrote: Before
[twitter-dev] Re: What happened, happened.
Interesting thought: Twitter is the *only* major API I'm aware of that does *not* require a per-user or per-company API key. Sure, there's the oAuth *application* keys, but there's no API key that tells Twitter this activity is coming from Ed Borasky, regardless of IP address or account or application. It would make my life as a developer simpler if a user of applications I create had to have an API key from Twitter to use them. Would it complicate Twitter's life substantially to do that? Yeah, this doesn't really make any sense. Users already sign in to OAuth apps and if they then use the apps, Twitter can tell what user and app the traffic is coming from. So what is your need/point? J -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter buying Tweetie
As a user and fellow developer I'm thrilled for Loren and what he's achieved... As a Twitter API and iPhone developer I'm shocked and feel like it's a kick in the teeth to us all. On Apr 10, 5:59 am, funkatron funkat...@gmail.com wrote: It is, of course, possible to find niches here, and we can of course come up with ideas that could work. I certainly am not debating that. But you have to admit that this is a big, big bomb to drop in the development community; bigger than anything since *maybe* the Summize acquisition, and the whole shebang was a lot smaller then. And Summize was doing work that most developers couldn't do, because of the technical issues involved. And I might also suggest that choice and diversity is generally a good thing, even in areas you personally find boring. But perhaps not in the financial sense for Twitter, which is why stuff like this happens. It's not really just what was done, but *how* it was done that was most disappointing. And I bet you didn't have anything to do with that, so not much to say there. Actually, I suspect iTunes is a great analogy, even with the other apps you suggest. iTunes did destroy any competition in the primary music playback app market, and I believe (anecdotally though) that it dominates the lowest common denominator market -- also the largest part of the market. I'll be happy to buy you a drink when Spotify and and last.fm combined hit 50% of iTunes usage. They are the niche apps along the lines you suggest we should be making. -- Ed Finklerhttp://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.com On Apr 10, 12:20 am, Raffi Krikorian ra...@twitter.com wrote: the way that i usually explain twitter.com (the web site) is that it embodies one particular experience of twitter. twitter.com needs to implement almost every feature that twitter builds, and needs to implement it in a way that is easy to use for the* lowest common denominator of user*. this now also holds for the iphone. so, one possible answer for how to innovate and do potentially interesting/lucrative/creative things is to simply not target the lowest common denominator user anymore. find a particular need, and not the generic need, and blow it out of the water. what i am most interested in seeing is apps that break out of the mold and do things differently. ever since i joined the twitter platform, our team has built APIs that directly mirror the twitter.com experience -- 3rd party developers have taken those, and mimicked the twitter.com experience. for example, countless apps simply fetch timelines from the API and just render them. can we start to do more creative things? i don't have any great potentials off the top of my head (its midnight where i am now, and i flew in on a red-eye last night), but here are a few potential ones. i'm sure more creative application developers can come up with more. i want to see applications for people that: - don't have time to sit and watch twitter 24/7/365. while i love to scan through my timeline, frankly, that's a lot of content. can you summarize it for me? can you do something better than chronological sort? - want to understand what's going on around them. how do i discover people talking about the place i currently am? how do i know this restaurant is good? this involves user discovery, place discovery, content analysis, etc. - want to see what people are talking about a particular tv show, news article, or any piece of live-real-world content in real time. how can twitter be a second/third/fourth screen to the world? perhaps the OS X music playback app market is a poor example? sure itunes is a dominant app, but last.fm, spotify, etc., all exist and are doing things that itunes can't do. On Fri, Apr 9, 2010 at 7:26 PM, funkatron funkat...@gmail.com wrote: Twitter did this to BB clients too, today. You think this is the last platform they'll do an Official Client on? Take a look at the OS X music playback app market to see the future of Twitter clients. Here's the shirt for the Chirp keynote:http://spaz.spreadshirt.com/ Have fun in SF next week, everybody! -- Ed Finkler http://funkatron.com @funkatron AIM: funka7ron / ICQ: 3922133 / XMPP:funkat...@gmail.comxmpp%3afunkat...@gmail.com On Apr 9, 10:18 pm, Dewald Pretorius dpr...@gmail.com wrote: It's great for Loren. But, there's a problem, and I hope I'm not the only seeing it. Twitter has just kicked all the other developers of Twitter iPhone (and iPad) clients in the teeth. Big time. Now suddenly their products compete with a free product that carries the Twitter brand name, and that has potentially millions of dollars at its disposal for further development. It's really like they're saying, We picked the winner. Thanks for
Re: [twitter-dev] Re: Twitter buying Tweetie
On 04/09/2010 09:20 PM, Raffi Krikorian wrote: - don't have time to sit and watch twitter 24/7/365. while i love to scan through my timeline, frankly, that's a lot of content. can you summarize it for me? can you do something better than chronological sort? Yeah ... I think a fair number of people want something like that. If Twitter would like to build it, grab me at Chirp and I'll give you some pointers to the relevant NLP literature. It's not a small enough project for a single-man shop like myself. - want to understand what's going on around them. how do i discover people talking about the place i currently am? how do i know this restaurant is good? this involves user discovery, place discovery, content analysis, etc. I think that ship has sailed, and the liner companies are Google, Yahoo, Yelp, Foursquare, Gowalla, Facebook, etc. Twitter's way late to that party. I'm not saying there aren't opportunities in location-based services - in fact, I think Twitter's cautious approach to a subject that others seem to be gung-ho about is the strategically correct one. But Twitter had a really cool location demo at SxSW and just about everybody ignored it and focused on the Foursquare / Gowalla smackdown. And everyone is waiting for Facebook to drop the other shoe. Then again, I haven't heard about @anywhere yet. ;-) - want to see what people are talking about a particular tv show, news article, or any piece of live-real-world content in real time. how can twitter be a second/third/fourth screen to the world? Now *that* one I like! Twitter as the world's real-time newspaper, complete with weather, sports, traffic, celebrity gossip, letters to the editor, etc. I think you could wipe USA Today off the map (pun intended). -- M. Edward (Ed) Borasky borasky-research.net @znmeb A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
