I have only used OAuth for sending private twitter messages with a
program, so I can only provide info through the twitter perspective.
There is a handshake that needs to take place, during which your
client program exchanges (token, key) pairs with the authentication
service.
Say you want to acce
i want to do some things which require OAuth. i don't like it, but
it's what many folks are doing now and i don't think i can fight it.
has anyone looked into this?
architecturally, it's not immediately clear to me how much of the
http dance out to be in factotum. it could just store access keys.
