Closed Prinzhorn closed 9 years ago
Just found this related issue https://github.com/jaredhanson/passport-facebook/issues/34
Since it's a hack, this shouldn't be part of fbgraph.
Since it's a hack
Could you explain which part is a hack?
were you not referring to this: https://github.com/jaredhanson/passport-facebook/issues/34#issuecomment-23073672 ? Or is it just a method to decode the signed_request?
I think I was referring to the issue as whole. As far as I remember for some reason this was the only related issue I could find on the interwebs. I was linking it because I hoped both projects would benefit from a solution.
Cool, I'll leave it open. Haven't really taken a deep dive into the issue
I'd like to keep fbgraph only accessing the api, without helper methods. A "helper" module seems like a good idea
The Facebook documentation lacks a lot when it comes to details for the "Deauthorize Callback URL" or the
signed_request
parameter.Using requestb.in I was able to find out that Facebook calls the URL when a user revokes access and passes a
signed_request
POST parameter along. Now the question is, how do I decode it and more importantly, should fbgraph offer a helper method do to so?