> It seems that it's currently using a "shared secret" approach instead of supporting signed-requests, thus limiting its use to HTTPS only.
Yeah, I believe oauth1 support would address that, and is planned. :)
Yeah, I believe oauth1 support would address that, and is planned. :)
No comments yet.