Hydrated message support in earlybird! http://github.com/zbowling/earlybird/
OAuth in query string doesn't work and only HMAC-SHA1 signature (unless you only allow plaintext over SSL) but its fine. One feature request would be an inital event with the users credentials just like how the user's social graph comes down initially. Right now I don't know the user's screen_name unless I also hit api.twitter.com or he tells me on the command line. With that I could drop the dependency on the twitter gem. Zac Bowling @zbowling On Wed, May 5, 2010 at 10:54 AM, Mark McBride <mmcbr...@twitter.com> wrote: > It should support both. Can you send me a direct email with a URL > that you tried? > > ---Mark > > http://twitter.com/mccv > > > > On Wed, May 5, 2010 at 10:38 AM, Zac Bowling <zbowl...@gmail.com> wrote: > > My fork of earlybird works: > > > > http://github.com/zbowling/earlybird/ > > > > Fixing it to support hydrated objects. > > > > One thing is that it doesn't appear to support query string passed OAuth > > params but if I pass it as authentication headers it works. > > > > Zac Bowling > > > > > > On Wed, May 5, 2010 at 10:31 AM, Mark McBride <mmcbr...@twitter.com> > wrote: > >> > >> OAuth support on betastream is live now. This is different OAuth > >> implementation than we use on twitter.com, so if you find any rough > >> edges please let us know quick like. > >> > >> The changes to make direct messages more distinguishable from tweets > >> has also been pushed. This will probably require some changes in > >> parsing logic when dealing with DMs. > >> > >> ---Mark > >> > >> http://twitter.com/mccv > > > > >
