Category Archives: Twitter

Bean Counters and Ecologists

[So many things in my drafts, but this one should be quick.]

Recently met someone who started describing their restaurant after calling it a “café”. The “pitch” revolved around ethical practices, using local products, etc. As both a coffee geek and ethnographer, my simple question was: “Which coffee do you use?” Turns out, they’re importing coffee from a multinational corporation. “Oh, but, they’re lending us an expensive espresso machine for free! And they have fair-trade coffee!”

Luckily, we didn’t start talking about “fair trade”. And this person was willing to reflect upon the practices involved, including about the analogy with Anheuser-Busch or Coca-Cola. We didn’t get further into the deeper consequences of the resto’s actions, but the “seed” has been planted.

Sure, it’s important to focus on your financials and there’s nothing preventing a business from being both socially responsible and profitable. It just requires a shift in mindset. Small, lean, nimble businesses are more likely to do it than big, multinational corporate empires…

…which leads me to Google.

Over the years since its IPO, Google has attracted its share of praise and criticism. Like any big, multinational corporate empire. In any sector.

Within the tech sector, the Goog‘ is often compared with Microsoft, Facebook, Twitter, and Apple. All of these corporate entities have been associated in some people’s minds with some specific issue, from child labour and failure to protect users’ privacy to anticompetitive practices (the tech equivalent of free fridges and espresso machines). The issues are distinct and tech enthusiast spend a large amount of time discussing which one is worse. Meanwhile, we’re forgetting a number of larger issues.

Twitter is an interesting example, here. The service took its value from being at the centre of an ecosystem. As with any ecosystem, numerous interactions among many different members produce unexpected and often remarkable results. As the story goes, elements like hashtags and “@-replies” were invented by users and became an important part of the system. Third-party developers were instrumental in Twitter’s reach outside of its original confines. Though most of the original actors have since left the company, the ecosystem has maintained itself over the years.

When Twitter started changing the rules concerning its API, it shook the ecosystem. Sure, the ecosystem will maintain itself, in the end. But it’s nearly impossible to predict how it will change. For people at Twitter, it must have been obvious that the first changes was a warning shot to scare away those they didn’t want in their ecosystem. But, to this day, there are people who depend on Twitter, one way or another.

Google Reader offers an interesting case. The decision to kill it might have been myopic and its death might have a domino effect.

The warning shot was ambiguous, but the “writing was on the wall”. Among potential consequences of the move, the death of RSS readers was to be expected. One might also expect users of feedreaders to be displeased. In the end, the ecosystem will maintain itself.

Chances are, feedreading will be even more marginalized than it’s been and something else might replace it. Already, many people have been switching from feedreading to using Twitter as a way to gather news items.

What’s not so well-understood is the set of indirect consequences, further down the line. Again, domino effect. Some dominoes are falling in the direction of news outlets which have been slow to adapt to the ways people create and “consume” news items. Though their ad-driven models may sound similar to Google’s, and though feedreading might not be a significant source of direct revenue, the death of feedreaders may give way to the birth of new models for news production and “consumption” which might destabilize them even further. Among the things I tag as #FoJ (“Future of Journalism”) are several pieces of a big puzzle which seems misunderstood by news organizations.

There are other big dominoes which might fall from the death of Google Reader. Partly because RSS itself is part of a whole ecosystem. Dave Winer and Aaron Swartz have been major actors in the technical specifications of RSS. But Chris Lydon and people building on calendar syndication are also part of the ecosystem. In business-speak, you might call them “stakeholders”. But thinking about the ecosystem itself leads to a deeper set of thoughts, beyond the individuals involved. In the aftermath of Aaron Swartz’s premature death, it may be appropriate to point out that the ecosystem is more than the sum of its parts.

As I said on a service owned by another widely-criticized corporate empire:

Many of us keep saying that Google needs to listen to its social scientists. It also needs to understand ecology.

Retour à Facebook?

Maintenant que Twitter commence à franchement m’énerver, je risque d’utiliser Facebook plus activement.

D’ailleurs, ça fait longtemps que je pense à repenser mes activités dans les médias sociaux. J’ai eu une passe un peu trop “broadcast”. J’aimerais être plus «interactif».

Faut dire que, comme la plupart des gens que je connais, je blogue presque plus. Twitter avait pris le relai, d’une certaine façon, mais seulement dans une direction. Finalement, après plusieurs années, je me rends compte que j’ai peu d’interactions sur Twitter. Sur mon compte principal, du moins.

Ce qui m’a fait remarquer tout ça, en fait, c’est d’être presque forcé de me concentrer sur une plateforme à la fois. Jusqu’à tout récemment, j’avais l’habitude d’envoyer les mêmes trucs sur plusieurs plateformes (Facebook, StatusNet, Twitter, Tumblr, LinkedIn…). Je sais bien que plusieurs personnes détestent le “crossposting”, mais c’était permis et ça me convenait.

J’utilisais le service Ping.fm, qui rendait la tâche très facile. Entre autres, il me permettait de distinguer entre des «mises à jour de statut» (“status updates”) d’envois de «microblogue». La différence était subtile et n’apparaissait pas sur toutes les plateformes, mais je la trouvais utile. Comme plusieurs le savent, mes «statuts» sont généralement bilingues, accordant une valeur particulière à la version française. C’était tout bête, comme truc, mais ça fonctionnait pour moi.

Malheureusement, Ping.fm a été acheté par Seesmic qui a été acheté par HootSuite. Par ces rachats, certaines limites ont été imposées et certaines fonctionnalités ont disparu. J’avais l’habitude d’envoyer mes trucs à plusieurs endroits à la fois, mais ça devient plus difficile à faire. Ceux qui détestent le “crossposting” seront peut-être satisfaits, mais ça m’embête un peu.

En même temps, c’est devenu plus facile de partager sur une plateforme donnée à la fois. Entre autres grâce au support natif dans OS X comme dans iOS et Android. Plusieurs «contenus» (liens et images, surtout) peuvent être envoyés directement à Facebook ou Twitter sans quitter l’application en cours d’utilisation. Pas mal. Mais ça ne facilite pas l’envoi simultané à Twitter et Facebook. Ou l’envoi sur StatusNet, Tumblr, LinkedIn, etc.

Je pensais donc à me réinvestir sur une autre plateforme.

Pourquoi Facebook? En fait, c’est pour une raison très simple: c’est sur Facebook que j’ai le plus d’interaction. Au-delà de tous les principes et de toutes les questions techniques, c’est ce qui compte le plus, pour moi. Si je suis honnête avec moi-même.

Pendant des années, j’ai essayé d’avoir le plus d’interactions possibles sur diverses plateformes. On peut dire que ma méthode était moins qu’adéquate pour toutes sortes de raisons, mais j’essayais quand même, à ma façon. La leçon que j’aurais peut-être dû apprendre, en envoyant les mêmes choses sur différentes plateformes, c’est qu’une seule d’entre ces plateformes devrait me suffire. Et c’est peut-être dommage mais cette plateforme semble être Facebook.

Pas que je vais abandonner les autres plateformes. Mais elles auront probablement un rôle différent, pour moi. Honnêtement, je suis pas certain quel rôle jouera chacune de ces plateformes. On verra à l’usage.

