I vote for Chirp: NYC!

Mike Caprio
Principal and Lead Consultant

Brainewave Consulting
402 Graham Avenue PMB 211
Brooklyn, NY  11211
p: +1-347-269-0558
@brainewave



On Feb 6, 2011, at 11:20 PM, [email protected] wrote:

> Yah, more of these would be fun.
> 
> On Feb 6, 12:28 pm, Abraham Williams <[email protected]> wrote:
>> How about some more state of the union events too. I thought they were going
>> to be quarterly.
>> 
>> Abraham
>> -------------
>> Abraham Williams | Hacker Advocate | abrah.am
>> @abraham <https://twitter.com/abraham> | github.com/abraham | blog.abrah.am
>> This email is: [ ] shareable [x] ask first [ ] private.
>> 
>> On Sun, Feb 6, 2011 at 12:21, M. Edward (Ed) Borasky <
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> [email protected]> wrote:
>>> Maybe this is the wrong place to ask, but is there going to be another
>>> Chirp? If so, when and where? I'm making my conference plans for the year
>>> and pretty much know when everything is *except* Chirp!
>> 
>>> --
>>> http://twitter.com/znmebhttp://borasky-research.net
>> 
>>> "A mathematician is a device for turning coffee into theorems." -- Paul
>>> Erdős
>> 
>>> --
>>> Twitter developer documentation and resources:http://dev.twitter.com/doc
>>> API updates via Twitter:http://twitter.com/twitterapi
>>> Issues/Enhancements Tracker:
>>> http://code.google.com/p/twitter-api/issues/list
>>> Change your membership to this group:
>>> http://groups.google.com/group/twitter-development-talk
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk
> 

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to