Comments on: The safety net http://www.thespanner.co.uk/2010/02/04/the-safety-net/ Javascript blog with messed up syntax inside Thu, 26 Jan 2012 01:38:34 +0000 hourly 1 By: Gareth Heyes http://www.thespanner.co.uk/2010/02/04/the-safety-net/#comment-1695 Gareth Heyes Mon, 15 Feb 2010 08:07:52 +0000 http://www.thespanner.co.uk/?p=586#comment-1695 @Robert The idea would be to only enable the SN when a specific action is taken like clicking on a link that takes you to a external web site, the SN is decided depending on the meta or http header of the parent site. For example twitter should have a meta identify as Social Network. This would allow sites to function as normal but prevent exploitation by limiting the user's "first click" @Robert

The idea would be to only enable the SN when a specific action is taken like clicking on a link that takes you to a external web site, the SN is decided depending on the meta or http header of the parent site. For example twitter should have a meta identify as Social Network.

This would allow sites to function as normal but prevent exploitation by limiting the user’s “first click”

]]> By: Robert Jakobson http://www.thespanner.co.uk/2010/02/04/the-safety-net/#comment-1694 Robert Jakobson Mon, 15 Feb 2010 05:32:12 +0000 http://www.thespanner.co.uk/?p=586#comment-1694 This is exactly what the web needs, I dare say I have thought of something of this kind myself, however there is the question of how this would fit the kind of old "new trend" of having the user manipulating their own data ( or data of their friends / etc .. ) from one application inside another ? Therefore, there should be an ability to have a list of outside inputs or URL-s which are "trusted" and "accepted" sources in the context of any concrete safety net. This is exactly what the web needs, I dare say I have thought of something of this kind myself, however there is the question of how this would fit the kind of old “new trend” of having the user manipulating their own data ( or data of their friends / etc .. ) from one application inside another ?

Therefore, there should be an ability to have a list of outside inputs or URL-s which are “trusted” and “accepted” sources in the context of any concrete safety net.

]]>