- From: Karl Dubost <karld@opera.com>
- Date: Fri, 4 Feb 2011 14:16:49 -0500
- To: Glenn Maynard <glenn@zewt.org>
- Cc: Charles McCathieNevile <chaals@opera.com>, Robin Berjon <robin@berjon.com>, Web Applications Working Group WG <public-webapps@w3.org>
Le 23 janv. 2011 à 18:13, Glenn Maynard a écrit : > But that's the point: when you put pictures (or tax forms, or other private files) on a webserver, you have mechanisms for access control. You wouldn't put private files on a publically-accessible webserver; you put them on a password-protected one. In fact many people do without knowing on many current sites. There is a notion of subtle opacity, aka something which is part of the public but "more difficult" to access. It has its good and bad social impacts. For example, if you have a flickr account, put an image with a limited shared context. Now find the exact URI of the image. It should be starting with static.flickr.com. Unlog, put this URI into your browser and you should be able to access the image. -- Karl Dubost - http://dev.opera.com/ Developer Relations & Tools, Opera Software
Received on Friday, 4 February 2011 19:17:27 UTC