Strict Standards: Declaration of UserSettings::get() should be compatible with AbstractSettings::get($col_key1, $col_key2 = NULL, $col_key3 = NULL) in /home/id212/public_html/blog/inc/MODEL/users/_usersettings.class.php on line 202

Strict Standards: Declaration of UserSettings::set() should be compatible with AbstractSettings::set() in /home/id212/public_html/blog/inc/MODEL/users/_usersettings.class.php on line 202

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Creating default object from empty value in /home/id212/public_html/blog/inc/MODEL/settings/_abstractsettings.class.php on line 221

Warning: Cannot modify header information - headers already sent by (output started at /home/id212/public_html/blog/inc/MODEL/users/_usersettings.class.php:202) in /home/id212/public_html/blog/inc/MODEL/sessions/_session.class.php on line 222

Strict Standards: Declaration of Blog::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/id212/public_html/blog/inc/MODEL/collections/_blog.class.php on line 1034

Strict Standards: Declaration of BlogCache::option_list() should be compatible with DataObjectCache::option_list($default = 0, $allow_none = false, $method = 'name') in /home/id212/public_html/blog/inc/MODEL/collections/_blogcache.class.php on line 272

Strict Standards: Declaration of Group::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/id212/public_html/blog/inc/MODEL/users/_group.class.php on line 420

Strict Standards: Declaration of User::dbdelete() should be compatible with DataObject::dbdelete() in /home/id212/public_html/blog/inc/MODEL/users/_user.class.php on line 1145

Strict Standards: Declaration of User::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/id212/public_html/blog/inc/MODEL/users/_user.class.php on line 1145

Strict Standards: Declaration of ResultSel::display_list_start() should be compatible with Results::display_list_start($detect_no_results = true) in /home/id212/public_html/blog/inc/_misc/_resultsel.class.php on line 48

Strict Standards: Declaration of ResultSel::display_list_end() should be compatible with Results::display_list_end($detect_no_results = true) in /home/id212/public_html/blog/inc/_misc/_resultsel.class.php on line 48

Strict Standards: Declaration of Filetype::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/id212/public_html/blog/inc/MODEL/files/_filetype.class.php on line 197

Strict Standards: Declaration of UserCache::option_list() should be compatible with DataObjectCache::option_list($default = 0, $allow_none = false, $method = 'name') in /home/id212/public_html/blog/inc/MODEL/users/_usercache.class.php on line 288

Strict Standards: Declaration of Comment::set() should be compatible with DataObject::set($parname, $parvalue, $make_null = false) in /home/id212/public_html/blog/inc/MODEL/comments/_comment.class.php on line 1164

Notice: Array to string conversion in /home/id212/public_html/blog/inc/_misc/_misc.funcs.php on line 1253

Strict Standards: Declaration of ItemList2::query() should be compatible with Results::query($create_default_cols_if_needed = true, $append_limit = true, $append_order_by = true) in /home/id212/public_html/blog/inc/MODEL/items/_itemlist2.class.php on line 48

Notice: Array to string conversion in /home/id212/public_html/blog/inc/_misc/_misc.funcs.php on line 1253

Notice: Array to string conversion in /home/id212/public_html/blog/inc/_misc/_misc.funcs.php on line 1317

Warning: Cannot modify header information - headers already sent by (output started at /home/id212/public_html/blog/inc/MODEL/users/_usersettings.class.php:202) in /home/id212/public_html/blog/inc/MODEL/skins/_skin.funcs.php on line 71
Security x.0 - Facebook Makes you a Living Dead

Facebook Makes you a Living Dead

05/06/09

Permalink 07:42:01 pm, by Igor Drokov, in User experience, Online identity  

A lot is written on privacy implications of sharing your personal information with different web services. Concerns have been raised about the ownership of information users upload in "the cloud" and it's persistence.

One recent experiment demonstrated that once you have used an online service to share your photos it might be problematic to remove them even when you choose:

My colleagues Jonathan Anderson, Andrew Lewis, Frank Stajano and I ran a small experiment on 16 social-networking, blogging, and photo-sharing web sites and found that most failed to remove image files from their photo servers after they were deleted from the main web site. It’s often feared that once data is uploaded into “the cloud,” it’s impossible to tell how many backup copies may exist and where, and this provides clear proof that content delivery networks are a major problem for data remanence.

Well, maybe deleting a single photo is too small of an operation to expect the site to really make sure it's gone forever. Surely, one would hope that once you de-register your whole account, it will be gone for good?

I have recently tried to close my Facebook account. According to Facebook's privacy policy:

Individuals who wish to deactivate their Facebook account may do so on the My Account page. Removed information may persist in backup copies for a reasonable period of time but will not be generally available to members of Facebook.

OK, I understand purging backup copies is probably asking too much for a user. However, I was surprised to receive the following email after deactivating my account:

You have deactivated your Facebook account. You can reactivate your account at any time by logging into Facebook using your old login email and password. You will be able to use the site like you used to.

Thanks,
The Facebook Team

Indeed, trying to click on the "resurrect" link I found myself back to my profile with all connections and personal information intact.

OK, maybe having a "grace" period for users deactivating their accounts on the spur of the moment is a good feature. So I deactivated my account again and this time left it for almost a month. Yet, today I was able to successfully login to my surely-by-now-non-existent account and found all my connections and information intact as it was...

Welcome to the Hotel California 2.0:

"You can checkout any time you like, But you can never leave!"

Pingbacks:

No Pingbacks for this post yet...

This post has 4 feedbacks awaiting moderation...

About

Securing personal financial transactions online and all that comes with it: trojans and man-in-the-browser, e-banking and e-commerce, usability and scalability. By Igor Drokov, Elena Punskaya et al. at Cronto - the inventor of Visual Transaction Signing.

Search


Strict Standards: Declaration of ArchiveList::count_total_rows() should be compatible with Results::count_total_rows($sql_count = NULL) in /home/id212/public_html/blog/plugins/_archives.plugin.php on line 544