Sure, people want different facets of themselves on different apps/platforms. But those apps/platforms get <i>bought and sold</i> along with the content and the facet of yourself that you put there.<p>Ergo, I disagree that we don't have a problem. It's just in a different form and involves the business models both companies and users have become used to (e.g free, ad-supported, etc). For the moment, there are still no viable systems people could move to so they just have to deal with what they get (or disengage).
There is data and there are views.<p>Self-expression in a particular app doesn't mean that you shouldn't have control over the underlying data you publish, and easily transfer it between apps. Already, many apps such as Tinder ask for your FB account and import your photos. But the import is still limited, and hardly any information is contributed back.<p>Just like MVC separates data, from views, so too the "apps" should take your data from one place which you control. This place shouldn't be a centralized social network, it should be an open-source server.<p>In this way, people can upload and manage their own videos, photos, and more. They can then give access to others (friends, etc.) as well as to apps (via OAuth) through their own server. If some of their data streams (e.g. a blog or a video) become popular, then the person pays for more hosting.<p>The age of centralized services that can go down and present juicy targets to the NSA is temporary. Just like open source systems like git and mercurial disrupted centralized version control systems, so too will the centralized web services eventually be disrupted. The web was originally meant to be decentralized, and it will be again.<p>Disclaimer: My company, Qbix, has been building the underlying (open source) platform for this exact thing in the last 3 years. And we have had to deal with a lot of issues surrounding identity, privacy, and individual control. Here are some links:<p><a href="http://magarshak.com/blog/?p=135" rel="nofollow">http://magarshak.com/blog/?p=135</a><p><a href="http://magarshak.com/blog/?p=114" rel="nofollow">http://magarshak.com/blog/?p=114</a>