D’ailleurs, ç’a toujours été ma philosophie, avec mes comptes personnels: j’expérimente, je m’amuse et je vois ce qui reste. Assez différent avec des comptes organisationnels ou professionnels. Mais l’idée de base est que mon usage personnel me donne une expérience qui est utile dans le reste de ma vie.

D’ailleurs, mon compte @iethnographer sur Twitter remplit bien sa fonction. Je l’utilise peu mais, quand je l’utilise, ça «fonctionne». Pas que ça démarre des longues discussions, mais ça me permet d’avoir des interactions ciblées. C’est tout ce que je veux. D’ailleurs, les abonnés de ce compte sont généralement des gens ou des groupes avec qui j’ai des intérêts en commun. Sur mon compte perso, j’ai accumulé pas mal d’abonnés qui ont surtout un intérêt pour les médias sociaux, souvent pour des buts un peu douteux. J’ai moins de nouveaux abonnés de ce type, mais je peux pas dire que j’ai réseau bien ciblé, sur mon principal compte Twitter. Évidemment, j’aurais pu éviter cette situation, si j’avais dédié mon compte à un sujet spécifique ou si j’avais pris soin de suivre des gens avec qui j’ai des intérêts communs. J’ai fait un peu de ça de 2007 à 2008 mais, depuis, c’est devenu plus difficile.

Qu’en est-il des autres plateformes? Je vais probablement continuer à les utiliser, à l’occasion, mais je crois que c’est le moment pour moi de me «regrouper». À une certaine époque (jusqu’en 2010, disons), j’accumulais des comptes sur toutes les plateformes possibles et imaginables. Pas que je m’investissais outremesure, mais j’essayais un peu tout, je sautais dans le «chariot» (le “bandwagon”). En présentation (à PodCamp, par exemple), j’avais tendance à dire qu’on pouvait me trouver sur n’importe quelle plateforme et j’invitais les gens à me faire signe s’ils étaient sur une plateforme où je n’avais pas de présence.

Depuis environ deux ans, j’ai cessé d’ouvrir des compte sur chaque nouvelle plateforme. Pas que c’était une décision consciente de me concentrer sur celles que j’utilisais déjà. Mais j’ai arrêté de «sauter dans le train en marche». Ainsi, je n’ai pas de compte sur Pinterest, Path, App.net ou Instagram. Et je sous-utilise certains des comptes que j’ai ouverts (Branch, Diaspora, Academia.edu, Quora…). Dans le fond, j’ai pas besoin de grand-chose, pour mon usage personnel. Même pour expérimenter.

Certaines des plateformes que j’utilisais ont disparu. D’ailleurs, ce qui s’est passé avec Google Wave a eu un drôle d’effet sur moi. J’avais espoir que ça puisse devenir quelque-chose de formidable. J’ai été si amèrement déçu que ma perception de Google a pris une nouvelle tournure. D’ailleurs, parlant de Google, leur acquisition et destruction d’Aardvark (vark.com) m’a aussi perturbé. Dans toute sa simplicité, ‘Vark était devenu une super plateforme, pour moi. Si ça peut paraître bête pour certains (surtout ceux qui croient que Quora et Stack Overflow peuvent remplir les mêmes fonctions), j’ai perdu quelque-chose quand Google a étouffé l’Aardvark dans l’œuf.

Et ne parlons pas de Google Buzz.

Mais un mot quand même au sujet de Google+, qui peut être ou devenir la principale plateforme de médias sociaux, pour certains…

En fait, ces derniers temps, j’ai pensé à me concentrer sur Google+ plutôt que sur Facebook ou d’autres plateformes. Un avantage, c’est que c’est une plateforme assez polyvalente, puisqu’on peut y partager toutes sortes de choses. Puisque je dispose d’un Nexus 7, ça pourrait devenir ma plateforme privilégiée. C’est peut-être même ce qui va se passer, après un certain temps. Mais probablement pas pour le moment.

Le principal problème que j’ai, avec Google+, c’est que j’aurais besoin de m’y investir à fond pour en retirer quelque-chose d’intéressant. Pas que j’y ai pas de contacts. En fait, je suis dans plus de cercles G+ que je n’ai d’«amis» sur Facebook. Mais ces contacts G+ demandent un autre type d’attention que ce que je suis disposé à accorder. Et, j’insiste, c’est une question qualitative, pas quantitative. Je parle pas d’un effort accru mais d’un effort distinct.

Parce qu’utiliser G+, pour moi, ça entre pas dans ma routine.

Pas que ce que j’y envoie tombe dans le vide. Proportionnellement, j’y reçois presqu’autant de retours que sur mon compte Twitter personnel. Et ces interactions sont tout-à-fait valables, dans le contexte. Mais elles sont d’un certain type, lié à ceux de mes contacts qui participent à une certaine sphère technologique. Pour rendre la plateforme vraiment satisfaisante, ça me demanderait un boulot de fond. Je devrais changer ma façon de procéder, provoquer de nouveaux types d’interactions, me lier à des gens qui partagent d’autres types d’intérêts, «produire du contenu» d’un certain type, etc.

Faut dire qu’il manque certains trucs, à Google+ (qui a pourtant fait son apparition il y a un an et demi). Par exemple, je peux pas envoyer des trucs sur G+ à partir d’autres plateformes, y compris WordPress et Foursquare. Je peux archiver mes envois grâce à ThinkUp, mais ça demeure bien limité. Pas vraiment de façon d’explorer les recoins de mon réseau social au-delà du premier degré. Pas vraiment de «groupes de discussion», non plus. Et les profils sont aussi limités que ceux de Google Profiles.

En disant tout ça, je continue à réfléchir (c’est un peu pour ça que j’écris). Peut-être que G+ deviendra bientôt ma plateforme de choix, surtout si j’arrive à me convaincre que les obstacles sont «dans ma tête». Un peu comme ma décision de «donner une chance à Android» (plutôt insatisfaisant), j’essaie non seulement de garder l’esprit ouvert mais de faire quelques efforts vers d’autres façons de fonctionner.

Un problème particulier, c’est que Google+ m’inspire pas. Je vois mal ce que ça peut devenir. J’y vois pas d’avantage majeur par rapport à Twitter et Facebook, malgré la réputation de Google dans certains de mes cercles d’amis. Bien que je sois sensible au discours sur l’ouverture et que le comportement corporatif de Facebook et Twitter puisse laisser à désirer, j’ai encore rien vu dans Google+ qui peut ouvrir des nouvelles possibilités, pour moi. Et les beaux principes qui semblent avantager Google dans les yeux de certains n’ont que peu de valeur à mes yeux quand ils sont associés à une entreprise qui, à la fois, accorde si peu d’importance à l’être humain et se concentre tellement sur la publicité.

En passant, je comprends bien que G+ est bien plus qu’une plateforme de média social. Mais je pense ici à mes activités dans les médias sociaux, pas aux objectifs que Google s’est fixé. Je trouve que l’engin de recherche Google continue à se détériorer et G+ n’a pas eu d’effet bien positif de ce côté. Je pense même qu’il y a une méprise fondamentale sur le type d’activité qui rend les médias sociaux si intéressants.

Ce qui me pousse à concentrer certaines de mes activités de médias sociaux sur Facebook.

