93
edits
(→Introduction and Rationale: minor typographic changes) |
|||
| Line 18: | Line 18: | ||
Now imagine a user who regularly visits three different social media sites: GMail (it's social and it mediates), Twitter and Facebook. The traces left behind at each site tell stories about the user's online relationships (e.g., email threads, @-discussions, RTs, wall posts, etc.). What if the browser could learn about them over time? What if it could do something smart with that knowledge? Some of the data will cross site lines, as some people live in both Facebook and GMail, or in all three simultaneously. The relationship (in the online sense) is the aggregate of all these sources. The browser is especially well-placed to understand these relationships. That's what we intend <code>jetpack.people</code> to do. | Now imagine a user who regularly visits three different social media sites: GMail (it's social and it mediates), Twitter and Facebook. The traces left behind at each site tell stories about the user's online relationships (e.g., email threads, @-discussions, RTs, wall posts, etc.). What if the browser could learn about them over time? What if it could do something smart with that knowledge? Some of the data will cross site lines, as some people live in both Facebook and GMail, or in all three simultaneously. The relationship (in the online sense) is the aggregate of all these sources. The browser is especially well-placed to understand these relationships. That's what we intend <code>jetpack.people</code> to do. | ||
Clearly, we must ensure privacy. Yet, this can be accomplished in the same way as the browser protects browsing history. We see this as a particularly forward-looking proposal. We think it's time for the browser to get into social media and take charge of making user experience richer. To do this, we intend to take advantage of [http://social.cs.uiuc.edu/people/gilbert/30 recent research] inside jetpack.people that demonstrates how to model relationships based on social media data. We also describe a handful of jetpack.people application scenarios later in this document. | Clearly, we must ensure privacy. Yet, this can be accomplished in the same way as the browser protects browsing history. We see this as a particularly forward-looking proposal. We think it's time for the browser to get into social media and take charge of making user experience richer. To do this, we intend to take advantage of [http://social.cs.uiuc.edu/people/gilbert/30 recent research] inside <code>jetpack.people</code> that demonstrates how to model relationships based on social media data. We also describe a handful of <code>jetpack.people</code> application scenarios later in this document. | ||
=== Proposal === | === Proposal === | ||
edits