Recomendados
Mais conteúdo relacionado
Semelhante a "What's Happening" to "What's Happening Here" @ Chirp
Semelhante a "What's Happening" to "What's Happening Here" @ Chirp (20)
Mais de Raffi Krikorian
Mais de Raffi Krikorian (20)
Último
Último (20)
"What's Happening" to "What's Happening Here" @ Chirp
- 2. “What’s Happening” to “What’s Happening Here” by Raffi Krikorian
- 3. 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?
- 4. Location = Context + Relevancy
- 5. Location = Context + Relevancy • Transforming the “What’s happening” to “What’s happening here” • 140 character limit • Metadata! • People want to talk about places
- 11. No location!
- 12. What is a “place”?
- 13. 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
- 14. What is a place? • 36o5’19.176”N, 115o10’36.084” • Needs a map to make sense!
- 15. A place is a polygon
- 16. A place is a name
- 17. A place is a name • 2010 Fort Mason Center, San Francisco, CA
- 18. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd
- 19. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd • “The Marina”
- 20. A place is a name • 2010 Fort Mason Center, San Francisco, CA • Laguna St and Marina Blvd • “The Marina” • Fort Mason
- 21. 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)
- 22. APIs
- 23. 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
- 24. Profile location curl -u USERNAME:PASSWORD -d location="San Francisco, California" http://twitter.com/account/update_location.xml
- 25. 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
- 30. 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
- 32. 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
- 33. Annotations are the Future • Arbitrary metadata attached to Tweets • Can store more than one location • Can store more than one ID
- 34. What do users expect?
- 35. Sharing coordinates • “Geotagging” • Photo sharing • Talking about a specific place • Needs a map • Privacy implications
- 36. Sharing polygons • Privacy implications are better • If you thought sharing one pair of numbers was bad
- 37. Sharing names • Can make a connection to users • Inverse relationship between privacy and granularity • I18n hell
- 39. 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”
- 40. Workflow • Plan for asynchronicity • Client may get “streamed” updated information stream to act on • Almost certainly need human intervention
- 41. 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
- 42. 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?
- 43. ????? Questions?