Depuis sept ans que je suis sur Facebook, j’ai pu observer beaucoup de changements. Plusieurs de ces changements ont un effet négatif sur l’expérience générale de la plateforme. Mais certains sont assez utiles, pour moi.

En 2005, mes seuls contacts Facebook étaient quelques-uns des étudiants avec lesquels j’étais en contact, aux États-Unis, y compris certains de ceux qui suivaient mes cours, à Bridgewater. Par la suite, j’ai eu quelques contacts Facebook dans des universités canadiennes. Mais c’est seulement  au moment où la plateforme a été ouverte à tout le monde que mon réseau sur Facebook a pris son sens.

Il y a aussi eu la période des applications. Plusieurs d’entre elles causaient plus de frustration que de nouveaux usages, mais elles ont poussé les gens à investir plus de temps sur Facebook, ce qui a eu certains effets intéressants sur l’utilisation de la plateforme. Ce que plusieurs ont bien compris, c’est qu’une fois que les gens sont sur une plateforme, ils risquent d’y passer plus de temps. Même avant les jeux sur Facebook (Spymaster, d’abord, puis FarmVille et autres phénomènes de masse), les applications ont eu pour effet d’asseoir la plateforme sur une base plus solide.

Dans les autres développements plutôt utiles, il y a eu l’ajout de «flux d’actualités» (“newsfeeds”) et l’amélioration du système de messagerie. J’ai jamais été très fort sur le clavardage alors le système hybride que Facebook propose tend à me convenir relativement bien.

Évidemment, il y a des tas de trucs qui me fatiguent, avec Facebook. Mais, finalement, c’est moins problématique que ça l’était, à une certaine époque.

Donc, on verra bien ce qui va se passer. Disons simplement que je vais retourner à Facebook avec un esprit ouvert.

 

iCloud Dreams

Got lots more to blog, including something about “received knowledge”. And a list of things I love about Google. (I’m also getting started on “logical punctuation”, as you may already be noticing…)

But, at the risk of attracting trolls and Apple haters, I thought I’d post some notes from a daydreaming session. In some ways, it’s easier to write than the rest. And it’s more “time-sensitive”, in that my thoughts will likely sound very silly, very soon.

But I don’t care.

So, yes, this post is about iCloud, which will be officially unveiled in a few hours. No, it doesn’t mean that I expect anything specific from iCloud or that I trust Apple to deliver something awesome.

Contrary to what some people seem to think, I’m no Apple fanboi. I use a number of Apple products and I find several of them to be close to the ideal in my workflow, but I don’t have any sort of deep involvement in “the Cult of Mac”, Apple Inc., AAPL, or even Apple-focused development. I use the tools and like them, but I don’t think Apple will save us any more than will Facebook, Dell, Google, Amazon, Twitter, HP, or Microsoft.

[Automattic, on the other hand;-) ]

So, back to iCloud…

According to many, “cloud computing” (whatever that means) is a domain in which Apple has been relatively weak. I tend to share that opinion, despite the fact that a number of tools that I use have to do with either “the cloud”, Apple, or both. What might give trolls and haters some ammo is that I do have a MobileMe subscription. But there’s a lot I dislike about it and the only features I really find valuable are “over-the-air” syncing (henceforth “OTA”) and “Find My iPhone”. And since I use GSync on my iPod touch, MobileMe’s OTA isn’t that incredibly important. Depending on what iCloud may be, my MobileMe renewal (which comes up in a few days) could be a very hard sell. I don’t regret having it as it did help me retrieve my iPad. But it’s rather expensive if it’s the only thing it does. (Then again, so is insurance of any kind, but I digress…)

So, I’m no MobileMe poweruser. Why would I care about iCloud?

In some ways, I don’t. Or, at least, I didn’t. Until very recently, though I saw rumours about Apple’s new “cloud services”, I was only vaguely intrigued about it. I did think that it might solve my MobileMe issue. But I treated these rumours with a lot of skepticism and a rather low level of interest.

Yet, today, iCloud has been giving me a drift-off moment. Like Android did, at some point.

It’s not that I have predictions to make about iCloud. I’m not even speculating, really. But it got me to think. And, I admit, I enjoy thinking.

Without further ado (about nothing), my fanciful thoughts stemming from a short daydreaming session about iCloud…

The main thing people seem to be expecting  (based on rumoured negotiations with music publishers) is a music streaming service similar to Music Beta by Google or a digital file storage service similar to Amazon Cloud Drive. Both of these are quite neat and I could see myself using something like this. But it’s not exactly what makes me dream. While iTunes integration might make Apple’s version of a music streaming service somewhat more useful than the others. Besides, rumours have it that, through agreements with the recording industry, iCloud might sync music without requiring long uploads. It’s quite possible that this only works with tracks purchased on iTunes, which would upset those whose expectations are high, but could already be useful to some.

Where I’m beginning to drift off, though, is when I start thinking about OTA for podcasts. It’s been high up on my wishlist, as a feature, and you might say that it’s a pet peeve with iOS devices for podcatching. Having to sync my iPod touch to my main desktop just to have my podcast list up-to-date is a major hassle. Sure, there are apps which sync podcasts OTA. Problem is, they can’t add podcasts to the native iOS media player, which is a dealbreaker in my case. (As absurd as it may sound to others, one reason this is a dealbreaker is that I now listen to everything at doublespeed. Hey, it’s my podcast library and I listen to it as I want, ok?)

So, OTA podcasts would constitute a significant enhancement to my experience. Nothing absolutely required and possibly not that significant for others, but it’d really help me in more ways than one could imagine.

Thing is, syncing my iPod touch isn’t just about podcasts, even though podcatching is my main motivation to sync. After all, I don’t listen to podcasts yet I still sync my iPad. So, what else? Well, backing up is the main other thing, and it might be one of the core reason for Apple’s implicit insistence on syncing. That’d be classic Apple. Data loss can be such a big problem that they’d “do what they can” to prevent users from losing data. Far from perfect, in my experience (I ended up having some problems when I lost my “iTunes Library” file). And quite annoying when it meant that the sync would take a very long time to finish at precisely the point when I’m trying to leave home. But a classic Apple move, even in the way Apple haters may mean it.

So OTA synchronization of the whole iOS device, and not just podcasts or music, would be a definite plus, in this perspective. If it does end up coming with iCloud, it’d provide support to the idea that the tethering of iOS devices to desktop computers is really about ensuring that users back up their devices…

…and stay up to date. Firmware updates aren’t that frequent, but they’re probably a major part of the equation for Apple.

But not so much for me. If OTA podcasts were available, I’d still sync my iOS devices on occasion, through whatever means necessary. In fact, were I to use an Android device, a backup app would be essential, to me. So still not much dreaming from the backup aspect of iCloud.

Although… Sync is much broader than preventing device-specific data loss and making sure your device has the latest firmware.

For one thing, it does encompass some of the aforementioned OTA functionalities in MobileMe. Useful, but still not dreamworthy.

