Oct. 4, 2011 webcast top 5 tips for building viral social web applications and sites jonatjan le blanc
Taken from lessons and technologies from "Programming Social Applications", this webcast will cover the top 5 tips that every web and application developer should know for using social techniques to increase traffic, build viral channels, and increase community involvement. We will look at mistakes that companies make when building social features into websites and applications, and how to prevent and solve those problems with open source technologies and techniques. This will take us on a tour of implementations from real products and showcase how emerging open source social technologies can be used to build rich social ecosystems. Presented by: Jonathan LeBlanc
• First round of “Mafia Wars” as an initial game partner for YAP in 2009. Failed to produce high install rates and difficult to integrate.• Second integration of “Mafia Wars” and “FishVille” in late 2010. Higher install rates, new viral channels and little integration pain.
curl http://www.google.com/s2/webfinger/?q=nake email@example.comThe User Profile: http://www.google.com/profiles/nakedtechnologistThe portable contacts link: http://www-opensocial.googleusercontent.com/api/people/118167121283215553793/The public Google Buzz feed:https://www.googleapis.com/buzz/v1/activities/118167121283215553793/@public
Understand your sharing model and integrate early
• Is the content coming from a trusted source?• How does the publisher prevent spam or abuse?• How does the publisher ensure the quality of the updates?
1. Subscriber sends signed request to publisher (e.g. using acct:firstname.lastname@example.org).1. Publisher performs discovery on endpoint to verify identity provider. • Webfinger • LRDD (Link-based Resource Descriptor)2. Provider verifies signature via public keys obtained during discovery.
Use the work that other companies have invested in
• Third round partner integrating with our social services.• They created their own OAuth implementation since we did not have an appropriate SDK.• Integration failed near completion of the code.