Facebook Developer Sessions: Open Graph Protocol, Credits, Analytics, and Insights
Table of Contents
- 1. Sessions
- 2. New Tools
- 3. Techniques
- 3.1. 12:30pm Making Things Fast
- 3.1.1. Questions
- 3.1.1.1. Apply the TOSS process for the redirections
- 3.1.1.2. Creating user automatically
- 3.1.1.3. What is realtime event notification
- 3.1.1.4. Parallel JS load -> lazy load of JS
- 3.1.1.5. Active session required for push notification of user data change
- 3.1.1.6. multi-queries
- 3.1.1.7. What are the timeouts for application response
- 3.1.1.8. Slow content rendering
- 3.1.1.9. New features
- 3.1.1.10. New Connect methods should be updated on the Wiki
- 3.1.1.11. Does pre-load query count against 15s timeout
- 3.1.1. Questions
- 3.2. DONE 1:30pm Integrating with Facebook
- 3.2.1. New like feature
- 3.2.2. OAuth 2 implemented
- 3.2.3. Much cleaner interface for getting the access token
- 3.2.4. Client-side access token is likely the easiest
- 3.2.5. Server-side requires redirectors
- 3.2.6. Mobile also uses OAuth
- 3.2.7. Facebook Connect library is open and available on GitHub
- 3.2.8. Size is 20kb for the library rather than 80kb
- 3.2.9. Auth token is now trivial to acquire and save
- 3.2.10. Graph API has access to public information by default
- 3.2.11. Social Plugins
- 3.2.12. Authentication
- 3.2.13. New caching policy: remove the 24h restriction
- 3.2.14. How do the widgets decrade
- 3.3. 2:30pm Focus on Feed
- 3.4. 3:30pm Design the Social Web
- 3.1. 12:30pm Making Things Fast
- 4. Facebook Strategy
1. Sessions
This is open graph protocal, credits, analytics and insights
2. New Tools
2.1. DONE 12:30pm Open Graph
12:25pm PST: Mark Kinsey and Austin Haugen from Facebook will be presenting on Social Plugins and the Open Graph Protocol.
http://developers.facebook.com/docs/api
Like button is a plugin. Trivial to implement assuming that some metadata is present for the page.
Use the Open Graph protocol to turn objects into URLs.
Like link rel="canonical".
<iframe src="http://www.facebook.com/widgets/like.php?href=http://example.com" scrolling="no" frameborder="0" style="border:none; width:450px; height:80px"></iframe>
2.3. DONE 2:30pm Graph API
Mike Vernac
Arjun Banker http://www.linkedin.com/in/arjunbanker
2.3.4. Search
https://graph.facebook.com/search?q=
New parameters user type event.
2.3.5. Realtime updates
2.3.6. Stability and documentation
Hackathon several weeks ago; should be considered stable.
Internal release to confirm how some of the core infrastructure should work to allow for this to release cleanly. Would need to have the core tools established before this could happen.
3. Techniques
3.1. 12:30pm Making Things Fast
Find fast query for the fast set. If you don't have enough data use delay.
Don't over fetch.
Don't over filter.
api.facebook.com returns around 400ms. However, a backend memcache server returns in 10ms given the caching policy.
- Get firstName and lastName for all users that have added the application.
- Notification delivered when something has changed for a user
- Make request against api
- Update the local cache
There is a new api-read.facebook.com: designed to shave off 70 ms off cross-coast penalty.
Access to developers who wrote the libraries.
Significant amount of change in the last year.
3.1.1. Questions
3.1.1.1. Apply the TOSS process for the redirections
These are all new features after a user has authed the page.
3.1.1.2. Creating user automatically
3.1.1.3. What is realtime event notification
3.1.1.4. Parallel JS load -> lazy load of JS
Lazy loading will be coming soon. Things not often used will be lazy loaded. No time.
This is based on user data that is being generated now.
3.1.1.6. multi-queries
Characteristics of the query requires empirical testing to determine where the slow and fast backend limits would be based on the complexity of the query.
3.1.1.7. What are the timeouts for application response
15s
Make sure you have a histogram listing all response times. 12s+ should be an error.
3.1.1.8. Slow content rendering
Need to make a decision behind what is the core content that needs to show. The flow depends on making trade-offs. Entirely possible to create a perfect page with comprehensive data that will never load.
3.1.1.9. New features
Application configuration includes these elements. Would need to treat strategic as the core
3.1.1.10. New Connect methods should be updated on the Wiki
Not strongly typed.
3.2. DONE 1:30pm Integrating with Facebook
3.2.1. New like feature
Simple one line reference.
Like applied to products on Levi's.
Pandora: Artist
This all then feeds back into the social graph.
3.2.2. OAuth 2 implemented
3.2.6. Mobile also uses OAuth
3.2.7. Facebook Connect library is open and available on GitHub
Fork and fix if necessary.