We get a bit closer to a “dream come true” if we talk about Xmarks, a bookmark-sync service originally meant for Firefox.  Sure, it sounds incredibly prosaic. But OTA bookmarks would open up a wide range of possibilities. This is about a qualitative difference from going OTA. In the case of backups, it’s about avoiding an annoyance but, arguably, it’s not really about changing something major about our behaviour. (Then again, maybe it is, with people who don’t back their devices up.) Point is, with something as simple as bookmarks, OTA is “disruptive”. At least, it gets me to daydream. One reason is that:

…no matter how fundamental they have been for the Web, links and bookmarks have yet to find their full value.

Hmm… Ok, perhaps a bit hyperbolic… So let me rephrase…

There’s still a lot to be done with URLs and, as simple as they are, I love thinking about links. Maybe I’m just obsessed with URLs.

As it so happens, I have a full list of thoughts about “link processing” and I’ve already blogged about related topics (on more than one occasion, in different contexts, going back to relatively early blogposts). And I even think social science can help.

I mean, think about it! There’s so much you can do, with links! Much of it is obvious, but I’d argue, rarely discussed. For instance, it’s very clear that we can post links pretty much anywhere. Doing so, we’re sharing their “content”. (In a semiotic sense, links are indices. I wish we can move from the “semantic Web” to the “semiotic Web”. But that’s another issue.) Sharing a link is the basic act of the social Web. It’s so obvious and frequent that it seems not to require discussion”.

Another obvious thing about links: we can measure the number of times they’re followed. In 2011, more than thirty years after hypertext has been introduced as a stable concept, much of the Web’s finances still relies on “clickthroughs”. Seems important.

And there’s a lot of processing which can be done with URLs: shortening them, adding them to “to do” lists, checking them for validity, keeping them in link libraries, archiving their “content”, showing them as external or internal links, preventing them from “rotting away”, showing the wordcount or reading time of the item they “target”, display them as QR codes, abuse them, etc.

As you can notice, it’s easy to get me on a tangent simply thinking about URLs. What’s this have t’do with iCloud, you ask? Probably not much, in terms of the actual service which will be announced at Moscone. But I’ve been dreaming about iCloud as a way to integrate Diigo, Instapaper, Delicious, reddit, digg, Slashdot, StumbleUpon, Spurl, The NethernetXmarks

Hey, I told you I was dreaming! Something as simple as managing, processing, sharing, and archiving links in iCloud could lead to just about anything, in my imagination.

And speaking of Xmarks… It’s now owned by Lastpass, a company which focus on password management. IMHO, some Lastpass-like features could make their way in diverse products, including iCloud. Is this far-fetched? Possibly. But secure handling of passwords can be a major issue in both of Apple’s new operating systems (Mac OS X Lion and iOS5). From “keychains” to SSO, there’s a lot of work to be done which relates to password management, in my mind.

Which leads me to think about authentication in general and the rumours about “deep Twitter integration in iOS 5”. (Not directly related to iCloud, but who knows?) Again, something which can send me (and others) on drift-off moments. What if this integration suddenly made iOS devices more useful in terms of social networking services? Something to ponder, if one has a propensity for pondering.

At the same time, given the relative lack of activity on iTunes Ping, I wouldn’t bet on Twitter integration having that major an impact by itself. Not unlike Google, Apple has a hard time making a mark on the social Web. Now, if Twitter integration does connect to everything else Apple does, it could lead to interesting things. A full-fledged online identity? Access to contacts for not only messaging and photo sharing but for collaboration, group management, and media sharing? Not betting on any of this, but it could be fun. Again, not specific to iCloud, but quite related to “The Cloud”. If Twitter integration is deep enough, in iOS 5, it’d be possible to use iOS devices for “cloud computing”, getting further into the “post-PC era”.

An iCloud feature which is expected by several people, is something like an OTA version of the “iTunes file sharing” feature in iOS. Several apps (especially Apple’s own apps) use iTunes and a USB cable to share files. It was a welcome addition to iTunes 9.1 but it’s rather inconvenient. So many other apps rely on Dropbox for file sharing.

Which leads me to dream about iCloud as a replacement for Dropbox. Sounds extremely unlikely that it’ll have the full Dropbox feature set, especially if one thinks about the “Pro 50” and “Pro 100” plans on Dropbox. But I dream of the day when Apple’s iDisk will compete with Dropbox. Not that I’m convinced it ever will. But it’d make Apple’s devices all the more useful if it did.

Something similar, which isn’t frequently discussed directly, in connection with iCloud rumours, but which would rock: Mozy- or Carbonite-style backup, for Mac OS X machines. Sounds very unlikely that Apple will ever offer something like this but, as crazy as it may sound, the connection between Time Capsule and iCloud would be great if it went that far. From a user’s perspective, the similarities between Time Machine backup and “backing up in the cloud” (à la Mozy/Carbonite) are quite obvious. The advantages of both are clear. And while no hardware announcement is supposed to make its way to the WWDC 2011 keynote, I’d give the Time Capsule some consideration if it provided me with the equivalent of what I currently have with Mozy. Not to mention that Mozy has already sparked some drift-off moments, in me, before they announced their new plans. What if I could have a single service which combines features from Mozy, Time Machine, Dropbox, and YouSendIt?

I even think about the possibilities in terms of web hosting. As it stands, MobileMe does allow for some Web publishing through the iWeb application in its iLife suite. But iWeb has never been a major effort for Apple and it hasn’t been seen a significant update in quite a while. What if iCloud could become a true webhost just like, say… iWeb.com? (Semi-disclaimer: I won a free account with iWeb.com, last Fall, and I host some sites there. I also know some of the people who work there…)

Yet again, I don’t expect this to happen. It’s not speculation, on my part. It’s a daydream.

The reason this makes me dream is that I find all these things to be related and I wish they were integrated more seamlessly. Something about which Apple haters may not care much is the type of integration represented by iTunes. As clunky as iTunes may be, in some respects, it’s quite a success in terms of integrating a lot of different things. In fact, it probably overextended its reach a bit too much and we need to replace it. Apple needs to replace iTunes and we should also replace iTunes in our lives.

Like Gruber, I end up thinking about iCloud in relation to iTunes more than in relation to MobileMe. But I also dream about the ideal cloud service, which would not only sync and backup files between iOS devices, hundreds of millions of iTunes store accounts, and Macs, but replace several of the services for which I’m paying monthly fees.

Here’s to dreaming…

Other parts of this crazy, iCloud-infused daydream, in notes form:

Buying Apps

Been mulling over this for a while, now. Before the Mac App Store was announced, I was thinking about “mobile apps” (mostly the iTunes/iOS App Store, but also Android Marketplace). Since the MAS announcement, though, I’ve been thinking about something which may be a broader shift. And because the MAS is opening tomorrow, now might be a good time to put some of these ideas out there.

The following blogpost, by Markus Nigrin, provides important insight from the perspective of some iOS developers.

Mac App Store – Sneak Peak

I tend to agree with the underlying idea: “traditional” Mac OS X developers run the risk of missing the boat, with the Mac App Store.

This point is made even more graphically by David Gewirtz on ZDNet.

While I do care about the fate of Mac developers, I’m really thinking about the users’ side of the equation. And I’m not really caught up in the Manichean “is it a good thing or a bad thing for us” kind of thinking.

Now, I do still think about the business side of things. Not that I have “a dog in this race,” but I do think about the business models, including app costs and “Free As In Beer”/No-Cost Software. Partly because, until recently, I rarely bought applications.

