Moving On

Sometimes, you might as well make radical changes in your life.

[I’m typically not very good at going back to drafts and I don’t have much time to write this. But I can RERO this. It’s an iterative process in any case….]

Been thinking about different things which all relate to the same theme: changing course, seizing opportunities, shifting focus, adapting to new situations, starting over, getting a clean slate… Moving on.

One reason is that I recently decided to end my ethnography podcast. Not that major a decision and rather easy to make. Basically, I had stopped doing it but I had yet to officially end it. I had to make it clear, in my mind, that it’s not part of the things I’m doing, these days. Not that it was a big thing in my life but I had set reminders every month that I had to record a podcast episode. It worked for ten episode (in ten months) but, once I had missed one episode, the reminder was nagging me more than anything else.

In this sense, “moving on” is realistic/pragmatic. Found something similar in Getting Things Done, by David Allen.

It’s also similar to something Larry Lessig called “email bankruptcy,” as a step toward enhanced productivity.

In fact, even financial bankruptcy can relate to this, in some contexts. In Canada, at least, bankruptcy is most adequately described as a solution to a problem, not the problem itself. I’ve known some people who were able to completely rebuild their finances after declaring bankruptcy, sometimes even getting a better credit rating than someone who hadn’t gone bankrupt. I know how strongly some people may react to this concept of bankruptcy (based on principle, resentment, fears, hopes…). It’s an extreme example of what I mean by “moving on.” It goes well with the notion, quite common in North American cultural contexts, that you always deserve a second chance (but that you should do things yourself).

Of course, similar things happen with divorces which, similarly, can often be considered as solutions to a problem rather than the problem itself. No matter how difficult or how bad divorce might be, it’s a way to start over. In some sense, it’s less extreme an example as the bankruptcy one. But it may still generate negative vibes or stir negative emotions.

Because what I’m thinking about has more to do with “turning over a new leaf.” And taking the “leap of faith” which will make you go where you feel more comfortable. I’m especially thinking about all sorts of cases of people who decided to make radical changes in their professional or personal lives, often leaving a lot behind. Whether they were forced to implement such changes or decided to jump because they simply wanted to, all of the cases I remember have had positive outcomes.

It reminds me of a good friend of mine with whom I went through music school, in college. When he finished college, he decided to follow the music path and registered for the conservatory. But, pretty quickly, he realized that it wasn’t for him. Even though he had been intensely “in music” for several years, with days of entering the conservatory, he saw that music wasn’t to remain the central focus of his career. Through a conversation with a high school friend (who later became his wife and the mother of his children), he found out that it wasn’t too late for him to register for university courses. He had been thinking about phys. ed., and thought it might be a nice opportunity to try that path. He’s been a phys. ed. teacher for a number of years. We had lunch together last year and he seems very happy with his career choice. He also sounds like a very dedicated and effective phys. ed. teacher.

In my last podcast episode, I mentioned a few things about my views of this “change of course.” Including what has become something of an expression, for me: “Done with fish.” Comes from the movie Adaptation. The quote is found here (preceded by a bit of profanity). Basically, John Laroche, who was passionately dedicated to fish, decided to completely avoid anything having to do with fish. I can relate to this at some rather deep level.

I’m also thinking about the negative consequences of “sticking with” something which isn’t working, shifting too late or too quickly, implementing changes in inappropriate ways. Plenty of examples there. Most of the ones which come to my mind have to do with business settings. One which would require quite a bit of “explaining” is my perception of Google’s strategy with Wave. Put briefly (with the hope of revisiting this issue), I think Google made bad decisions with Wave, including killing it both too late and too early (no, I don’t see this as a contradiction; but I don’t have time to explain it). They also, I feel, botched a few transitions, in this. And, more importantly, I’d say that they failed to adapt the product to what was needed.

And the trigger for several of my reflections on this “moving on” idea have to do with this kind of adaptation (fun that the movie of that name should be involved, eh?). Twitter could be an inspiration, in this case. Not only did they, like Flickr, start through a switch away from another project, but Twitter was able to transform users’ habits into the basis for some key features. Hashtags and “@replies” are well-known examples. But you could even say that most of the things they’ve been announcing have been related to the way people use their tools.

So, in a way, it’s about the balance between vision and responsiveness. Vision is often discussed and it sounds to some people as a key thing in any “task-based group (from a team to a corporation). But the way a team can switch from one project to the next based on feedback (from users or other stakeholders) seems underrated. Although, there is some talk about the “startup mentality” in many contexts, including Google and Apple. Words which fit this semantic field include: “agile,” “flexible,” “pivot,” “lean,” and “nimble” (the latter word seemed to increase in currency after being used by Barack Obama in a speech).

Anyhoo… Gotta go.

But, just before I go: I am moving on with some things (including my podfade but also a shift away from homebrewing). But the key things in my life are very stable, especially my sentimental life.

Advertisement

Actively Reading: Organic Ideas for Startups

Annotations on Paul Graham’s Organic Startup Ideas.

