in Technology

3 principles for a more Open approach.

This exchange on Google+ with Rob Poulter (referencing my previous post on platforms and standards) got me thinking. The highlights are below.

Rob:

Ultimately I don’t think the problem is between native vs web, the problem is one of closed vs open, and not in a Google PR way. The things we tend to care about in the online world are services, not apps. Services see us passing responsibility for our data on to a third party, and usually based on features rather than interoperability or longevity. At the end of the day, if there’s something which we would mind losing, it’s our responsibility to keep it, not some third party.

Doug:

My issue, I suppose is platforms becoming de facto standards because ‘everyone uses them’. Kind of like Dropbox and Twitter and so on…

There’s definitely an elision which I need to resolve in my thinking between ‘HTML5 webapps’ and ‘openness’. Thanks for the pointers!

Rob:

The standards thing is tough I guess. Who wants to be the business that boasts of how easy it is to jump ship? Especially for social applications like Twitter, Facebook, G+ etc (Dropbox and other personal services not so much since they tend to compete on features and can’t rely on “hey, all your friends are here, you’re not going anywhere”).

I pointed out that Google Takeout actually does allow you to export your data from Google to other platforms. But, as Rob responded, not the comments on other people’s posts.

All of this made me think about my principles for using software and web services. It reminded me of Baltasar Gracian’s constant reminders in The Art of Worldly Wisdom (which I read on constant repeat) that it’s easy to begin well, but it’s the ending well that counts.

So, I’ve come up three principles to guide me:

  1. I will use free and Open Source software wherever possible. (I’m after the sustainable part of OSS, not the ‘free’ part)
  2. If this is not possible then I will look for services which have a paid-for ‘full-fat’ offering.
  3. I will only use proprietary services and platforms without a paid-for option if not doing so would have a significant effect on my ability to connect with other people.

What’s in and what’s out? I’ll stick with Twitter and Google+ (but will try to connect with people I follow in additional ways). Evernote, Spotify, Skype and Dropbox are fine for the time being (I pay for them). I’ll try and move away from GMail and Google Calendar.

Any suggestions for replacements?

 

  • http://boone.gorg.es/ Boone Gorges

    > But, as Rob responded, not the comments on other people’s posts

    IMO this points to a fundamental problem with the concept of content ownership in the context of digital networks. If I leave a comment here on Doug’s blog (or, more appropriately, his G+ profile), in what sense do I still own it at all, such that there’s a moral imperative that it be exportable? I tend to think of comments as a kind of gift to the author – I no longer claim control over that content.

    More generally, I think your principles make a lot of sense as a decision tree for reliance on software/services that may not be totally free. Though I do have a nit to pick with this:

    > I’m after the sustainable part of OSS, not the ‘free’ part

    The ‘free’ in ‘free software’ is free-as-in-speech (libre), not free-as-in-beer (gratuit). I would argue that this kind of freedom in standards/software is more fundamental than the ‘open source’ aspect. ‘Open source’ emphasizes the availability of source code. But ‘Free’ stresses the freedom to modify this source, and the freedom to use the software as one will. Openness, in this sense, wouldn’t be valuable without the corresponding freedom. See RMS https://www.gnu.org/philosophy/open-source-misses-the-point.html 

  • http://dougbelshaw.com/ Doug Belshaw

    Hi Boone, and thanks for the comment.

    I’m absolutely in agreement with you on the ‘free’ point and often reference’s Miles Berry’s stuff on the ‘four freedoms’: http://milesberry.net/2009/04/why-schools-should-use-open-source-software/
    The trouble is, using the same word in four different ways is kind of confusing. I wanted to be clear to my a general audience (which made it less clear to another audience, sorry).

  • Pingback: Getting a Kik Messenger Account – and Assessing Risks and Benefits « UK Web Focus