“What’s Happening” to
“What’s Happening Here”
by Raffi Krikorian
What am I going to talk
about?
• What is a “place”?
• How do users expect to use “where” information?
• Where do you actua...
Location =
Context + Relevancy
Location =
Context + Relevancy
• Transforming the “What’s happening” to “What’s
happening here”
• 140 character limit
• Me...
No location!
What is a “place”?
What is a “place”?
• 36o5’19.176”N, 115o10’36.084”
• A pair of decimals
• Gets a bit complicated when trying to account fo...
What is a place?

                   • 36o5’19.176”N,
                   115o10’36.084”
                   • Needs a map t...
A place is a polygon
A place is a name
A place is a name
• 2010 Fort Mason Center, San Francisco, CA
A place is a name
• 2010 Fort Mason Center, San Francisco, CA
• Laguna St and Marina Blvd
A place is a name
• 2010 Fort Mason Center, San Francisco, CA
• Laguna St and Marina Blvd
• “The Marina”
A place is a name
• 2010 Fort Mason Center, San Francisco, CA
• Laguna St and Marina Blvd
• “The Marina”
• Fort Mason
A place is a name
• 2010 Fort Mason Center, San Francisco, CA
• Laguna St and Marina Blvd
• “The Marina”
• Fort Mason
• WO...
APIs
Original attempts
• Adding it to a Tweet
  • Use myloc.me, et. al. to add text to the tweet
  • Localizes mobile phone and...
Profile location
curl -u USERNAME:PASSWORD 
-d location="San Francisco, California" 
http://twitter.com/account/update_loc...
Geotagging API
• Adding it to a Tweet
  • Per-tweet basis
  • Out of band
• Native Twitter support
  • Simple way to updat...
Geo-hose
curl "http://stream.twitter.com/1/statuses/
filter.xml?
locations=-74.5129,40.2759,-73.5019,41.2759
Trends API
• Global trends
  • Currently on front page of Twitter.com
  • Analysis of “hot conversations”
• Location speci...
Geo-place API
• Reverse geocoder to get a list of places that a Tweet
can be attached to
• Place can then be permanently a...
Annotations are the Future
• Arbitrary metadata attached to Tweets
• Can store more than one location
• Can store more tha...
What do users expect?
Sharing coordinates

                      • “Geotagging”
                      • Photo sharing
                      • Ta...
Sharing polygons

                   • Privacy
                   implications are
                   better
             ...
Sharing names
• Can make a connection to users
• Inverse relationship between privacy and granularity
• I18n hell
Working with users
Implicit vs Explicit
• Do you automatically add location content,
or does the user have to explicitly do
something?
• Beca...
Workflow
• Plan for asynchronicity
• Client may get “streamed” updated
information stream to act on
• Almost certainly nee...
Lying is a feature
• Not just falsification
• Understand if you’re building a “verifiied” location
service
• Sometimes jus...
Privacy
• Give the user control
• Communicate to the user what’s
happening both in the client and
the server
• Can somebod...
?????
Questions?
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
"What's Happening" to "What's Happening Here" @ Chirp
Upcoming SlideShare
Loading in …5
×

"What's Happening" to "What's Happening Here" @ Chirp

2,428 views
2,369 views

Published on

Published in: Technology
1 Comment
4 Likes
Statistics
Notes
No Downloads
Views
Total views
2,428
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
46
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide











































  • "What's Happening" to "What's Happening Here" @ Chirp

    1. 1. “What’s Happening” to “What’s Happening Here” by Raffi Krikorian
    2. 2. What am I going to talk about? • What is a “place”? • How do users expect to use “where” information? • Where do you actually get “location” from? • What is Twitter doing?
    3. 3. Location = Context + Relevancy
    4. 4. Location = Context + Relevancy • Transforming the “What’s happening” to “What’s happening here” • 140 character limit • Metadata! • People want to talk about places
    5. 5. No location!
    6. 6. What is a “place”?
    7. 7. What is a “place”? • 36o5’19.176”N, 115o10’36.084” • A pair of decimals • Gets a bit complicated when trying to account for “precision” • Doesn’t mean much to people
    8. 8. What is a place? • 36o5’19.176”N, 115o10’36.084” • Needs a map to make sense!
    9. 9. A place is a polygon
    10. 10. A place is a name
    11. 11. A place is a name • 2010 Fort Mason Center, San Francisco, CA
    12. 12. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd
    13. 13. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd • “The Marina”
    14. 14. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd • “The Marina” • Fort Mason
    15. 15. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd • “The Marina” • Fort Mason • WOEID and twID (28b412827a461f1e)
    16. 16. APIs
    17. 17. Original attempts • Adding it to a Tweet • Use myloc.me, et. al. to add text to the tweet • Localizes mobile phone and puts location “in band” • Takes from 140 characters • Setting profile level locations • Setting the user/location of a Twitter user • There’s an API for that! • Not a per-tweet basis
    18. 18. Profile location curl -u USERNAME:PASSWORD -d location="San Francisco, California" http://twitter.com/account/update_location.xml
    19. 19. Geotagging API • Adding it to a Tweet • Per-tweet basis • Out of band • Native Twitter support • Simple way to update status with location data • Ability to remove geotags from tweets en masse • Across all Twitter APIs
    20. 20. Geo-hose curl "http://stream.twitter.com/1/statuses/ filter.xml? locations=-74.5129,40.2759,-73.5019,41.2759
    21. 21. Trends API • Global trends • Currently on front page of Twitter.com • Analysis of “hot conversations” • Location specific trends • Through a variety of means into trends • Locations exposed over the API as WOEIDs • Can ask for available trends sorted by distance from your location
    22. 22. Geo-place API • Reverse geocoder to get a list of places that a Tweet can be attached to • Place can then be permanently attached to the Tweet and appears in all APIs • Allows for “location obfuscation” rends
    23. 23. Annotations are the Future • Arbitrary metadata attached to Tweets • Can store more than one location • Can store more than one ID
    24. 24. What do users expect?
    25. 25. Sharing coordinates • “Geotagging” • Photo sharing • Talking about a specific place • Needs a map • Privacy implications
    26. 26. Sharing polygons • Privacy implications are better • If you thought sharing one pair of numbers was bad
    27. 27. Sharing names • Can make a connection to users • Inverse relationship between privacy and granularity • I18n hell
    28. 28. Working with users
    29. 29. Implicit vs Explicit • Do you automatically add location content, or does the user have to explicitly do something? • Because this is a privacy sensitive issue - users want to “be in control”
    30. 30. Workflow • Plan for asynchronicity • Client may get “streamed” updated information stream to act on • Almost certainly need human intervention
    31. 31. Lying is a feature • Not just falsification • Understand if you’re building a “verifiied” location service • Sometimes just want to annotate a comment with a place
    32. 32. Privacy • Give the user control • Communicate to the user what’s happening both in the client and the server • Can somebody else tag your house?
    33. 33. ????? Questions?

    ×