News for hackers. Stuff that matters.
Re:Facebook is for grandparents: What we need in a next-gen ... by voltagex_ on Monday November 25, 2013 @12:45AM (#6792713)
Does this mean I'm going to have to rescue my data every time a software/network is "retired"?
Re:Facebook is for grandparents: What we need in a next-gen ... by tombrossman on Monday November 25, 2013 @03:56AM (#6793127)
Rather than rescuing your data, start publishing to your own platform and syndicating content out to whichever silos become popular.

This is the idea behind 'Indie Web' [1] and even though it is harder at first it is the simplest long-term solution. Domain names are cheap, hosting is cheap, and publishing isn't very difficult.

[http://indiewebcamp.com/why]

Re:Facebook is for grandparents: What we need in a next-gen ... by personlurking on Monday November 25, 2013 @02:17AM (#6792912)
'Rescue' might be the wrong word here. A simple transfer, or updated 'address' form would seem more likely. Like when you want to delete a WP blog, it gives you several options for your content/blog (though most imply not owning it anymore).
Re:Facebook is for grandparents: What we need in a next-gen ... by voltagex_ on Monday November 25, 2013 @06:53PM (#6798003)
That assumes the services you're moving between are based on any kind of standard. Try moving your Facebook data to Google+ and see how far you get.
Re:Facebook is for grandparents: What we need in a next-gen ... by 72deluxe on Monday November 25, 2013 @04:15AM (#6793178)
I suppose this highlights the problem with a third-party owned and run system - you don't own your data! You are at the mercy of the third party for data that you put there and believe are owed.
Re:Facebook is for grandparents: What we need in a next-gen ... by coldtea on Monday November 25, 2013 @04:39AM (#6793231)
Of course. Or rather, that you'll learn that the more important data, you publish on your own, and everything else is transient.