{"id":13883,"date":"2017-01-23T09:00:02","date_gmt":"2017-01-23T14:00:02","guid":{"rendered":"https:\/\/www.kaspersky.co.za\/blog\/?p=13883"},"modified":"2019-11-15T13:45:10","modified_gmt":"2019-11-15T11:45:10","slug":"ffforget-or-not-ffforget","status":"publish","type":"post","link":"https:\/\/www.kaspersky.co.za\/blog\/ffforget-or-not-ffforget\/13883\/","title":{"rendered":"To FFForget or not to FFForget, that is the question"},"content":{"rendered":"<p>Hi, my name is Serge, and I just realized that I have been an active Internet user for 20 years. Seriously, this year I should celebrate an anniversary, but instead I will tell you a couple of personal stories: stories of unexpected Internet twists I have experienced.<\/p>\n<p>Since the early 90s, the Internet has been a platform for social interactions \u2014 although they were not always convenient or easy to carry out. Sometimes \u201csocializing\u201d required users to find, install, and set up certain apps like a newsgroup reader or even to master a \u201cprogramming\u201d language. You might remember one early Internet trend, which was to create so-called <em>home pages<\/em> that effectively served as public user profiles. They often were ugly, and people shared a lot of irrelevant things about themselves via those pages.<\/p>\n<p>However, those home pages were one of a very few ways to get to know your virtual friends better. To publish such a page, you would have signed up with a <em>free home page provider<\/em>. Some of the more famous ones were Geocities and Xoom. You probably haven\u2019t heard of those, and there is a good reason for that: Both collapsed after the first dot-com bubble burst in the early 2000s. I had a home page on both, and the only reason I can show you a screenshot today is that I bothered to back up those pages on my hard drive.<\/p>\n<p><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/103\/2017\/01\/06020958\/ffforget-sym-homepage.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/103\/2017\/01\/06020958\/ffforget-sym-homepage.png\" alt=\"Some of the more famous ones were Geocities and Xoom.\" width=\"785\" height=\"455\" class=\"aligncenter size-full wp-image-13885\"><\/a><\/p>\n<p>In other circumstances, this delightful story of my early Internet life could have vanished completely. But the lesson about services coming and going is still relevant. Take Twitter \u2014 the company recently <a href=\"http:\/\/variety.com\/2017\/digital\/news\/twitter-vine-shut-down-1201961620\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">shut down its video-related spin-off Vine<\/a>. The shutdown was announced several months in advance, so content creators had time to do what I did years ago \u2014 download or move their creations elsewhere.<\/p>\n<p>Obviously, this issue is particularly important for artistic people (<a href=\"http:\/\/boingboing.net\/2016\/02\/26\/a-copyright-troll.html\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">cutting them off from their own creations can be brutal<\/a> \u2014 or <a href=\"https:\/\/blog.vellumatlanta.com\/2016\/05\/04\/apple-stole-my-music-no-seriously\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">very brutal<\/a>). But even if what you create is something as simple as your vacation photos or a compilation of funny things your children said, you probably want to make sure those creations won\u2019t vanish if, say, Facebook decides to go out of business in a few years.<\/p>\n<p>But let\u2019s get back to my early Internet life. Fast-forward five years and everyone is fond of <em>blogs<\/em>. Tech-savvy people create stand-alone sites for their blogs; however, the easiest way to start your own blog is to create an account on a dedicated blogging site. I selected a popular-back-then service called LiveJournal and spent a few years writing book\/movie\/restaurant reviews for a few dozens of my friends and colleagues.<\/p>\n<p>LiveJournal undertook a few significant transformations, and it\u2019s not that popular nowadays; however, it still exists and works in more or less the same way. Despite that, you won\u2019t be able to read my older posts on the platform because one day in late 2000s I used LiveJournal\u2019s convenient bulk-editing interface to set all of my posts\u2019 visibility to \u201cfriends-only.\u201d<\/p>\n<p>So unless you\u2019re one of my very old LJ friends, you can\u2019t see that content anymore. I restricted viewing after realizing that a completely unintended audience was reading and reacting to my posts. It varied wildly, from new business partners to strangers who apparently admired my ramblings, but they had one thing in common: I didn\u2019t want to interact with them in the context of my old, personal blog. This lesson was not a hard one \u2014 there was no reputational or other damage \u2014 but it could be different for some people. Serious threats or bullying over a single tweet are not uncommon nowadays, and heated arguments and breakups over a partner\u2019s social media actions <a href=\"https:\/\/www.kaspersky.co.za\/blog\/likeaholism\/13873\/\" target=\"_blank\" rel=\"noopener noreferrer\">happen as well<\/a>.<\/p>\n<blockquote class=\"twitter-tweet\" data-width=\"500\" data-dnt=\"true\">\n<p lang=\"en\" dir=\"ltr\">Who owns your <a href=\"https:\/\/twitter.com\/hashtag\/digital?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#digital<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/memories?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#memories<\/a>? Is there a way for the answer to be YOU? <a href=\"https:\/\/t.co\/3h25qAM8hq\" target=\"_blank\" rel=\"noopener nofollow\">https:\/\/t.co\/3h25qAM8hq<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/SocMe?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#SocMe<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/SocialMedia?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#SocialMedia<\/a> <a href=\"https:\/\/twitter.com\/hashtag\/SMM?src=hash&amp;ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">#SMM<\/a> <a href=\"https:\/\/t.co\/HG5eMOgPkT\" target=\"_blank\" rel=\"noopener nofollow\">pic.twitter.com\/HG5eMOgPkT<\/a><\/p>\n<p>\u2014 Kaspersky (@kaspersky) <a href=\"https:\/\/twitter.com\/kaspersky\/status\/812048987842809856?ref_src=twsrc%5Etfw\" target=\"_blank\" rel=\"noopener nofollow\">December 22, 2016<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Sometimes the repercussions are just too much for a person to tolerate, and the best course of action might seem to be either total isolation of the social media account or even its complete removal. However, the account may contain sentimental memories (as with my blog, for example), so before actually deleting anything, you should obtain a copy. With LiveJournal circa 2008, by the way, it was ridiculously complex. A special geeky app was required, and getting it working was a tech task a notch above average. For the record, I did it, and now I have a LJ blog backup just in case the service follows in Geocities\u2019 footsteps.<\/p>\n<div class=\"pullquote\">Trying to keep chat histories backed up, up-to-date, and private is very important<\/div>\n<p>Nowadays, I don\u2019t spend much time on social media \u2014 at least for personal amusement. My postings are rare and brief, and honestly, I don\u2019t value them all that much. My messenger chats, however, are a completely different story. Starting with ICQ and up through Whatsapp and the rest of today\u2019s cohort, chats tell the story of my life, love, work, and everything else. So trying to keep chat histories backed up, up-to-date, and private is very important. I am willing to spend money to have this problem solved efficiently. At the moment, a bunch of solutions are on the market; however, each backs up only one social network.<\/p>\n<p>That\u2019s how the idea of a service that allows users to back up all of their social content at once emerged. Such a service would have to keep the backup encrypted in local or cloud storage as well. The beta version of our social backup will be available soon. Although for now it will be limited to local storage, not cloud, and a limited set of social networks from which it can fetch content, the service will develop further in line with users\u2019 demands. You can learn more and subscribe for early beta access at <a href=\"http:\/\/ffforget.me\/\" target=\"_blank\" rel=\"noopener noreferrer nofollow\">ffforget.me<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When web services collapse, they bury users\u2019 data under their ruins. How can we solve this problem?<\/p>\n","protected":false},"author":32,"featured_media":13884,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1788,2671],"tags":[1874,43,211,1916,1915],"class_list":{"0":"post-13883","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-privacy","8":"category-special-projects","9":"tag-ffforget","10":"tag-privacy","11":"tag-social-media","12":"tag-users-data","13":"tag-web-services"},"hreflang":[{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/ffforget-or-not-ffforget\/13883\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/ffforget-or-not-ffforget\/5842\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/ffforget-or-not-ffforget\/4078\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/ffforget-or-not-ffforget\/10713\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/ffforget-or-not-ffforget\/8836\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/ffforget-or-not-ffforget\/9912\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/ffforget-or-not-ffforget\/9659\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/ffforget-or-not-ffforget\/14003\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/ffforget-or-not-ffforget\/2902\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/ffforget-or-not-ffforget\/13883\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/ffforget-or-not-ffforget\/7087\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/ffforget-or-not-ffforget\/6082\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/ffforget-or-not-ffforget\/14003\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/ffforget-or-not-ffforget\/13883\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.co.za\/blog\/tag\/privacy\/","name":"privacy"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/13883","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/users\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/comments?post=13883"}],"version-history":[{"count":2,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/13883\/revisions"}],"predecessor-version":[{"id":24181,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/posts\/13883\/revisions\/24181"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/media\/13884"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/media?parent=13883"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/categories?post=13883"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.co.za\/blog\/wp-json\/wp\/v2\/tags?post=13883"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}