Been using Diigo as a way to annotate online texts. In this case, I was as interested in the tone as in the text itself. At the same time, I kept thinking about things which seem to be missing from Diigo.

One thing I like about this text is its tone. There’s an honesty, an ingenuity that I find rare in this type of writing.

  • startup ideas
    • The background is important, in terms of the type of ideas about which we’re constructing something.
  • what do you wish someone would make for you?
    • My own itch has to do with Diigo, actually. There’s a lot I wish Diigo would make for me. I may be perceived as an annoyance, but I think my wishlist may lead to something bigger and possibly quite successful.
    • The difference between this question and the “scratch your own itch” principle seems significant, and this distinction may have some implications in terms of success: we’re already talking about others, not just running ideas in our own head.
  • what do you wish someone would make for you?
    • It’s somewhat different from the well-known “scratch your own itch” principle. In this difference might be located something significant. In a way, part of the potential for this version to lead to success comes from the fact that it’s already connected with others, instead of being about running ideas in your own mind.
  • grow organically
    • The core topic of the piece, put in a comparative context. The comparison isn’t the one people tend to make and one may argue about the examples used. But the concept of organic ideas is fascinating and inspiring.
  • you decide, from afar,
    • What we call, in anthropology, the “armchair” approach. Also known as “backbenching.” For this to work, you need to have a deep knowledge of the situation, which is part of the point in this piece. Nice that it’s not demonizing this position but putting it in context.
  • Apple
    was the first type
    • One might argue that it was a hybrid case. Although, it does sound like the very beginnings of Apple weren’t about “thinking from afar.”
  • class of users other than you
    • Since developers are part of a very specific “class” of people, this isn’t insignificant a way to phrase this.
  • They still rely on this principle today, incidentally.
    The iPhone is the phone Steve Jobs wants.
    • Apple tends to be perceived in a different light. According to many people, it’s the “textbook example” of a company where decisions are made without concerns for what people need. “Steve Jobs uses a top-down approach,” “They don’t even use focus groups,” “They don’t let me use their tools the way I want to use them.” But we’re not talking about the same distinction between top-down and bottom-up. Though “organic ideas” seem to imply that it’s a grassroots/bottom-up phenomenon, the core distinction isn’t about the origin of the ideas (from the “top,” in both cases) but on the reasoning behind these ideas.
  • We didn’t need this software ourselves.
    • Sounds partly like a disclaimer but this approach is quite common and “there’s nothing wrong with it.”
  • comparatively old
    • Age and life experience make for an interesting angle. It’s not that this strategy needs people of a specific age to work. It’s that there’s a connection between one’s experience and the way things may pan out.
  • There is no sharp line between the two types of ideas,
    • Those in the “engineering worldview” might go nuts, at this point. I can hear the claims of “hand waving.” But we’re talking about something complex, here, not a merely complicated problem.
  • Apple type
    • One thing to note in the three examples here: they’re all made by pairs of guys. Jobs and Woz, Gates and Allen, Page and Brin. In many cases, the formula might be that one guy (or gal, one wishes) comes up with ideas knowing that the other can implement them. Again, it’s about getting somebody else to build it for you, not about scratching your own itch.
  • Bill Gates was writing something he would use
    • Again, Gates may not be the most obvious example, since he’s mostly known for another approach. It’s not inaccurate to say he was solving his own problem, at the time, but it may not be that convincing as an example.
  • Larry and Sergey when they wrote the first versions of Google.
    • Although, the inception of the original ideas was academic in context. They weren’t solving a search problem or thinking about monetization. They were discovering the power of CitationRank.
  • generally preferable
    • Nicely relativistic.
  • It takes experience
    to predict what other people will want.
    • And possibly a lot more. Interesting that he doesn’t mention empirical data.
  • young founders
    • They sound like a fascinating group to observe. They do wonders when they open up to others, but they seem to have a tendency to impose their worldviews.
  • I’d encourage you to focus initially on organic ideas
    • Now, this advice sounds more like the “scratch your own itch” advocation. But there’s a key difference in that it’s stated as part of a broader process. It’s more of a “walk before you run” or “do your homework” piece of advice, not a “you can’t come up with good ideas if you just think about how people will use your tool.”
  • missing or broken
    • It can cover a lot, but it’s couched in terms of the typical “problem-solving” approach at the centre of the engineering worldview. Since we’re talking about developing tools, it makes sense. But there could be a broader version, admitting for dreams, inspiration, aspiration. Not necessarily of the “what would make you happy?” kind, although there’s a lot to be said about happiness and imagination. You’re brainstorming, here.
  • immediate answers
    • Which might imply that there’s a second step. If you keep asking yourself the same question, you may be able to get a very large number of ideas. The second step could be to prioritize them but I prefer “outlining” as a process: you shuffle things together and you group some ideas to get one which covers several. What’s common between your need for a simpler way to code on the Altair and your values? Why do you care so much about algorithms instead of human encoding?
  • You may need to stand outside yourself a bit to see brokenness
    • Ah, yes! “Taking a step back,” “distancing yourself,” “seeing the forest for the trees”… A core dimension of the ethnographic approach and the need for a back-and-forth between “inside” and “outside.” There’s a reflexive component in this “being an outsider to yourself.” It’s not only psychological, it’s a way to get into the social, which can lead to broader success if it’s indeed not just about scratching your own itch.
  • get used to it and take it for granted
    • That’s enculturation, to you. When you do things a certain way simply because “we’ve always done them that way,” you may not create these organic ideas. But it’s a fine way to do your work. Asking yourself important questions about what’s wrong with your situation works well in terms of getting new ideas. But, sometimes, you need to get some work done.
  • a Facebook
    • Yet another recontextualized example. Zuckerberg wasn’t trying to solve that specific brokenness, as far as we know. But Facebook became part of what it is when Zuck began scratching that itch.
  • organic startup ideas usually don’t
    seem like startup ideas at first
    • Which gets us to the pivotal importance of working with others. Per this article, VCs and “angel investors,” probably. But, in the case of some of cases cited, those we tend to forget, like Paul Allen, Narendra, and the Winklevosses.
  • end up making
    something of value to a lot of people
    • Trial and error, it’s an iterative process. So you must recognize errors quickly and not invest too much effort in a specific brokenness. Part of this requires maturity.
  • something
    other people dismiss as a toy
    • The passage on which Gruber focused and an interesting tidbit. Not that central, come to think of it. But it’s important to note that people’s dismissive attitude may be misled, that “toys” may hide tools, that it’s probably a good idea not to take all feedback to heart…
  • At this point, when someone comes to us with
    something that users like but that we could envision forum trolls
    dismissing as a toy, it makes us especially likely to invest.
  • the best source of organic ones
    • Especially to investors. Potentially self-serving… in a useful way.
  • they’re at the forefront of technology
    • That part I would dispute, actually. Unless we talk about a specific subgroup of young founders and a specific set of tools. Young founders tend to be oblivious to a large field in technology, including social tools.
  • they’re in a position to discover
    valuable types of fixable brokenness first
    • The focus on fixable brokenness makes sense if we’re thinking exclusively through the engineering worldview, but it’s at the centre of some failures like the Google Buzz launch.
  • you still have to work hard
    • Of the “inspiration shouldn’t make use forget perspiration” kind. Makes for a more thoughtful approach than the frequent “all you need to do…” claims.
  • I’d encourage anyone
    starting a startup to become one of its users, however unnatural it
    seems.
    • Not merely an argument for dogfooding. It’s deeper than that. Googloids probably use Google tools but they didn’t actually become users. They’re beta testers with a strong background in troubleshooting. Not the best way to figure out what users really want or how the tool will ultimately fail.
  • It’s hard to compete directly with open source software
    • Open Source as competition isn’t new as a concept, but it takes time to seep in.
  • there has to be some part
    you can charge for
    • The breach through which old-school “business models” enter with little attention paid to everything else. To the extent that much of the whole piece might crumble from pressure built up by the “beancounter” worldview. Good thing he acknowledges it.

