Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve The README #11

Open
nsanta opened this issue Aug 27, 2010 · 4 comments
Open

Improve The README #11

nsanta opened this issue Aug 27, 2010 · 4 comments

Comments

@nsanta
Copy link
Owner

nsanta commented Aug 27, 2010

Currently, the README sucks. needs Improvements

@nielsjansendk
Copy link

If you could start with explaining how to get authorization to work for a canvas app, that would be awesome for me. I think this is a really great gem, good work!

@nsanta
Copy link
Owner Author

nsanta commented Sep 15, 2010

@ninajansen: Updated the expanation of how to use Canvas module for parse signed requests when the app runs as a facebook canvas app.

@rklubenspies
Copy link

Could you please provide an example of how to store a user's token and email in a database so that one could replace a typical brick and mortar login system with fbgraph (and a basic model to store a Facebook auth token). That way when a user logged in again all of their information would be remembered! An example like that would be much appreciated!

@andypalmer
Copy link

Storing a 3rd party id as a number, even if it looks like one, is bad practice. We don't need to do number-y things with the ids (mathematical functions etc)
(see twitpocalypse, http://absolutely2nothing.wordpress.com/2009/08/02/the-twitpocalypse-returns/ )

Rather than recommend that clients store it in a BIGINT column, I would recommend VARCHAR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants