- From: Mark Lizar <info@smartspecies.com>
- Date: Tue, 24 Apr 2012 18:48:56 +0100
- To: Karl Dubost <karld@opera.com>
- Cc: public-privacy@w3.org
- Message-Id: <3D632932-4BD8-44BD-8266-E0D766A1870A@smartspecies.com>
:-) > Jack Byrnes: I'm watching you. > Greg Focker: Yeah, well I have eyes too, so I'll be watching you… > watching me. Nice way to put a finger on the issue. People are being watched but it is very difficult to watch cookies, web history access, surveillance camera's and geo-loaction permissions. Let alone keep track and understand the numerous privacy policy and terms of services agreements that we all apparently subscribe to when just sending an email using a smart phone. > > There are plenty of issues with all these notifications be for CCTV, > cookies, WIFI bases, Even if we have access to the policies it needs to be meaningful. The fact that information age technology is bolted on to industrial age infrastructure dosnt help. CCTV is a glaring example, as the title itself is technically explicit specifying a type of video surveillance defined in such a way as to alleviate privacy and security concerns. (CCTV referring to a camera connected to a cable connected directly to a monitor.) Which, with CCTV becoming an integrated part of networks, the term CCTV is in danger of becoming fundamentally misleading, and the term itself undermining the security it advertises to the individual. At some point in time the use of the term CCTV becomes disproportionate to the type of technology used. A quick search on Google with this search term "inurl:LvAppl intitle:liveapplet" shows a CCTV hack, any of these camera's found in this search are clearly not CCTV. (as this video illustrates) > > Still the reciprocity is needed. If we want surveillance devices > (cameras, computers, softwares) be part of the society, then they > need an id, which is symmetrically accessible. > tosback.org is a good example of an emerging surveillance privacy/ trust framework. The Tosback project illustrates a surveillance framework where policies and there changes are recorded, this provides a context enabling people to be able to see how different the service agreement is from the one they originally agreed to. While also providing transparency for the service User over what the current privacy policy is. Need more projects like this. Better yet surveillance should be explicit at the engineering level, and get rid of policies all together. :-) - Mark
Received on Tuesday, 24 April 2012 17:57:46 UTC