A few things changed, recently. One is that I’ve been able to allocate more money to my computing needs (partly because I do freelance work, much of it related to online stuff). Another is that I started paying more attention to software bundles like MacUpdate Promo and MacHeist. Yet another is that (very recently) I started buying games on Steam. And, finally, I’ve been getting a rather large number of iOS apps on the App Store, including some paid ones (despite my frustrating experience, initially).

One thing I notice is that there does seem to be a distinction between mobile-style “apps” and “traditional software packages.” While “app” is short for “application” and there may not be a very strong distinction between the type of software distributed through the Mac App Store and other applications, “apps” may be emerging as something of a new category. Partly in terms of business, partly in terms of development models, partly in terms of users’ expectations.

It may be a bit confusing, especially since Apple itself is selling pieces of software on both sides. For instance, they will distribute their iWork productivity suite (Keynote, Pages, and Numbers) through six (6) different ways.

  1. You can buy it as a productivity suite.
  2. You can get it through an education licensing program.
  3. You can get it as part of a box set (with Mac OS X and iLife).
  4. You can get it preinstalled on new hardware.
  5. You can buy iPad versions of individual apps (through the iOS App Store).
  6. And you’ll soon be able to buy Mac versions of the individual applications on the Mac App Store.

There are significant (and frustrating) differences between the Mac and iPad versions of these three programs. But Apple still markets the iPad apps as directly equivalent to the Mac applications. It might work as a marketing strategy, but it can be quite confusing. For instance, it can be difficult to find information about features which may or may not be present in the iPad version, such as the ability to change master slides (was looking for this just last night).

In mind, there might be a distinction between apps and applications in terms of user behaviour. When I get something from the (iOS) App Store, it’s usually a matter of curiosity. Sure, there are occasions where I look for and get a very specific app for a very specific need. But, most of the time, my behaviour is “impulsive.”

If it’s a free app, I don’t think twice about it, it’s almost on the order of a reflex. If the app is inexpensive (or if AppShopper warned me that it decreased in price quite significantly), chances are that I’ll buy it even if I’m just vaguely interested in it. If it’s more expensive, I may add it to my AppShopper wishlist, look for cheaper equivalents, or make a headnote to look later in that category.

In my mind, free and inexpensive apps need almost no justification. But, after a certain threshold (which may be as low as 5$ in certain categories), I need a rather strong incentive to invest in an app.

In many ways, the same is true with (non-mobile) applications. The threshold might be different, within the same category. But there’s a point at which I go from “sure, I’ll download this” to “do I really need it?” And cost isn’t the only factor. I won’t download a no-cost application if I get the impression that it’ll be difficult to use or take too much disk space.

Apparent simplicity is important, here. Even if an app merely looks simple, I might get it, just to explore and experiment. If, at first blush, an application looks unnecessarily complicated, chances are that I won’t g

Thinking about this, I’m predicting my own behaviour with the Mac App Store. I’ll probably start trying out all sorts of free and low-cost “apps” if they look like they can provide me with instant gratification. (Especially if I can use an external hard drive to store them.) And I’ll probably buy a few “apps” that I can justify, in terms of effort and cost. But I might give up quickly on these if my initial experience isn’t optimal (if the apps in question aren’t worth the cost or effort). And I’ll try different things associated with these apps I do enjoy.

Which, in a way, is my main thought: apps aren’t really like applications, in this case. They’re a “hook” for something else.

There are useful examples with Web applications and services. Especially things like Foursquare, Twitter, and ToodleDo. I wouldn’t spend fortunes on apps for use with these services. But I do spend a fair bit of time using these services. Mixed models like those for InstaPaper and TaskPaper are also important to keep in mind.

I actually have a lot more to say about all of this, but it’s probably better if I post it now. We’ll see how things go, tomorrow.

WordPress as Content Directory: Getting Somewhere

{I tend to ramble a bit. If you just want a step-by-step tutorial, you can skip to here.}

Woohoo!

I feel like I’ve reached a milestone in a project I’ve had in mind, ever since I learnt about Custom Post Types in WordPress 3.0: Using WordPress as a content directory.

The concept may not be so obvious to anyone else, but it’s very clear to me. And probably much clearer for anyone who has any level of WordPress skills (I’m still a kind of WP newbie).

Basically, I’d like to set something up through WordPress to make it easy to create, review, and publish entries in content databases. WordPress is now a Content Management System and the type of “content management” I’d like to enable has to do with something of a directory system.

Why WordPress? Almost glad you asked.

These days, several of the projects on which I work revolve around WordPress. By pure coincidence. Or because WordPress is “teh awsum.” No idea how representative my sample is. But I got to work on WordPress for (among other things): an academic association, an adult learners’ week, an institute for citizenship and social change, and some of my own learning-related projects.

There are people out there arguing about the relative value of WordPress and other Content Management Systems. Sometimes, WordPress may fall short of people’s expectations. Sometimes, the pro-WordPress rhetoric is strong enough to sound like fanboism. But the matter goes beyond marketshare, opinions, and preferences.

In my case, WordPress just happens to be a rather central part of my life, these days. To me, it’s both a question of WordPress being “the right tool for the job” and the work I end up doing being appropriate for WordPress treatment. More than a simple causality (“I use WordPress because of the projects I do” or “I do these projects because I use WordPress”), it’s a complex interaction which involves diverse tools, my skillset, my social networks, and my interests.

Of course, WordPress isn’t perfect nor is it ideal for every situation. There are cases in which it might make much more sense to use another tool (Twitter, TikiWiki, Facebook, Moodle, Tumblr, Drupal..). And there are several things I wish WordPress did more elegantly (such as integrating all dimensions in a single tool). But I frequently end up with WordPress.

Here are some things I like about WordPress:

This last one is where the choice of WordPress for content directories starts making the most sense. Not only is it easy for me to use and build on WordPress but the learning curves are such that it’s easy for me to teach WordPress to others.

A nice example is the post editing interface (same in the software and service). It’s powerful, flexible, and robust, but it’s also very easy to use. It takes a few minutes to learn and is quite sufficient to do a lot of work.

This is exactly where I’m getting to the core idea for my content directories.

I emailed the following description to the digital content editor for the academic organization for which I want to create such content directories:

You know the post editing interface? What if instead of editing posts, someone could edit other types of contents, like syllabi, calls for papers, and teaching resources? What if fields were pretty much like the form I had created for [a committee]? What if submissions could be made by people with a specific role? What if submissions could then be reviewed by other people, with another role? What if display of these items were standardised?

Not exactly sure how clear my vision was in her head, but it’s very clear for me. And it came from different things I’ve seen about custom post types in WordPress 3.0.

For instance, the following post has been quite inspiring:

I almost had a drift-off moment.

But I wasn’t able to wrap my head around all the necessary elements. I perused and read a number of things about custom post types, I tried a few things. But I always got stuck at some point.

Recently, a valuable piece of the puzzle was provided by Kyle Jones (whose blog I follow because of his work on WordPress/BuddyPress in learning, a focus I share).

Setting up a Staff Directory using WordPress Custom Post Types and Plugins | The Corkboard.