Vague expérience

Brèves notes au sujet de #GoogleWave.

Bon, ça fait déjà quelques temps que je suis sur Google Wave alors il me faudrait commencer à parler de mon expérience. J’ai pris pas mal de notes et j’ai remarqué des tas de choses. Mais vaut mieux commencer par quelques petits points…

J’écrivais une réponse à une amie sur Facebook dont les amis tentaient d’en savoir plus à propos de Wave. Et ça m’a donné l’occasion de mettre quelques idées en place.

 

Wave est un drôle de système. Comme Twitter lors des premières utilisations, c’est difficile de se faire une idée. Surtout que c’est une version très préliminaire, pleine de bogues.

Jusqu’à maintenant, voici les ressources que j’ai trouvé utiles:
http://lifehacker.com/5376138/google-wave-101
http://danieltenner.com/posts/0012-google-wave.html

(Oui, en anglais. Je traduirai pas, à moins qu’il y ait de la demande.)

Le guide suivant risque en effet d’être le plus complet. Je l’ai pas encore lu…
http://completewaveguide.com/

Sinon, version relativement courte…
Wave est un outil de communication basé sur la notion que les participants à l’événement de communication (la discussion, dions) ont accès à un contenu centralisé. Donc, plutôt que d’échanger des courriels, on construit une “wave” qui peut contenir des tas de choses. On pense surtout au texte mais le contenu est très flexible.
Quelques forces…
– On passe du temps réel au mode asynchrone. Donc, on peut commencer une conversation comme si c’était un échange de courriels puis se faire une séance de clavardage dans le même contenu et retourner au mode courriel plus tard. Très utile et exactement le genre de truc dont plusieurs ont besoin, s’ils échangent des idées à propos de contenus.
– Comme Wiki, SubEthaEdit ou même Google Docs, c’est de l’écriture collaborative. Donc, on peut facilement construire du contenu avec plusieurs autres personnes. Le système permet un suivi plus facile que sur un Wiki ou avec Google Docs.
– La gestion des accès est incroyablement facile. En ce moment, on ne peut pas retirer quelqu’un qu’on a ajouté à une “wave”, mais c’est vraiment très facile de spécifier qui on veut ajouter comme participants à une “wave” ou même à une plus petite section. Donc, on peut conserver certaines choses plus privées et d’autres presque publiques. Ça semble simple, mais c’est assez important, comme changement. On peut créer des listes ad hoc comme si on décidait soudainement de faire équipe.
– C’est une architecture ouverte, avec la possibilité de créer des outils pour transformer les contenus ou pour ajouter d’autres choses (cartes, contenus interactifs, sondages…). Du genre widgets, mais ça va plus loin. Et ça motive le monde des développeurs. L’idée, c’est que le système permet d’être étendu de façon inattendue.
– C’est si nouveau et relativement limité dans le nombre d’utilisateurs qu’on en est à une phase où tout le monde essaie d’expérimenter et accepte de répondre à toute question.

