Campbell et al v. Facebook Inc.

Filing 199

NOTICE by Facebook Inc. Joint Notice of Refiling of Documents Accompanying Class Certification Briefs and Evidentiary Objections (Attachments: # 1 Ex. 1 - Replacement for Dkt. 178-1, # 2 Ex. 2 - Replacement for Dkt. 183-4, # 3 Ex. 3 - Replacement for Dkt. 179-1, # 4 Ex. 4 - Replacement for Dkt. 184-3, # 5 Ex. 5 - Replacement for Dkt. 179-2, # 6 Ex. 6 - Replacement for Dkt. 179-3, # 7 Ex. 7 - Replacement for Dkt. 179-4, # 8 Ex. 8 - Replacement for Dkt. 179-5, # 9 Ex. 9 - Replacement for Dkt. 179-6, # 10 Ex. 10 - Replacement for Dkt. 179-7, # 11 Ex. 11 - Replacement for Dkt. 179-10, # 12 Ex. 12 - Replacement for Dkt. 179-11, # 13 Ex. 13 - Replacement for Dkt. 179-12, # 14 Ex. 14 - Replacement for Dkt. 179-13, # 15 Ex. 15 - Replacement for Dkt. 179-14, # 16 Ex. 16 - Replacement for Dkt. 179-15, # 17 Ex. 17 - Replacement for Dkt. 179-16, # 18 Ex. 18 - Replacement for Dkt. 179-17, # 19 Ex. 19 - Replacement for Dkt. 179-18, # 20 Ex. 20 - Replacement for Dkt. 179-20, # 21 Ex. 21 - Replacement for Dkt. 180-2, # 22 Ex. 22 - Replacement for Dkt. 180-3, # 23 Ex. 23 - Replacement for Dkt. 184-9, # 24 Ex. 24 - Replacement for Dkt. 180-7, # 25 Ex. 25 - Replacement for Dkt. 180-9, # 26 Ex. 26 - Replacement for Dkt. 180-12, # 27 Ex. 27 - Replacement for Dkt. 180-17, # 28 Ex. 28 - Replacement for Dkt. 180-18, # 29 Ex. 29 - Replacement for Dkt. 180-19, # 30 Ex. 30 - Replacement for Dkt. 180-20, # 31 Ex. 31 - Replacement for Dkt. 180-21, # 32 Ex. 32 - Replacement for Dkt. 180-22, # 33 Ex. 33 - Replacement for Dkt. 180-23, # 34 Ex. 34 - Replacement for Dkt. 178-5)(Chorba, Christopher) (Filed on 6/15/2016)

EXHIBIT 10

From:

Sent:
To:

Subject:

Ethan Beard
Sunday, April 18, 2010 8:51 PM
Sandra Liu Huang
RE: f8 dev blogpost #1

If that's the order for the keynote then we can stick to it. Just seems that the OG is the real story of f8 and the plugins
are simply a way to implement it.
From: Sandra Liu Huang
Sent: Saturday, April 17, 2010 11:49 PM
To: Ethan Beard
Subject: RE: f8 dev blogpost #1

Thanks -your feedback is great. I'll incorporate tomorrow. The only thing that I'm not sure I'd change is the order of
SPI then OGP, b/c that's the order we're building up in Bret's keynote as well. I'll think about it more.
Thanks,
Sandra
From: Ethan Beard
Sent: Saturday, April 17, 2010 11:12 PM
To: Sandra Liu Huang
Subject: RE: f8 dev blogpost #1

This looks really good - nice work.
I made a bunch of small edits and a bunch of comments. If there are parts you don't like I'm happy to work specifically
on them but I feel it looks good. Feel free to ignore and delete my comments since they seem to take up a lot of space.
From: Sandra Liu Huang
Sent: Saturday, April 17, 2010 5:53 PM
To: Ethan Beard; David Swain; Cat Lee; Francis Larkin; Malorie Lucich; Kelly Winters; Gareth Davis; Rebecca Hahn;
[e-mail]; Pete Bratach
Subject: f8 dev blogpost #1

Hi all,
Thanks for the feedback for the first f8 dev blogpost. I've incorporated, and v2 is ready for review. In the Google doc
(https://docs.google.com/a/facebook.com/Doc?docid=OAeOyheOETSYoZGYSMmZ2N3FfMjFmajl6Nnpocw&hl=en), markup in your own color and try to provide suggestions vs just feedback where possible.
Thanks,
Sandra

=========================================================================

V2

Title: The Next Evolution of Facebook Platform
Author: Bret Taylor

Highly Confidential

FB000012539

Today we're hosting our third f8 conference in San Francisco. There are two important themes behind everything we're
delivering today. First, the web is moving to a model based on the connections between people and all the things they
care about. Second, this connections-based Web is well on its way to being built and providing value to both people and
developers -- the underlying graph of connections just needs to be constructed in a way that makes it easy to use and
interoperable.
Today we are introducing three new components of the Facebook Platform to make this vision real: social plug ins, the
Open Graph protocol and the new Graph API.
Social Plugins - Engaging social experiences with just one line of HTML
Social plugins are the easiest way to integrate the social graph into your site. All it takes is a Like button, available with
one line of HTML. On Facebook and now anywhere, the Like button offers users a light-weight and consistent way to
share the things and topics they're interested in. With the Like button in place, you can leverage the other Facebook
social plugins to personalize your site and drive traffic and engagement. The Activity Stream plugin shows users what
their friends have liked on your site; the Recommendations plug in gives content suggestions from your site. As with the
Like button, these social plug ins are simple to use: via a line of HTML or XFBML tags if you choose to use our new, faster
JavaScript SOK.
Open Graph Protocol - How any webpage can gain the capabilities of a Facebook Page
On Facebook, users express their identities through connections to what they care about - be it their friends or their
favorite sports teams, bottles of wine or celebrities. The Open Graph protocol opens up the social graph and lets you
enable your pages to become objects users can add to their profiles. When a user establishes this connection by clicking
Like on one of your Open Graph-enabled pages, you gain all lasting capabilities of Facebook Pages: a link from the user's
profile, ability to publish to the user's News Feed, inclusion in search on Facebook and analytics through our new Insights
product.
In summary, by giving your users better, simpler ways to connect with the content on your service, you can then use those
connections to provide more personalized, relevant experiences. And the product only gets better over time. The more
people that come back to your site, the more connections that are made, the better your service becomes.
Graph API - A drastically simplified way for developers to read and write data to Facebook
The Open Graph protocol enables users to make more connections and more fully represent themselves. Through the
applications and websites you build with Facebook Platform, users can take their connections with them across the web to
experience more social and personalized products. We are excited to introduce the Graph API, a redesign of our core
API that reflects the structure of the graph. This new API is a simple, consistent representation of data in the graph, so
that all objects and APls can be accessed via URLs.
We've also made it much easier to integrate with Facebook by using a simplified, standards-based method for
authorization. We've adopted OAuth 2.0, a standard we've co-authored with the open community, including
representatives from Google, Twitter, Yahoo and others.
The Graph API is not only simpler, it is more powerful. We've enabled a search feature which lets you search over
objects like people and events, and over the stream - both public stream updates and personalized ones for your
users. In addition, the graph is ever-changing, so we're launching real-time updates to let you subscribe to updates to
user data. We'll continue to support our old REST API indefinitely, but will focus future improvements on just the Graph
API.
Hacking the Graph
People make meaningful connections everywhere, on every site they visit, on every device they use. As we open the
graph, developers can use these connections and create a smarter, more personalized web that gets better with every
action taken. We've <link>announced partnerships</link> with Microsoft, Pandora, Yelp and Simply Hired to build
experiences where people can seamlessly transition between Facebook and other services. These unique partnerships
demonstrate how bringing friends with you creates a more meaningful, personalized and social web.

2

Highly Confidential

FB000012540

And now through Facebook Platform's new tools and technologies, every developer - new and old, big and small, novice
and advanced - can engage users, build businesses, and revolutionize industries. This year's f8 is about hacking the
graph; we hope you'll join us.
Learn more about these launches on our new developer site at http://developers.facebook.com.

3

Highly Confidential

FB000012541