As I discussed in the comments to this post, it contained almost everything I needed to make this work. But the two problems Jones mentioned were major hurdles, for me.

After reading that post, though, I decided to investigate further. I eventually got some material which helped me a bit, but it still wasn’t sufficient. Until tonight, I kept running into obstacles which made the process quite difficult.

Then, while trying to solve a problem I was having with Jones’s code, I stumbled upon the following:

Rock-Solid WordPress 3.0 Themes using Custom Post Types | Blancer.com Tutorials and projects.

This post was useful enough that I created a shortlink for it, so I could have it on my iPad and follow along: http://bit.ly/RockSolidCustomWP

By itself, it might not have been sufficient for me to really understand the whole process. And, following that tutorial, I replaced the first bits of code with use of the neat plugins mentioned by Jones in his own tutorial: More Types, More Taxonomies, and More Fields.

I played with this a few times but I can now provide an actual tutorial. I’m now doing the whole thing “from scratch” and will write down all steps.

This is with the WordPress 3.0 blogging software installed on a Bluehost account. (The WordPress.com blogging service doesn’t support custom post types.) I use the default Twenty Ten theme as a parent theme.

Since I use WordPress Multisite, I’m creating a new test blog (in Super Admin->Sites, “Add New”). Of course, this wasn’t required, but it helps me make sure the process is reproducible.

Since I already installed the three “More Plugins” (but they’re not “network activated”) I go in the Plugins menu to activate each of them.

I can now create the new “Product” type, based on that Blancer tutorial. To do so, I go to the “More Types” Settings menu, I click on “Add New Post Type,” and I fill in the following information: post type names (singular and plural) and the thumbnail feature. Other options are set by default.

I also set the “Permalink base” in Advanced settings. Not sure it’s required but it seems to make sense.

I click on the “Save” button at the bottom of the page (forgot to do this, the last time).

I then go to the “More Fields” settings menu to create a custom box for the post editing interface.

I add the box title and change the “Use with post types” options (no use in having this in posts).

(Didn’t forget to click “save,” this time!)

I can now add the “Price” field. To do so, I need to click on the “Edit” link next to the “Product Options” box I just created and add click “Add New Field.”

I add the “Field title” and “Custom field key”:

I set the “Field type” to Number.

I also set the slug for this field.

I then go to the “More Taxonomies” settings menu to add a new product classification.

I click “Add New Taxonomy,” and fill in taxonomy names, allow permalinks, add slug, and show tag cloud.

I also specify that this taxonomy is only used for the “Product” type.

(Save!)

Now, the rest is more directly taken from the Blancer tutorial. But instead of copy-paste, I added the files directly to a Twenty Ten child theme. The files are available in this archive.

Here’s the style.css code:

/*
Theme Name: Product Directory
Theme URI: http://enkerli.com/
Description: A product directory child theme based on Kyle Jones, Blancer, and Twenty Ten
Author: Alexandre Enkerli
Version: 0.1
Template: twentyten
*/
@import url("../twentyten/style.css");

The code for functions.php:

<!--?php /**  * ProductDir functions and definitions  * @package WordPress  * @subpackage Product_Directory  * @since Product Directory 0.1  */ /*Custom Columns*/ add_filter("manage_edit-product_columns", "prod_edit_columns"); add_action("manage_posts_custom_column",  "prod_custom_columns"); function prod_edit_columns($columns){ 		$columns = array( 			"cb" =--> "<input type="\&quot;checkbox\&quot;" />",
			"title" => "Product Title",
			"description" => "Description",
			"price" => "Price",
			"catalog" => "Catalog",
		);

		return $columns;
}

function prod_custom_columns($column){
		global $post;
		switch ($column)
		{
			case "description":
				the_excerpt();
				break;
			case "price":
				$custom = get_post_custom();
				echo $custom["price"][0];
				break;
			case "catalog":
				echo get_the_term_list($post->ID, 'catalog', '', ', ','');
				break;
		}
}
?>

And the code in single-product.php:

<!--?php /**  * Template Name: Product - Single  * The Template for displaying all single products.  *  * @package WordPress  * @subpackage Product_Dir  * @since Product Directory 1.0  */ get_header(); ?-->
<div id="container">
<div id="content">
<!--?php the_post(); ?-->

<!--?php 	$custom = get_post_custom($post--->ID);
	$price = "$". $custom["price"][0];

?>
<div id="post-<?php the_ID(); ?><br />">>
<h1 class="entry-title"><!--?php the_title(); ?--> - <!--?=$price?--></h1>
<div class="entry-meta">
<div class="entry-content">
<div style="width: 30%; float: left;">
			<!--?php the_post_thumbnail( array(100,100) ); ?-->
			<!--?php the_content(); ?--></div>
<div style="width: 10%; float: right;">
			Price
<!--?=$price?--></div>
</div>
</div>
</div>
<!-- #content --></div>
<!-- #container -->

<!--?php get_footer(); ?-->

That’s it!

Well, almost..

One thing is that I have to activate my new child theme.

So, I go to the “Themes” Super Admin menu and enable the Product Directory theme (this step isn’t needed with single-site WordPress).

I then activate the theme in Appearance->Themes (in my case, on the second page).

One thing I’ve learnt the hard way is that the permalink structure may not work if I don’t go and “nudge it.” So I go to the “Permalinks” Settings menu:

And I click on “Save Changes” without changing anything. (I know, it’s counterintuitive. And it’s even possible that it could work without this step. But I spent enough time scratching my head about this one that I find it important.)

Now, I’m done. I can create new product posts by clicking on the “Add New” Products menu.

I can then fill in the product details, using the main WYSIWYG box as a description, the “price” field as a price, the “featured image” as the product image, and a taxonomy as a classification (by clicking “Add new” for any tag I want to add, and choosing a parent for some of them).

Now, in the product management interface (available in Products->Products), I can see the proper columns.

Here’s what the product page looks like:

And I’ve accomplished my mission.

The whole process can be achieved rather quickly, once you know what you’re doing. As I’ve been told (by the ever-so-helpful Justin Tadlock of Theme Hybrid fame, among other things), it’s important to get the data down first. While I agree with the statement and its implications, I needed to understand how to build these things from start to finish.

In fact, getting the data right is made relatively easy by my background as an ethnographer with a strong interest in cognitive anthropology, ethnosemantics, folk taxonomies (aka “folksonomies“), ethnography of communication, and ethnoscience. In other words, “getting the data” is part of my expertise.

The more technical aspects, however, were a bit difficult. I understood most of the principles and I could trace several puzzle pieces, but there’s a fair deal I didn’t know or hadn’t done myself. Putting together bits and pieces from diverse tutorials and posts didn’t work so well because it wasn’t always clear what went where or what had to remain unchanged in the code. I struggled with many details such as the fact that Kyle Jones’s code for custom columns wasn’t working first because it was incorrectly copied, then because I was using it on a post type which was “officially” based on pages (instead of posts). Having forgotten the part about “touching” the Permalinks settings, I was unable to get a satisfying output using Jones’s explanations (the fact that he doesn’t use titles didn’t really help me, in this specific case). So it was much harder for me to figure out how to do this than it now is for me to build content directories.

