I Hate FTP [en]

[fr] Je hais le FTP. Donnez-moi un accès SSH et screen sur le serveur, et me voilà heureuse.

Ever since I discovered the magical combination of SSH + screen, I have come to loathe FTP. Although some of you will cringe at the idea, I like working directly on the server. No stray copies lying around, dated I-don’t-know-what. No chance of mistakenly overwriting your last set of changes.

Screen is a terminal multiplexer (just learned the term). What you do, basically, is climb inside it when you’re on the server, and do everything from there. The advantage is that:

  • when you disconnect your SSH connection, screen keeps running, so your workspace is how you left it next time you come in
  • you can have multiple “screens” (ie, terminal windows) you can easily switch around, so you can have your IRC channel running in one screen, be editing a file in another, etc. (basically, multi-tasking like you would do with windows in a graphical environment).

I learnt shell commands as I went along. Those I use the most are:

  • wget http://wordpress.org/latest.zip to download (instantly!) the latest version of WordPress directly on the server
  • unzip latest.zip to unzip it, still directly on the server
  • mv wp old-200910 to archive an old installation of wordpress (or move other files around)
  • cp -Rf plugins/* ../../wordpress/wp-content/plugins/ to copy all my plugins to the freshly unzipped install of WordPress
  • nano wp-config-sample.php to add my settings to the file and save it as wp-config.php

These are just a few examples. Once you know these commands and have them at the tip of your fingers, how fast you work is only limited by how fast you can type them. And you’re doing things directly on the web server. You’re not stuck looking at the “real world” (= the server) through the imperfect lens of an FTP client, waiting for uploads to happen (or downloads), paying attention not to overwrite stuff, having everything ready on your computer before pressing the magic button and hoping everything will be all right, because otherwise you’re in for another bout of download, edit, upload…

Some of my clients have WordPress installations on servers with no shell access. Obviously, I don’t have as much practice doing things the FTP way, but I swear it takes me 5 times as much time to do things with no SSH access. When you know how to use it, the command-line is wickedly fast.

The only situation where I actually do like FTP is when I’m using CSSEdit, because coupled to an FTP client, I can be editing my CSS file with the added power of the programme on my Mac, and have it upload and update the file on the server each time I hit save. Because yes, it’s nicer to write CSS in CSSEdit than in nano.

But for managing files and moving them around and minor edits… I’m much happier sitting on my server inside my screen.

Bloguer en français ou en anglais? [fr]

[en] I write a weekly column for Les Quotidiennes, which I republish here on CTTS for safekeeping.

Chroniques du monde connecté: cet article a été initialement publié dans Les Quotidiennes (voir l’original).

Les blogueurs qui se lancent se demandent souvent dans quelle langue il vaut mieux bloguer, pour autant qu’il en aient plus d’une à disposition. Dans notre région, le choix à faire est généralement entre le français, langue maternelle, et l’anglais, langue internationale.

On se dit que bloguer en anglais permettra de toucher un plus grand public.

Parce que oui, bloguer, c’est en général pour être lu. On cherche un peu de reconnaissance, ou à établir son expertise dans un domaine qui nous passionne. Alors bien sûr, c’est légitime, on veut mettre toutes les chances de notre côté. Et on se demande à juste titre dans quelle langue écrire.

En fait, écrire en anglais est probablement une fausse bonne idée, surtout si l’on ne cherche pas à tout prix à atteindre un public international: plus la mare est grande, plus il y a de gros poissons dedans. La concurrence sera plus rude dans une langue majoritaire que dans une langue minoritaire. Plus facile, donc, de faire son trou dans une langue qui n’est pas déjà saturée de blogs sur le sujet qui nous tient à coeur, particulièrement si l’on est plus habile avec.

Le blogueur, même populaire, n’atteindra toujours qu’une infime fraction des lecteurs potentiels dans la langue qu’il utilise. Ce n’est pas la taille de la mare qui est le facteur limitant, mais bien le nombre de poissons qui nagent dedans.

Reste qu’on peut toujours décider de rejeter les frontières linguistiques en mélangeant plusieurs langues sur un blog… mais ça c’est une autre histoire

Agenda: La conférence internationale Lift, portant sur des sujets mêlant technologie et société, et qui a lieu chaque année a Genève (5-7 mai 2010) offre jusqu’au 26 décembre son billet d’entrée à moitié prix. Ne manquez pas de vous y inscrire sans tarder si ce thème vous interpelle.

WPML to Make Your WordPress Site Multilingual [en]

[fr] A tester absolument si vous devez mettre en place un site multilingue: le plugin WPML pour WordPress.

I’ve been wanting to play with the WPML WordPress plugin for a while now, and I finally took the plunge today and updated my professional site to the latest version of WordPress, as well as WPML. (Sadly, the content still needs a major overhaul.)

Until now, I had built it using two separate WordPress installations, one in English, one in French, linked together by my quick-and-dirty plugin Bunny’s Language Linker (which, in the light of today’s experiment, I will be retiring from rather inactive development — Basic Bilingual remains, though, and still very much makes sense).

Here’s a summary of what I did:

  • backed up my database
  • upgraded both WordPress blogs to the latest version and exported their content
  • removed the automatic language redirection based on browser language preferences to make sure it wouldn’t interfere (I want to find a way to insert it back in, help appreciated)
  • added and activated the WPML plugin on the English installation
  • went through the settings after activating advanced mode
  • translated widget text and site tagline
  • manually imported content from the French site (import failed due to PHP on my server not being compiled with ctype_digit()), but it was only a dozen pages — it’s easy to specify language and of which English page a new one is a translation of, if any)

Setting up WPML

I did encounter some grief:

  • when selecting the “different languages in directories” I kept getting an error message which didn’t make much sense to me; tip: if that happens, make sure that your site and pages all work fine (in my case, I had to reset permalink structure because it had got lost somewhere on the way — even though the settings didn’t change)
  • I’m using a theme with an existing .mo file for French, so I selected that option (to figure out what the textdomain is, look through a theme file to see what the second argument to the gettext calls is — they look like __("Text here", "text domain here")) but it seems that all the strings for my theme still appear in the “string translation” pane
  • initially the strings for my widgets and site tagline weren’t appearing in the “string translation” pane — you have to click the “Save options and rescan strings” button for that, even if you haven’t changed any settings (that was not exactly obvious to me)

Here’s what I still need to fix:

  • the rewrite rules are set to hide the “language directory” part of the URL when browsing the site in the default language — I want to change this as explained in this forum post
  • reimplement automatic language detection
  • set up a custom language switcher that looks more like “Français | English” somewhere at the top right of the page

And honestly, once that is settle, WPML is as close as it gets to my dream multilingual plugin for WordPress!

Get Your Lift10 Ticket Half-Price Before Christmas [en]

[fr] Vous savez certainement que Lift, à Genève (5-7 mai 2010) est un des événements incontournables du milieu de la technologie en Europe. Une conférence non-commerciale, qui vous donnera matière à penser pour l'année à venir et ouvrira des portes dans votre tête dont vous ignoriez l'existence jusqu'ici. Trois jours pour 650.- (220.- par jour!) si vous vous inscrivez avant le 26 décembre. (Comparez ça aux tarifs des formations usuelles, et vous avez un prix imbattable pour du contenu inégalable.)

The reasons I gave for attending Lift nearly two years ago are still very much true. In all honesty, if there is one European tech event you should absolutely attend each year, it’s the Lift Conference in Geneva. This year, unlike the previous ones, it will take place in May (5-7th) — much nicer weather than February!

Lift10 conference in Geneva, May 5-7, 2010. In a nutshell, Lift is 3 days of extraordinary speakers you have not heard before a dozen times already, a very diverse gathering of smart and interesting attendees, various presentation formats in addition to keynotes like discussions, workshops, open stage presentations (part of the programme is community-contributed), rich hallway conversations, and a very uncommercial feel to it all.

But don’t stop there, please do read my post from two years ago, then come back. I’ve attended the conference since it started, so you might want to read some of my posts covering it (2006, 2007, 2008, 2009) — and all the videos of past talks are available freely online.

Another thing that has changed since last year besides the date is the conference pricing, which has gone up significantly for those who do not register early. Laurent wrote a really great post about the challenges encountered in pricing an event like Lift, which tries to attract attendees with different profiles and very different budgets: be too expensive, and people without an employer behind them to pay for the ticket can’t come — but be too cheap, and you’re not taken seriously (which tends to be the problem Lift has faced over the years).

Actually, anybody who provides services to a client base which is not homogeneous are faced with this dilemma, which is one of the reasons my rates (for example) vary according to which client I’m providing services to — shocking thought it may seem to some (upcoming blog post about that, by the way).

So, the good news is that if you have your ears and eyes open, and know that you’re going to Lift in 2010, you can get in for 650.- CHF (50% of the final ticket price) if you register before December 26th.

Students can apply to get one of the 20 free tickets that are reserved for them (deadline January 15th).

Journalists and bloggers should apply for a media pass.

I really hope to see you at Lift. You won’t regret it.

Conversation in Comments vs. Conversation in Twitter [en]

[fr] Twitter n'est pas en train de tuer les conversations dans les commentaires des blogs. Le bavardage s'est déplacé dans Twitter, Friendfeed, Facebook -- mais quand certains disent que la conversation y est meilleure, ils ignorent le fait qu'il y a plusieurs sortes de conversation.

Hey, another “vs.” post! It must be because I get tired quickly of people comparing apples and oranges, and saying that we’re not going to eat apples anymore because we now have oranges.

A good year and a half ago there was some talk around the fact that the conversation had moved out of blogs and into Twitter and Friendfeed.

That’s not quite true: some of the conversation has moved from blog comments into the stream. The chatter, mainly.

Just like, when comments first started appearing on weblogs (remember those times, folks?) — well, some of the conversation that was happening from blog post to blog post moved into the comments.

But there was already conversation. Blogs without comments are still blogs.

So, what has happened? The more immediate, chat-like conversation has indeed moved out of blog comments and into Twitter, Facebook, and Friendfeed-like services. The short one-liners. But the real value-adding comments, those that make the conversation meaningful, those that actually discuss in depth what the blogger wrote, or contribute something beyond “great post” or “load of horseshit” — those are still there in our blog comments.

I see a parallel here with the distinction I make between live-tweeting and live-blogging. I’m not anti-Twitter or anti-anything: I love Twitter, and use it for more than my fair share of chatter. But the chatter of today most often has lost its appeal tomorrow, and will not take the place of deep conversation that one can catch up with even once it has gone cold.

This, by the way, is also the root of my dislike of threaded conversations on blogs.

Interaction Space [en]

[fr] Ce qui compte, c'est qui est dans notre "espace d'interaction", autrefois délimité par l'espace physique autour de nous. Il n'y a rien de mal à attendre le bus au téléphone avec un ami plutôt qu'en échangeant des mondanités pataudes avec les inconnus qui se trouvent à l'arrêt.

At the bus stop, I’m listening to music on my iPhone and the two other women waiting are talking on the phone, smiling, but not to each other. That’s when I understand: what’s important is who is in your “can interact” space, not who is in your physical space.

Physical co-presence used to be important because it defined who you could interact with. That is not true anymore: your interaction space is not limited to your physical space.

There’s nothing bad about being on the phone with a friend rather than exchanging awkward mundanities with strangers at the bus stop.

Live-Blogging vs. Live-Tweeting at Conferences [en]

[fr] Live-tweeter une conférence, c'est l'équivalent d'être actif dans le backchannel IRC de la belle époque des conférences de blogs. Il n'y a rien de mal à ça, mais il ne faut pas confondre ça avec le live-blogging: en effet, passés quelques jours, semaines, mois ou même années, qui va replonger son nez dans le fouillis des tweets ou des logs IRC de telle ou telle journée? Comparez ça avec un article sur un blog, qui sera lu, relu, et encore relu -- qui conserve donc sa valeur une fois que l'excitation du temps réel est passée.

One of the things bloggers brought with them when they started attending conferences is live coverage. Unlike the traditional press, which would provide you with a summary of the proceedings the next day, bloggers would be madly photographing, taking notes, uploading, and hitting publish in the minutes following the end of a presentation.

Live-blogging was born.

(For my personal history with it, see my BlogTalk 2.0 posts (2004) about collaborative note-taking using SubEthaEdit and a wiki, and my notes of LIFT06 (2006). Real proper live-blogging had to wait until LIFT’07 and Martin Roell’s workshop on getting started with consulting (2007), however.)

Then Twitter showed up, and everybody started a-tweeting, and more particularly live-tweeting during conferences.

But live-tweeting does not replace live-blogging. It replaces the IRC backchannel, allowing people to comment on what is going on as it happens, and letting people who are not physically present take part in the fun.

(I’m not going to talk about backchannels here: they’re great, but can also have unpleasant consequences in certain situations. A whole series of blog posts could be devoted to them.)

So when bloggers at conferences neglect their blogs and spend all their time live-tweeting, they are in fact fooling around in the backchannel instead of doing what bloggers do, which is produce content which retains value months, sometimes years, after it was published.

Don’t get me wrong: live-tweeting is fine, so is participation in a more traditional IRC-based backchannel. But don’t confuse it with live-blogging.

Tweets of the moment, just like IRC conversations, tend to be great when consumed in real time. But as the days and weeks go by, they become just as pleasant to read as an IRC log. (Understand: not pleasant at all.)

So, dear bloggers, when you’re at a conference to provide coverage, do not forget who you are. Not everybody is a live-blogger, of course, and some produce very valuable writing about an event they attended once they are home and have allowed the dust to settle.

But tweeting does not replace blogging.

Do you think I got my point across, now? 😉

A Quick Thought on Being Public [en]

[fr] Dans un monde où l'on est des personnages de plus en plus publics, s'adressant simultanément à des publics jadis séparés, on peut pour moi soit se réfugier dans la langue de bois pour ne heurter personne, soit se mettre les gens à dos en leur disant en face des choses qu'on aurait auparavant évité qu'ils entendent, soir jouer de l'équilibrisme en privilégiant l'honnêté exprimée d'une manière qui prend soin des sentiments des autres.

In these days of increasingly overlapping publics, I see three ways in which to deal with the fact that we are all becoming — to some extent — public figures, our multiple faces forced to come together as the publics they’re meant for also do:

  • go all tongue-tied and diplomatic, and dumb down your discourse so nobody can take offence or hear something they shouldn’t;
  • be an asshole, by saying things to people’s faces that one normally would keep for behind their backs;
  • walk the fine line of honesty and respect whilst expressing things in a way that cares for others’ feelings.

The third way, clearly, is the most challenging, but probably also the most rewarding from the point of view of personal growth.

LeWeb'09: danah boyd [en]

Live notes from LeWeb’09. They could be inaccurate, although I do my best. You might want to read other posts by official bloggers, in various languages!

What you see online is not what others see online. It’s mediated through your friends.

How do we get a sense of our norms? Not through our audience, but through the people we follow. What we see gives us our sense of going on, rather than who sees us.

We’re not on the same internet as the average teen.

We have the ability to look in on people’s lives, a very powerful thing about the web. But lots of people don’t look.

Funny things that danah does is searching Twitter for “the” or random words to see what comes up. Even better in another language. => different kinds of environments.

Three case studies about visibility and what we see. Assumptions about what people see/do online that need questioning.

1. College admissions

MySpace, early on, college admissions officer calls danah about this young man who wrote a beautiful essay about wanting to leave the gang world, but his MySpace seemed to tell a different story. Interesting question: why do they lie to college admissions officers, and put the truth online? They’re not lying, just different ways of describing oneself in different parts of our lives to survive. Gang profile on MySpace to survive. Interesting: admissions officer assumes he is lying! Two different context, neither the kid or the officer knows how to deal with it.

2. Parental access

MySpace girl invited her dad to be her friend, but dad saw she took a test “what drug are you?” — cocaine. He did the good thing, talked to her. Asked her. “Dad, just one of these quizzes!” Having the conversation, opening up. Dad made the decision not to make assumptions based on what he saw, but to start conversations.

3. Violence

Young woman in Colorado murders her mother. American press: “girl with MySpace kills mother”. On her profile, detailed descriptions of how her mother abused her. It was documented but nobody did anything. Heartbreaking.

Just because it’s visible doesn’t mean people will see it or do anything about it.

We can be very visible, but nobody is looking. What does it mean to be public? Who is looking, and why are they looking?

Those who are looking are those who hold power over those observed. “If it’s public, I’m allowed to look!” => great conversations around privacy. Surveillance.

Flip it around: when should we be looking when we are not? Should we be looking to see a world different than ours? Jane Jacobs (?): “Eyes on the street.” Look at what is going on. One of the best ways to keep the community safe. Somebody is aware of what’s going on when a kid falls off his bicycle.

When should we be creating eyes on the street?

Privacy is used often to justify why we aren’t looking at things. Last 3 years: shift about how we think about domestic violence. 60s: didn’t exist. Can do what you want at home. Now: right to safety in private space. We use privacy to deal with when people are hurt in public spaces.

Lots of kids crying out for help online.

Transparency, visibility: the best and the worst is made available.

Bullying: lots of parents are afraid of technology because they fear it creates new dangers or situations. Data shows that bullying is not more present today than before, but it is much more visible.

Challenge: we can see when kids are hurt. Parents who don’t understand the technology blame the technology, when the technology is just making the problem visible. Call to action.

People move to gated communities to get away from different people and not have to deal with them but the internet is bringing all these people together. We might not want to be in such a mixed space.

BET: on Twitter, all the trending topics were black icons in America. And then also, critique of black culture, it’s full of black topics in Twitter. Reaction. How do we deal with this?

TV news often takes power by making us uncomfortable, showing us what we don’t like. But recently, showing us more what we want to see. And now, what happens when we’re forced to see what we don’t want?

Looking at the darker side of youth-generated content. But there is nobody to turn to. Legal? Easy to get the police involved, but not about social services, etc?

We’re making all sorts of parts of society visible, parts we like and others we don’t. Ramifications of doing this. How do we deal with this visibility of hurtful and harmful things? It doesn’t have to be illegal…

Content Curation: Pearltrees, SmallRivers [en]

[fr] Tentative d'utilisation de Pearltrees et SmallRivers. Ça semble intéressant mais pour le moment j'ai l'impression que soit quelque chose m'échappe, soit qu'ils sont en train de réinventer la roue.

If you’re at LeWeb’09, you’ve heard of Pearltrees. They’re offering an interface/platform to help people curate web content by collecting it (bookmarking it?) in the shape of “pearls”. SmallRivers are a Lausanne startup which are also in the content curating business, by allowing people to network pages together by inserting some code in the page.

I’m trying both, unfortunately with not exactly enough energy and time to do it properly. But I already have a few comments.

In a way, this kind of content curation is already possible. Blogs, wikis, and even stupid old webpages with hypertext (hypertext!) allow this. So, is the revolution simply in the interface? In some element of social auto-discovery? Part of me is excited by new services in this space, but I’m also pretty skeptical. Is this just reinventing the wheel in a pretty wrapping?

The question I always want to ask is the following: what exactly does this new shiny service do that I cannot already do (or almost do) with my existing tools, and which will justify the overhead of investing in a new space or service?

For the moment, I am “not getting” either Pearltrees or SmallRivers, but as I said, I have just given them an initial “does it click?” look. I have my pearltree account (not much in it yet) in which I’ll try to place interesting posts about the conference when I have a moment. I also tried to create a “LeWeb’09” network with SmallRivers but think I messed up a little. If you go to my initial post on the LeWeb’09, you’ll see a little widget at the bottom which opens up a sidebar to which you can connect other posts about LeWeb’09. Give it a try and we’ll see if we can build something. (Basically: click on widget, click the connect button in the sidebar, copy the javascript code and paste it into your post.)

I’ve been thinking a lot about content curation during this conference — it’s a topic that the “real-time web” really brings to the forefront. Expect more posts on the topic.