– Il n’y a pour l’instant pas de pourriel.

Bon, c’est déjà pas si court… 😉

Si vous avez des questions, faites-moi signe. Si vous êtes déjà sur Wave, je suis enkerli et informalethnographer (dans les deux cas, c’est @googlewave.com).

Apps and iTunes Cards in Canada: Follow Up

Recently blogged about this issue: though information about this appears nowhere on the card or in the terms of service, iTunes Cards (gift cards or certificates) may not be used to purchase applications on the Canadian version of the iTunes Store.

Since I posted that blog entry, a few things have happened. I did receive replies from Apple, which were rather unhelpful. The most useful one was this message:

Hello Alexandre,

I understand and apologize about your situation and i do want to assist you as much as possible . I am going to issue you 10 song credit. Again i apologize and i hope this issue gets resolved. I will also apply feedback about this issue .

Thank you for choosing iTunes Store and have a great day.

Sincerely,

Todd
iTunes Store Customer Support

I had no intention of purchasing tracks on the iTunes Store at this point but I do “appreciate the gesture.” Here’s what I wrote back:

Thanks. I wasn’t planning on downloading songs but I appreciate the gesture.

Not overwhelming gratitude on my part. Simply stating that, though this isn’t appropriate, I can still be polite.

What’s funny is that I received this reply to my simple “thank you” note:

Dear Alexandre,

You’re very welcome. I’m glad to hear that i was able to help some .

Nothing makes Apple happier than to hear that we have pleased our customers. I hope that you continue to enjoy the iTunes Store.

Thank you for choosing iTunes Store and have a great day.

Sincerely,

Todd
iTunes Store Customer Support

From that message, you’d think I had praised the iTunes Store for hours on end.

Just in case it might make a difference, I tried filing another support request. Here’s the reply on that one:

Dear Alexandre,

Welcome to the iTunes Support Site. My name is Staci and I am here to assist you.

Thank you for contacting Apple about the App Store. We’re glad you’re interested in
this new offering.

I’m sorry, but you will not be able to purchase games or applications with store
credit or an iTunes Gift Card in Canada. Customers residing in Canada may only
purchase games and applications using a credit card.

I am confident that the information provided will solve your gift card issue. If
you have further questions, I can be contacted during the hours listed below. Thank
you and have a prosperous New Year.

Sincerely,

Staci
iTunes Stores Customer Support

This one sounds even more like a canned reply and  “the information provided” doesn’t, in fact, “solve [my] gift card issue.”

Clearly, Apple isn’t “doing the right thing.” In terms of customer service, it’s not a positive experience. I did enjoy some aspects of the iTunes Store and I think it’s quite convenient. But I’m not “enjoying the iTunes Store” so much, anymore.

In the meantime, I started receiving comments on my previous blogpost on the issue. One was from someone who purchased a 150$ iTunes Card. Almost as much as the 8GB iPod nano.

Most of the advice given on this issue, outside from Apple’s unhelpful replies, has to do with things which are illicit. One would be to resell tracks purchased with this card to other iTunes users. Since the tracks are now all DRM-free, this is technically feasible. But it’s also illicit and potentially traceable. Another piece of advice, to purchase applications using an iTunes Card, is to buy a card in the US. As far as I know, this is technically doable but it also contradicts Apple terms of service.

Not good solutions, but ones which disgruntled iTunes Card buyers may contemplate.

Since then, I also received a message asking me to complete a survey about my experience with Apple support. Here’s the complaint I included in that survey:

I was given the “runaround” on a very easy issue: I need a refund.
There’s an obvious problem with the fact that iTunes Cards may not be used to purchase applications on the Canadian version of the iTunes Store. Nowhere on the card itself or even in the Terms of Service is this restriction mentioned. As this issue gains prominence, Apple could get a significant hit in consumer perception. Not sure if it will become a class action lawsuit, but it’s as significant an issue.
Email replies were disappointingly unhelpful. Instead of investigating the situation, I was led to a forum post musing about the possible reasons for this restriction. I was eventually credited ten songs even though I had no intention of getting tracks on the iTunes Store at this point.
While the amount of money is relatively small in my case, I’m getting comments on my blog from people who lost the money equivalent of an iPod nano.

