> We should probably just burp the whole user object out at connection start.
I think I heard an obstetrician say that once.
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- "I'd lo
Ok. The query string OAuth variant should be working now. We only
support HMAC-SHA1 (just like twitter.com does) for signature methods,
and don't have plans to support other schemes.
---Mark
http://twitter.com/mccv
On Wed, May 5, 2010 at 3:21 PM, John Kalucki wrote:
> We should probably
We should probably just burp the whole user object out at connection start.
On Wed, May 5, 2010 at 3:12 PM, Zac Bowling wrote:
> Hydrated message support in earlybird!
>
> http://github.com/zbowling/earlybird/
>
> OAuth in query string doesn't work and only HMAC-SHA1 signature (unless you
> onl
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
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 wrote:
> My fork of earlybird works:
>
> http://github.com/zbowling/earlybird/
>
> Fixing it to support hydrated objects.
>
> One
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 McBri
