The document discusses location sharing and privacy when using cloud-based services. It notes that allowing settings to define caller ID actions based on person, context, and time could help make complex privacy preferences simple. The discussion then focuses on how to share location data with a girlfriend based on preferences for time of day and day of week, keeping the location data at the city level rather than showing an exact street address. Automating privacy preferences is proposed as a way to maintain privacy with no settings.

1. location sharing
privacy
clouds
simplicity
no lat/long

2. let’s talk about
caller-id.

3. and then my
girlfriend calls.

4. if settings
could define
caller-id actions

5. would we use
them?
Connect calls from girlfriend
Always
After 5pm and on weekends
Between 12noon and 1:30pm

6. caller-id decisions
not person
not context
not time
all of the above.
Danah Boyd - @zephoria

7. yes well done Nick.
but what’s all this got to
do with location?

8. real world
where are you?

9. If we know where we
don’t know who.
If we know who we
don’t know where.

10. cloud based
preferences
share location with girlfriend
After 5pm and on weekends
Between 12noon and 1:30pm
Only City level not street level

11. device based
preferences

13. not person
not context
not time
all of the above
Danah Boyd strikes again.

14. push
microblogging
caveat transportor

15. pull
on-demand location
and if you automate?

16. How do you make
the complex = easy?
privacy - with no settings.

18. Who owns the cloud data?

19. when is a cloud
not a cloud?

20. if we can get
where are you
right...
what’s next?

21. try it now:
m.echoecho.me
nick@echoecho.me
@echoechome