Again, I probably won’t file a class action lawsuit against Apple, in part because these suits mostly make money for lawyers. But my dissatisfaction with Apple remains. In a way, it even grows, because there were several opportunities for Apple to “do the right thing.” Yes, it’s partly on principle. But it’s also a matter of the way the corporation is perceived. In this case, they sound polite but quite dismissive.

There’s no question in my mind that a mistake was made: no information on this restriction was added anywhere a gift card purchaser may find it. Because of this, people are redeeming iTunes Cards with the specific intention of enjoying their iPhone or iPod touch in a new way. As this was a season of gift-giving, some people probably received these gift cards and, thinking they might use them anywhere on iTunes, redeemed these cards instead of returning them. Only to find out, after the fact, that “you will not be able to purchase games or applications with store credit or an iTunes Gift Card in Canada.”

Bummer.

This frustration isn’t such a big deal in the abstract. But context is everything. Part of the context is the set of restrictions placed by the iTunes Store in general. It may not have been much of an issue, for a given user, that it’s impossible to buy applications directly from developers, unlike Android Market (the Google equivalent to the App Store). For casual users, this is pretty much a non-issue, especially since the App Store is so convenient. But this restriction becomes quite conspicuous once an iPhone or iPod touch user runs into this kind of problem.

There’s a broader issue. With the iTunes Store, Apple is sometimes said to have “solved micropayment.” Ever since the iTunes Music Store opened, at least part of Apple’s success has been assigned to the Amazon-like way they implemented their payment structure and it’s quite likely that the iTunes Store model has been having positive effects on the way Apple is perceived by investors. Because of the way it handles payments and reduces overhead, Apple has been able to make money on relatively small amounts of 99¢ (and, recently, 69¢). I’d call this “minipayment” because one can easily imagine even smaller amounts being paid online (for instance, a minute of cellular or long-distance communication). In this case, Nokia, eBay/Skype, and cellphone carriers have better micropayment systems. But Apple still deserves “Wall Street cred” for the way it handles small payments.

Yet, once you start thinking about Apple’s payment system in more details, say because of a bad experience with the applications section of the iTunes Store, you start noticing how flimsy the payment structure is because it relies on users willingly entering a closed system. It’s not just that the iTunes Store is closed. It’s that, once you buy on Apple, you need to restrict yourself to “Apple’s ecosystem.” This has often been the case on a technical level. It’s now a matter more visible to the casual end user: money.

From a “tech media” perspective, this closed ecosystem is part of a pattern for Apple. But the financial part isn’t frequently discussed.

It will sound like a strange analogy but it’s the one with which I come up as I think about this: IKEA bedding. Because IKEA’s measurements are metric, bed linen was an issue with IKEA-purchased mattresses in Canada. Not sure if it’s still the case but it used to be that those who bought beds at IKEA were then stuck with metric measurements for bed linen and those are difficult to find in Canada. In effect, those who purchased beds at IKEA were restricted to IKEA linen.

In computer terms, the classic case is that of a difference in fileformat between products from two developers. Apple certainly had its share of “format wars” but it mostly solved these issues. Recent Macs (including the Mac mini Intel Core Duo I’m currently using) support a Windows installation as well as Mac OS X. In terms of networking, it’s now quite easy to set up mixed networks with both Mac OS X and Windows machines. Even the music part of the iTunes Store is lifting those restrictions which made them technically incompatible with other devices. All in all, Apple has gone away from its strict control, at least in technical terms.

But in financial terms, Apple is using a fairly restrictive model for its iTunes Store. Once money gets into an account (through gift cards, allowances, or “gifting”), it can only be used on that account. Because of some restrictions specific to Canada, some of that money is restricted from use for buying applications. And Paypal isn’t available as a payment option in the Canadian iTunes Store. In effect, the only way to purchase an application for the iPhone or iPod touch is through a valid credit card. Given the fact that a majority of people are likely to have some kind of credit card, this doesn’t seem too restrictive. But there’s a variety of reasons people may not have valid credit cards and there’s no connection between buying something on the App Store and using a credit card. The iPod touch has been marketed as a gaming platform during the holidays and chances are that some iPod touch owners are children without credit cards. I’m not sure what the options are for them to buy iPod touch games. The same could be said about games for the iPod Classic, a device which clearly is used by children.

Part of the problem relates to the Canadian financial system. For one thing, debit cards with credit card numbers are rare in Canada (I’m not sure they exist). Many Canadians tend to use Interac, which does offer some advantages over credit cards, IMHO. As I’ve recently experienced, Interac now works online. It would make a lot of sense for Apple to support it online (I’m sure Canadian Apple Stores already support it). And there must be a reason Paypal, which can be used for iTunes Store purchases in the US, is unavailable in the Canadian iTunes Store.

So, yet again, Apple’s Canadian customers appear “underprivileged” by comparison with US customers. In public perception, this is pretty much a pattern for Apple.

