[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
[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.
[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.
