[locationaware-specs] Icon Design

[Doug Turner]

Timeless,
might be a good idea to read my last email.  I am indeed suggesting a  
dialog when a site asks for location info and that icon would be  
something that would allow you to change your current privacy settings.

Of course, we probably need to spec this out a bit more than my last  
email, right.? :-)

Doug


On Apr 3, 2007, at 3:15 PM, timeless wrote:

> On 4/3/07, Ryan Sarver <rsarver at skyhookwireless.com> wrote:
>> Good point – this is more of a notification than an actionable  
>> item, so the
>> lock icon is good analogy.
>
> sorry. i haven't had time to read any of the background/specs/URLs/ 
> etc.
>
> but wouldn't something being location aware be actionable to the
> extent that i might choose to allow or disallow access between the
> page and my device's coordinate information?
>
> The security icon doesn't really do that today, although it could and
> arguably should.
> today, instead if there's a secure site w/ insecure content, you get
> an annoying dialog. instead in some future product you might get only
> the secure content w/ broken lock icons for images and an option in
> the lock icon that allows you to load insecure content.
>
> to see how that would look, play w/ the NoScript FireFox extension.
>
> And no, this isn't off topic. I'm probably going to have some
> significant influence in how location is reflected in the browser I
> ship on my device, and I'm very concerned about whether a user's
> location is made available to random sites. I hope that some model
> similar to NoScript's menu will be used to allow users to decide which
> sites will be able to access location information. (The actual
> implementation will probably be more complicated than NoScript,
> because you can basically say "always allow a page to access location
> information if it has scripts from <x>", "never allow a page to access
> location information if it has scripts from <x>","unless otherwise
> restricted, allow a page with scripts from <x> to access location
> information", and "scripts from <x> do not influence access to
> location information".
>
> Talking with a UI designer about this problem is currently at least a
> year away (including building a mock up to show the UI designer), but
> I don't want people to make specs for things without keeping in mind
> the uses that I expect to be present.
> _______________________________________________
> locationaware-specs mailing list
> locationaware-specs at locationaware.org
> http://lists.locationaware.org/mailman/listinfo/locationaware-specs