I don’t think that the messages I’ve received helped. Though they were polite, they were dismissive as my problem was basically dismissed. From being dismissive, Apple can sound arrogant. And arrogance is tricky, in today’s marketplace.

I’m reminded of the recent Simpsons episode about Apple. Excerpts of it made their way to YouTube as they play on several gripes people have with Apple. Arrogance was clearly a key theme in that episode. Another Apple parody, the MacBook Wheel spoof from The Onion, was more directly centred on making fun of users and elements related to Apple’s perceived arrogance were less obvious.

I don’t own AAPL.0 stock but, if I did, I might sell some. Sounds silly but corporations which treats its customers in this way aren’t something I would invest in. Despite the fact that I do “invest” in Apple products.

I just wish Apple “did the right thing.”

How Do I Facebook?

In response to David Giesberg.

How Do You Facebook? | david giesberg dot com

How have I used Facebook so far?

  • Reconnected with old friends.
    • Bringing some to Facebook
    • Noticing some mutual friends.
  • Made some new contacts.
    • Through mutual acquaintances and foafs.
    • Through random circumstances.
  • Thought about social networks from an ethnographic perspective.
    • Discussed social networks in educational context.
    • Blogged about online forms of social networking.
  • “Communicated”
    • Sent messages to contacts in a relatively unintrusive way (less “pushy” than regular email).
    • Used “wall posts” to have short, public conversations about diverse items.
  • Micro-/nanoblogged, social-bookmarked:
    • Shared content (links, videos…) with contacts.
    • Found and discussed shared items.
    • Used my “status update” to keep contacts updated on recent developments on my life (something I rarely do in my blogposts).
  • Managed something of a public persona.
    • Maintained a semi-public profile.
    • Gained some social capital.
  • Found an alternative to Linkup/Upcoming/MeetUp/GCal?
    • Kept track of several events.
    • Organized a few events.
  • Had some aimless fun:
    • Teased people through their walls.
    • Answered a few quizzes.
    • Played a few games.
    • Discovered bands through contacts who “became fans” of them (I don’t use iLike).

Less Than 30 Minutes

Nice!

At 20:27 (EST) on Saturday, November 17, 2007, I post a blog entry on the archaic/rare French term «queruleuse» (one equivalent of “querulous”). At 20:54 (EST) of the same day, Google is already linking my main blog page as the first page containing the term “queruleuse” and as the fourth page containing the term “querulente.” At that point in time, the only other result for “queruleuse” was to a Google Book. Interestingly enough, a search in Google Book directly lists other Google Books containing that term, including different versions of the same passage. These other books do not currently show up on the main Google search for that term. And blogs containing links to this blog are now (over two hours after my «queruleuse» post) showing above the Google Book in search results.

Now, there’s nothing very extraordinary, here. The term «queruleuse» is probably not the proper version of the term. In fact, «querulente» seems a bit more common. Also, “querulous” and “querulent” both exist in English, and their definitions seem fairly similar to the concept to which «queruleuse» was supposed to refer. So, no magic, here.

But I do find it very interesting that it takes Google less than a half hour for Google to update its database to show my main page as the first result for a term which exists in its own Google Books database.

I guess the reason I find it so interesting is that I have thought a bit about SEO, Search Engine Optimization. I usually don’t care about such issues but a couple of things made me think about Google’s PageRank specifically.

One was that someone recently left a comment on this very blog (my main blog, among several), asking how long it took me to get a PageRank of 5. I don’t know the answer but it seems to me that my PageRank hasn’t varied since pretty much the beginning. I don’t use the Google Toolbar in my main browser so I don’t really know. But when I did look at the PR indicator on this blog, it seemed to be pretty much always at the midway point and I assumed it was just normal. What’s funny is that, after attending a couple Yulblog meetings more than a year ago, someone mentioned my PageRank, trying to interpret why it was so high. I checked that Yulblogger’s blog recently and it has a PR of 6, IIRC. Maybe even 7. (Pretty much an A-List blogger, IMHO.)

The other thing which made me think about PageRank is a discussion about it on a recent episode of the This Week in Tech (TWiT) “netcast” (or “podcast,” as everybody else would call it). On that episode, Chaos Manor author Jerry Pournelle mused about PageRank and its inability to provide a true measure of just about anything. Though most people would agree that PageRank is a less than ideal measure for popularity, influence, or even relevance, Pournelle’s point was made more strongly than “consensus opinion among bloggers.” I tend to agree with Pournelle. 😉

Of course, some people probably think that I’m a sore loser and that the reason I make claims about the irrelevance of PageRank is that I’d like to get higher in a blogosphere’s hierarchy. But, honestly, I had no idea that PR5 might be a decent rank until this commenter asked me about. Even when the aforementioned Yulblogger talked about it, I didn’t understand that it was supposed to be a rather significant number. I just thought this blogger was teasing (despite not being a teaser).