I still have some technical issues to face. Some which are near essential, such as a way to create archive templates for custom post types. Other issues have to do with features I’d like my content directories to have, such as clearly defined roles (the “More Plugins” support roles, but I still need to find out how to define them in WordPress). Yet other issues are likely to come up as I start building content directories, install them in specific contexts, teach people how to use them, observe how they’re being used and, most importantly, get feedback about their use.

But I’m past a certain point in my self-learning journey. I’ve built my confidence (an important but often dismissed component of gaining expertise and experience). I found proper resources. I understood what components were minimally necessary or required. I succeeded in implementing the system and testing it. And I’ve written enough about the whole process that things are even clearer for me.

And, who knows, I may get feedback, questions, or advice..

What Not to Tweet

Here’s a list I tweeted earlier.

Twenty Things You Should Never, Ever Tweet for Fear of Retaliation from the Tweet Police

  1. Lists. Too difficult to follow.
  2. Do’s and don’ts. Who died and made you bandleader?
  3. Personal thoughts. Nobody cares what anyone else thinks, anyway.
  4. Anything in a foreign language. It confuses everyone.
  5. Personal opinions. You may offend someone.
  6. Jokes. Same reason as #5.
  7. Links. Too dangerous, since some could be malicious.
  8. Anything in “the second degree.” The bareness of context prevents careful reading.
  9. Anything insightful. Who do you think you are?
  10. Personal replies. Can’t you get a room?
  11. -20: What @oatmeal said you shouldn’t tweet. If it’s funny, it must be true.

In case it wasn’t clear… Yes, I mean this as sarcasm. One of my pet peeves is to hear people tell others what to do or not to do, without appropriate context. It’s often perceived to be funny or useful but, to be honest, it just rubs me the wrong way. Sure, they’re allowed to do it. I won’t prevent them. I don’t even think they should stop, that’s really not for me to decide. It’s just that, being honest with myself, I realize how negative of an effect it has on me. It actually reaches waaaaay down into something I don’t care to visit very often.

The Oatmeal can be quite funny. Reading a few of these comics, recently, I literally LOLed. And this one probably pleased a lot of people, because it described some of their own pet peeves. Besides, it’s an old comic, probably coming from a time when tweets were really considered to be answers to the original Twitter prompt: “What are you doing?” (i.e., before the change to the somewhat more open “What’s happening?”). But I’ve heard enough expressions of what people should or shouldn’t do with a specific social media system that I felt the need to vent. So, that was the equivalent of a rant (and this post is closer to an actual rant).

I mean, there’s a huge difference between saying “these are the kinds of uses for which I think Twitter is the appropriate tool” and the flat-out dismissal of what others have done. While Twitter is old news, as social media go, it’s still unfolding and much of its strength comes from the fact that we don’t actually have a rigid notion of what it should be.

Not that there aren’t uses of Twitter I dislike. In fact, for much of 2009, I felt it was becoming too commercial for my taste. I felt there was too much promotion of commercial entities and products, and that it was relatively difficult to avoid such promotional tweets if one were to follow the reciprocation principle (“I really should make sure I follow those who follow me, even if a large proportion of them are just trying to increase their follower counts”). But none of this means that “Twitter isn’t for commercial promotion.” Structurally, Twitter almost seems to be made for such uses. Conceptually, it comes from the same “broadcast” view of communication, shared by many marketers, advertisers, PR experts, and movie producers. As social media tools go, Twitter is among the most appropriate ones to use to broadly distribute focused messages without having to build social relationships. So, no matter how annoyed I may get at these tweets and at commercial Twitterers, it’d be inaccurate to say that “Twitter isn’t for that.” Besides, “Twitter, Inc.” has adopted commercial promotion as a major part of its “business model.” No matter what one feels about this (say, that it’s not very creative or that it will help distinguish between commercial tweets and the rest of Twitter traffic), it seems to imply that Twitter is indeed about commercial promotion as much as it is about “shar[ing] and discover[ing] what’s happening now.”

The same couldn’t be said about other forms of tweeting that others may dislike. It’d be much harder to make a case for, say, conference liveblogging as being an essential part of what Twitter is about. In fact, some well-known and quite vocal people have made pronouncements about how inappropriate, in their minds, such a practice was. To me, much of it sounds like attempts at rationalizing a matter of individual preference. Some may dislike it but Twitter does make a very interesting platform for liveblogging conferences. Sure, we’ve heard about the negative consequences of the Twitter backchannel at some high-profile events. And there are some technical dimensions of Twitter which make liveblogging potentially more annoying, to some users, than if it were on another platform. But claiming that Twitter isn’t for liveblogging  reveals a rather rigid perspective of what social media can be. Again, one of the major strengths in Twitter is its flexibility. From “mentions” and “hashtags” to “retweets” and metadata, the platform has been developing over time based on usage patterns.

For one thing, it’s now much more conversational than it was in 2007, and some Twitter advocates are quite proud of that. So one might think that Twitter is for conversation. But, at least in my experience, Twitter isn’t that effective a tool for two-way communication let alone for conversations involving more than two people. So, if we’re to use conversation to evaluate Twitter (as its development may suggest we should do), it seems not to be that successful.

In this blog version of my list, I added a header with a mention of the “Tweet Police.” I mean it in the way that people talk about the “Fashion Police,” wish immediately makes me think about “fashion victims,” the beauty myth, the objectification of the human body, the social pressure to conform to some almost-arbitrary canons, the power struggles between those who decide what’s fashionable and those who need to dress fashionably to be accepted in some social contexts, etc. Basically, it leads to rather unpleasant thoughts. In a way, my mention of the “Tweet Police” is a strategy to “fight this demon” by showing how absurd it may become. Sure, it’d be a very tricky strategy if it were about getting everyone to just “get the message.” But, in this case, it’s about doing something which feels good. It’s my birthday, so I allow myself to do this.

Development and Quality: Reply to Agile Diary

Former WiZiQ product manager Vikrama Dhiman responded to one of my tweets with a full-blown blogpost, thereby giving support to Matt Mullenweg‘s point that microblogging goes hand-in-hand with “macroblogging.”

My tweet:

enjoys draft æsthetics yet wishes more developers would release stable products. / adopte certains produits trop rapidement.

Vikrama’s post:

Good Enough Software Does Not Mean Bad Software « Agile Diary, Agile Introduction, Agile Implementation.

My reply:

“To an engineer, good enough means perfect. With an artist, there’s no such thing as perfect.” (Alexander Calder)

Thanks a lot for your kind comments. I’m very happy that my tweet (and status update) triggered this.

A bit of context for my tweet (actually, a post from Ping.fm, meant as a status update, thereby giving support in favour of conscious duplication, «n’en déplaise aux partisans de l’action contre la duplication».)

I’ve been thinking about what I call the “draft æsthetics.” In fact, I did a podcast episode about it. My description of that episode was:

Sometimes, there is such a thing as “Good Enough.”

Though I didn’t emphasize the “sometimes” part in that podcast episode, it was an important part of what I wanted to say. In fact, my intention wasn’t to defend draft æsthetics but to note that there seems to be a tendency toward this æsthetic mode. I do situate myself within that mode in many things I do, but it really doesn’t mean that this mode should be the exclusive one used in any context.

