From Mozilla’s new BrowserID to OpenID and the Facebook Graph API, determining user identity has become a simple matter of leveraging a profile. The problem, and the source of many heated debates, arises when trying to determine whether to identify a user by their true, real life, identity and whether that should be forced on them when interacting online. Social powerhouses like Facebook and Google+ are throwing their weight behind forcing users to be directly tied to their real life identity, but what does this mean for privacy, anonymity, and online social interactions? In this talk we’ll explore the concepts behind identity models, how online and real life social graphs are used for defining identity and relationships, and how using real identity and social graph models have led to real life issues of security and privacy worldwide. Through these models, we’ll explore how services like BrowserID, OpenID and the Facebook Graph API are used to construct user identity online.
by Dave Stokes
by Wil Moore
by Joël Perras
When OpenSocial was first introduced, the main goal was to create an open and distributed alternative to the closed off Facebook platform for social apps. Since then much has happened: The specification has majored and powerful new features have been introduced. More and more social networks are implementing OpenSocial containers, allowing developers to reach over 900 million users with one social app. Additionally education organizations and enterprise companies like IBM, SAP, SurfNET or Atlassian are seeing the benefits of an open standard to open them up to other developers. In this presentation I will introduce you to OpenSocial, and walk you through an example to show you how easy it is to connect an existing web application to enterprise products and social networks alike. I will especially highlight some of the new OpenSocial 2.0 features, such as Embedded Experiences or OpenSearch, that help you with a tight integration into your user's existing tools and workflows.
Que se soit suite à une attaque, une défaillance matérielle ou un bogue applicatif, et malgré toute les précautions prises en amont, aucune application en production n'est à l'abri d'une catastrophe.
L'important est d'avoir un plan de reprise sur incident efficace pour limiter le plus possible l'impact d'un tel incident sur la qualité de service.
Cela passe par une phase de préparation (mise en place de logs, sauvegardes régulière, etc) et par un plan d'action pour le jour J (Communication de crise, diagnostiques, priorisation des tâches, etc.)
by David Zuelke
The case for online identity has been present for as long as there has been a need to customize a web experience for an individual person. From OpenID to BrowserID, there are open solutions for solving the issue of having different logins for all of the sites and services we use. The problem with open identity systems in the Ecommerce world is that the identifying characteristics of a user in current implementations is shallow, providing basically a “yes, this person has an account” answer to “who is this user?”.
This is where new X.commerce identity is trying to change identity. By leveraging off of the massive user Ecommerce information of PayPal and eBay, open Ecommerce identity is now a valuable source of real user data. Using buying and selling history, user ratings, profile identifiers and a vast array of different user data, X.commerce identity is able to define “trust levels” for a user who signs in to your site and provide solutions for easy, secure identity and payment.
by Joseph Wilk
by Heath Kesler
by Jake Smith
Ever thought how much better CSS would be if you only had variables or expressions or "x" or "y". Tired of remembering all of the browser prefixes for the new CSS3 features? Enter LESS CSS. LESS CSS is a CSS pre-processor that offers variables, mixins, expressions and much more. This is how everyone dreamed CSS would be ran. In this session, you will learn how to fully harness all the functionality of LESS while avoiding some of the pitfalls many new users face. CSS3 will never seem easier!
by jeremyclarke
by Michael Michalowicz
by David Mirza
by lpcarignan
by Sean Yo
by Mike McQuaid
by Joël Perras