Answering the commenter’s question as to when my PR reached 5, I talked about the rarity of my name. Basically, I can always rely on my name being available on almost any service. Things might change if a distant cousin gets really famous really soon, of course… ;-) In fact, I’m wondering if talking about this on my blog might push someone to use my name for some service just to tease/annoy me. I guess there could even be more serious consequences. But, in the meantime, I’m having fun with my name’s rarity. And I’m assuming this rarity is a factor in my PageRank.

Problem is, this isn’t my only blog with my name in the domain. One of the others is on Google’s very own Blogger platform. So I’m guessing other factors contribute to this (my main) blog’s PageRank.

One factor is likely to be my absurdly long list of categories. Reason for this long list is that I was originally using them as tags, linked to Technorati tags. Actually, I recently shortened this list significantly by transforming many categories into tags. It’s funny that the PageRank-interested commenter replied to this very same post about categories and tags since I was then positing that the modification to my categories list would decrease the number of visits to this blog. Though it’s hard for me to assess an actual causal link, I do get significantly less visits since that time. And I probably do get a few more comments than before (which is exactly what I wanted). AFAICT, WordPress.com tags still work as Technorati tags so I have no idea how the change could have had an impact. Come to think of it, the impact probably is spurious.

A related factor is my absurdly long blogroll. I don’t “do it on purpose,” I just add pretty much any blog I come across. In fact, I’ve been adding most blogs authored by MyBlogLog visitors to this blog (those you see on the right, here). Kind of as a courtesy to them for having visited my blog. And I do the same thing with blogs managed by people who comment on this blog. I even do it with blogs by pretty much any Yulblogger I’ve come across, somehow. All of this is meant as a way to collect links to a wide diversity of blogs, using arbitrary selection criteria. Just because I can.

Actually, early on (before I grokked the concept of what a blogroll was really supposed to be), I started using the “Link This” bookmarklet to collect links whether they were to actual blogs or simply main pages. I wasn’t really using any Social Networking Service (SNS) at that point in time (though I had used some SNS several years prior) and I was thinking of these lists of people pretty much the same way many now conceive of SNS. Nowadays, I use Facebook as my main SNS (though I have accounts on other SNS, including MySpace). So this use of links/blogrolls has been superseded by actual SNS.

What has not been superseded and may in fact be another factor for my PageRank is the fact that I tend to keep links of much of the stuff I read. After looking at a wide variety of “social bookmarking systems,” I recently settled on Spurl (my Spurl RSS). And it’s not really that Spurl is my “favourite social bookmarking system evah.” But Spurl is the one system which fits the most in (or least disrupts) my workflow right now. In fact, I keep thinking about “social bookmarking systems” and I have lots of ideas about the ideal one. I know I’ll be posting some of these ideas someday, but many of these ideas are a bit hard to describe in writing.

At any rate, my tendency to keep links on just about anything I read might contribute to my PageRank as Google’s PageRank does measure the number of outgoing links. On the other hand, the fact that I put my Spurl feed on my main page probably doesn’t have much of an impact on my PageRank since I started doing this a while after I started this blog and I’m pretty sure my PageRank remained the same. (I’m pretty sure Google search only looks at the actual blog entries, not the complete blog site. But you never know…)

Now, another tendency I have may also be a factor. I tend to link to my own blog entries. Yeah, I know, many bloggers see this as self-serving and lame. But I do it as a matter of convenience and “thought management.” It helps me situate some of my “streams of thought” and I like the idea of backtracking my blog entries. Actually, it’s all part of a series of habits after I started blogging, 2.5 years ago. And since I basically blog for fun, I don’t really care if people think my habits are lame.

Sheesh! All this for a silly integer about which I tend not to think. But I do enjoy thinking about what brings people to specific blogs. I don’t see blog statistics on any of my other blogs and I get few enough comments or trackbacks to not get much data on other factors. So it’s not like I can use my blogs as a basis for a quantitative study of “blog influence” or “search engine relevance.”

One dimension which would interesting to explore, in relation to PageRank, is the network of citations in academic texts. We all know that Brin and Page got their PageRank idea from the academic world and the academic world is currently looking at PageRank-like measures of “citation impact” (“CitationRank” would be a cool name). I tend to care very little about the quantitative evaluation of even “citation impact” in academia, but I really am intrigued by the network analysis of citations between academic references. One fun thing there is that there seems to be a high clustering coefficient among academic papers in some research fields. In some cases, the coefficient itself could reveal something interesting but the very concept of “academic small worlds” may be important to consider. Especially since these “worlds” might integrate as apparently-coherent (and consistent) worldviews.

Groupthink, anyone? 😉

Android “Sales Pitch” and “Drift-Off”

(Google’s Android is an open software platform to be put on cellphones next year.)

There’s something to this video. Something imilar to Steve Jobs’s alleged “Reality Distortion Field,” but possibly less connected to presentation skills or perceived charisma. Though Mike seems to be a more experienced presenter than those we see in other videos about Android, and though the presentation format is much slicker than other videos about Android, there’s something special about this video, to me.