That aforequoted tweet was thus a response to my podcast episode on draft æsthetics. “Yes, ‘good enough’ may work, sometimes. But it needs not be applied in all cases.”

As I often get into convoluted discussions with people who seem to think that I condone or defend a position because I take it for myself, the main thing I’d say there is that I’m not only a relativist but I cherish nuance. In other words, my tweet was a way to qualify the core statement I was talking about in my podcast episode (that “good enough” exists, at times). And that statement isn’t necessarily my own. I notice a pattern by which this statement seems to be held as accurate by people. I share that opinion, but it’s not a strongly held belief of mine.

Of course, I digress…

So, the tweet which motivated Vikrama had to do with my approach to “good enough.” In this case, I tend to think about writing but in view of Eric S. Raymond’s approach to “Release Early, Release Often” (RERO). So there is a connection to software development and geek culture. But I think of “good enough” in a broader sense.

Disclaimer: I am not a coder.

The Calder quote remained in my head, after it was mentioned by a colleague who had read it in a local newspaper. One reason it struck me is that I spend some time thinking about artists and engineers, especially in social terms. I spend some time hanging out with engineers but I tend to be more on the “artist” side of what I perceive to be an axis of attitudes found in some social contexts. I do get a fair deal of flack for some of my comments on this characterization and it should be clear that it isn’t meant to imply any evaluation of individuals. But, as a model, the artist and engineer distinction seems to work, for me. In a way, it seems more useful than the distinction between science and art.

An engineer friend with whom I discussed this kind of distinction was quick to point out that, to him, there’s no such thing as “good enough.” He was also quick to point out that engineers can be creative and so on. But the point isn’t to exclude engineers from artistic endeavours. It’s to describe differences in modes of thought, ways of knowing, approaches to reality. And the way these are perceived socially. We could do a simple exercise with terms like “troubleshooting” and “emotional” to be assigned to the two broad categories of “engineer” and “artist.” Chances are that clear patterns would emerge. Of course, many concepts are as important to both sides (“intelligence,” “innovation”…) and they may also be telling. But dichotomies have heuristic value.

Now, to go back to software development, the focus in Vikrama’s Agile Diary post…

What pushed me to post my status update and tweet is in fact related to software development. Contrary to what Vikrama presumes, it wasn’t about a Web application. And it wasn’t even about a single thing. But it did have to do with firmware development and with software documentation.

The first case is that of my Fonera 2.0n router. Bought it in early November and I wasn’t able to connect to its private signal using my iPod touch. I could connect to the router using the public signal, but that required frequent authentication, as annoying as with ISF. Since my iPod touch is my main WiFi device, this issue made my Fonera 2.0n experience rather frustrating.

Of course, I’ve been contacting Fon‘s tech support. As is often the case, that experience was itself quite frustrating. I was told to reset my touch’s network settings which forced me to reauthenticate my touch on a number of networks I access regularly and only solved the problem temporarily. The same tech support person (or, at least, somebody using the same name) had me repeat the same description several times in the same email message. Perhaps unsurprisingly, I was also told to use third-party software which had nothing to do with my issue. All in all, your typical tech support experience.

But my tweet wasn’t really about tech support. It was about the product. Thougb I find the overall concept behind the Fonera 2.0n router very interesting, its implementation seems to me to be lacking. In fact, it reminds me of several FLOSS development projects that I’ve been observing and, to an extent, benefitting from.

This is rapidly transforming into a rant I’ve had in my “to blog” list for a while about “thinking outside the geek box.” I’ll try to resist the temptation, for now. But I can mention a blog thread which has been on my mind, in terms of this issue.

Firefox 3 is Still a Memory Hog — The NeoSmart Files.

The blogpost refers to a situation in which, according to at least some users (including the blogpost’s author), Firefox uses up more memory than it should and becomes difficult to use. The thread has several comments providing support to statements about the relatively poor performance of Firefox on people’s systems, but it also has “contributions” from an obvious troll, who keeps assigning the problem on the users’ side.

The thing about this is that it’s representative of a tricky issue in the geek world, whereby developers and users are perceived as belonging to two sides of a type of “class struggle.” Within the geek niche, users are often dismissed as “lusers.” Tech support humour includes condescending jokes about “code 6″: “the problem is 6″ from the screen.” The aforementioned Eric S. Raymond wrote a rather popular guide to asking questions in geek circles which seems surprisingly unaware of social and cultural issues, especially from someone with an anthropological background. Following that guide, one should switch their mind to that of a very effective problem-solver (i.e., the engineer frame) to ask questions “the smart way.” Not only is the onus on users, but any failure to comply with these rules may be met with this air of intellectual superiority encoded in that guide. IOW, “Troubleshoot now, ask questions later.”

Of course, many users are “guilty” of all sorts of “crimes” having to do with not reading the documentation which comes with the product or with simply not thinking about the issue with sufficient depth before contacting tech support. And as the majority of the population is on the “user” side, the situation can be described as both a form of marginalization (geek culture comes from “nerd” labels) and a matter of elitism (geek culture as self-absorbed).

This does have something to do with my Fonera 2.0n. With it, I was caught in this dynamic whereby I had to switch to the “engineer frame” in order to solve my problem. I eventually did solve my Fonera authentication problem, using a workaround mentioned in a forum post about another issue (free registration required). Turns out, the “release candidate” version of my Fonera’s firmware does solve the issue. Of course, this new firmware may cause other forms of instability and installing it required a bit of digging. But it eventually worked.

The point is that, as released, the Fonera 2.0n router is a geek toy. It’s unpolished in many ways. It’s full of promise in terms of what it may make possible, but it failed to deliver in terms of what a router should do (route a signal). In this case, I don’t consider it to be a finished product. It’s not necessarily “unstable” in the strict sense that a software engineer might use the term. In fact, I hesitated between different terms to use instead of “stable,” in that tweet, and I’m not that happy with my final choice. The Fonera 2.0n isn’t unstable. But it’s akin to an alpha version released as a finished product. That’s something we see a lot of, these days.

The main other case which prompted me to send that tweet is “CivRev for iPhone,” a game that I’ve been playing on my iPod touch.

I’ve played with different games in the Civ franchise and I even used the FLOSS version on occasion. Not only is “Civilization” a geek classic, but it does connect with some anthropological issues (usually in a problematic view: Civ’s worldview lacks anthro’s insight). And it’s the kind of game that I can easily play while listening to podcasts (I subscribe to a number of th0se).

What’s wrong with that game? Actually, not much. I can’t even say that it’s unstable, unlike some other items in the App Store. But there’s a few things which aren’t optimal in terms of documentation. Not that it’s difficult to figure out how the game works. But the game is complex enough that some documentation is quite useful. Especially since it does change between one version of the game and another. Unfortunately, the online manual isn’t particularly helpful. Oh, sure, it probably contains all the information required. But it’s not available offline, isn’t optimized for the device it’s supposed to be used with, doesn’t contain proper links between sections, isn’t directly searchable, and isn’t particularly well-written. Not to mention that it seems to only be available in English even though the game itself is available in multiple languages (I play it in French).

Nothing tragic, of course. But coupled with my Fonera experience, it contributed to both a slight sense of frustration and this whole reflection about unfinished products.

Sure, it’s not much. But it’s “good enough” to get me started.