Talking to Doc earlier this week, I tried to explain my unease with various interpretations of VRM that come thick and fast as the concepts gain traction by identifying the fundamental problem.*
It is the assumption that “the individual needs to be provided for” that I see everywhere other than on the social (or live) web where the demand side can, and often does, supply itself, where users can and often do become creators, where the audiences have become distributors, and intermediaries of all kinds are melting away from decentralised networks and direct connections. Alas, even on the web, it’s not all P2P roses – my online existence is scattered across many platforms, Google, WordPress, Flickr, Dopplr, Twitter, and many more.
Most VRM approaches or implementations I have seen involve a third party as a provider. I believe we first need to focus on changing the relationships between individuals and companies or institutions. First comes redressing the balance – manually, as it were – by helping individuals relate to companies in ways that change companies’ behaviour.
Most of all, I want to avoid using technology to address a non-technology problem, using automation or aggregation for the aspects of relationships which should be processed by a human mind. I want to avoid jumping straight into ‘industrial’ processing of data treasures found on the customer side. We need a more balanced relationships with vendors and institutions, with different tools and possibly rules of interaction. Then we can look at ways to rationalise the technology and processes that help us create and maintain those relationships.
The most common solutions for providing individuals with online services are based around centralised databases or platforms. They are suspect on security and privacy grounds even though they may be created by a trustworthy party. So, any framework or structure provided by a third party that is meant to provide a place for individuals to create, gather, manage and share data as well as allowing a degree of aggregation, connectivity, will have to have in-built checks and balances as it may ultimately expose individuals to potential data-mining (whether the more private among us like it or not!). The challenge is to separate the data storage provider and a services/application provider. If I let someone store or back up my data – reluctantly admitting it may still be necessary for now – I would want them to store my data only, and not push or even provide any other apps based on that data. I should then be able to choose and apply whatever application I want, to my data, at my convenience.
Jason Scott of ASCII has a juicy way of putting this:
This is about your data. This is about your work. This is about you using your time so that you make things and work on things and you trust a location to do “the rest” and guess what, here is what we have learned:
- If you lose your shit, the technogeeks will not help you. They will giggle at you and make fun of your not understanding the fundamental principles and engineering of client-server models. This is kind of like firemen sitting around giggling at you because you weren’t aware of the inherent lightning-strike danger of improperly bonded CSST.
- Since the dawn of time, companies have hired people whose entire job is to tell you everything is all right and you can completely trust them and the company is as stable as a rock, and to do so until they, themselves are fired because the company is out of business.
- You are going to have to sit down and ask yourself some very tough questions because the time where you could get away without asking very tough questions with regard to your online presence and data are gone.
And his advice further into the wonderful rant is even juicier:
- Insult, berate and make fun of any company that offers you something like a “sharing” site that makes you push stuff in that you can’t make copies out of or which you can’t export stuff out of. They will burble about technology issues. They are fucking lying. They might go off further about business models. They are fucking stupid. Make fun of these people, and their shitty little Cloud Cities running on low-grade cooking fat and dreams. They will die and they will take your stuff into the hole. Don’t let them.
…but is no less sound for it!
Please, let’s have more of enabling and less of mere providing.
* as described in the paper A VRM journey.
cross-posted from VRM Hub