For one thing, the content of the three “Androidology” videos are easy to understand, even for a non-developer/non-coder. Sure, you need to know some basic terms. But the broad concepts are easy to understand, at least for those who have been observing the field of technology. One interesting thing about this is that these “Androidology” videos are explicitly meant for software programmers. The “you” in this context specifically refers to would-be developers of Android applications. At the same time, these videos do a better job, IMHO, of “selling Android to tech gurus” than other Android-related videos published by Google.

Now, I do find this specific video quite interesting, and my interest has to do with a specific meaning of “sales pitch.”

I keep going back to a Wired article about the “drift-off moment” during sales pitches (or demos):

When Mann gives a demo, what he’s waiting for is what salespeople call “the drift-off moment.” The client’s eyes get gooey, and they’re staring into space. They’re not bored – they’re imagining what they could do with SurveyBuilder. All tech salespeople mention this – they’ve succeeded not when they rivet the client’s attention, but when they lose it.

I apply this to teaching when I can and I specifically talked about this during a presentation about online tools for teaching.

This video on four of Android’s APIs had this effect on me. Despite not being a developer myself, I started imagining what people could do with Android. It was just a few brief moments. But very effective.

The four APIs discussed in this video are (in presentation order):

  1. Location Manager
  2. XMPP Service
  3. Notification Manager
  4. View System (including MapView and WebView)

Mike’s concise (!) explanations on all of these are quite straightforward (though I was still unclear on XMPP and on details of the three other APIs after watching the video). Yet something “clicked” in my mind while watching this. Sure, it might just be serendipitous. But there’s something about these APIs or about the way they are described which make me daydream.

Which is exactly what the “drift-off moment” is all about.

Technorati Tags: , , , , , , , , , , , , , , , , ,

How Can Google Beat Facebook?

It might not be so hard:

As I see it, the biggest shortcoming of social-networking sites is their inability to play well with others. Between MySpace, Facebook, LinkedIn, Tribe, Pownce, and the numerous also-rans, it seems as if maintaining an active presence at all of these sites could erode into becoming a full-time job. If Google can somehow create a means for all of these services to work together, and seamlessly interact with the Google family, then perhaps this is the killer app that people don’t even realize they’ve been waiting for. Google gives social networking another go | Media Sphere – Josh Wolf blogs about the new information age – CNET Blogs

Some might take issue at Wolf’s presumption. Many of us have realised in 1997 that the “killer app” for social networking services is for them to work together. But the point is incredibly important and needs to be made again and again.

Social Networking Services work when people connect through it. The most intricate “network effect” you can think of. For connections to work, existing social relationships and potential social relationships need to be represented in the SNS as easily as possible. What’s more, investing effort and time in building one’s network relates quite directly with the prospective life of SNS. Faced with the eventuality of losing all connections in a snap because everybody has gone to “the next thing,” the typical SNS user is wary. Given the impression that SNS links can survive the jump to “the next one” (say, via a simple “import” function), the typical SNS user is likely to use the SNS to its fullest potential. This is probably one of several reasons for the success of Facebook. And Google can certainly put something together which benefits from this principle.

Yeah, yeah, Wolf  was referring more specifically to the “synchronisation” of activities on different SNS or SNS-like systems. That’s an important aspect of the overall “SNS interoperability” issue. Especially if SNS are important parts of people’s lives. But I prefer to think about the whole picture.

Another thing which has been mentioned is the connection Google could make between SNS and its other tools. One approach would be to build more “social networking features” (beyond sharing) into its existing services. The other could be to integrate Google tools into SNS (say, top-notch Facebook applications). Taken together, these two approaches would greatly benefit both Google and the field of social networking in general.

All in all, what I could easily see would be a way for me to bring all my SNS “content” to a Google SNS, including existing links. From a Google SNS, I would be able to use different “social-enabled” tools from Google like the new Gmail, an improved version of Google Documents, and the Blogger blogging platform. Eventually, most of my online activities would be facilitated by Google but I would still be able to use non-Google tools as I wish.

There’s a few tools I’m already thinking about, which could make sense in this “Google-enabled social platform.” For one, the “ultimate social bookmarking tool” for which I’ve been building feature wishlists. Then, there’s the obvious need for diverse applications which can use a centralised online storage system. Or the browser integration possible with something like, I don’t know, the Google toolbar… 😉

Given my interest in educational technology, I can’t help but think about online systems for course management (like Moodle and Sakai). Probably too specific, but Google could do a wonderful job at it.

Many people are certainly thinking about advertisement, revenue-sharing, p2p for media files, and other Google-friendly concepts. These aren’t that important for me.

I can’t say that I have a very clear image of what Google’s involvement in the “social networking sphere” will look like. But I can easily start listing Google products and features which are desperately calling for integration in a social context: Scholar, Web History, Docs, Reader, Browser Sync, Gcal, Gmail, Notebook, News, Mobile, YouTube, Ride Finder, Blog Comments, Music Trends, University Search, MeasureMap, Groups, Alerts, Bookmarks…

Sometimes, I really wonder why a company like Google can’t “get its act together” in making everything it does fit in a simple platform. They have the experts, the money, the users. They just need to make it happen.

Ah, well…