Rebooting The Blogosphere (Part 2: Interaction) [en]

Start with part 1!

Yesterday I started writing “a blog post” to capture my coalescing thoughts about the open web and how to remove friction from blogging. Not all of it: some friction is good. But enough that people like me don’t get so easily drawn away from their blogs by “The Socials”.

So far, in Rebooting The Blogosphere (Part 1: Activities) I have distinguished four types of “activities” we carry out in online social spaces:

  • reading
  • commenting/reacting
  • writing
  • sharing.

Today, I’ll focus less on the actions an individual carries out, and more on the interaction between individuals. The wonderful thing about blogs is that they lowered the barrier to personal expression online, which in turn makes dialogue possible. But dialogue can take many forms.

Some thoughts on Dave’s “new model for blog discourse

Before I go any further, I would like to address a few points Dave brings up in his podcast from yesterday, because I actually started yesterday’s post with the intention of responding to it (amongst other things), but he put it up while I was already writing.

I love what Dave describes doing in the very early days, if I understood it right: write something, send it by e-mail to handful of people, and have a first round of discussion with that smallish group before publishing, and including value-adding responses to the publication. All this, scripted so that it was as frictionless as possible for him. This reminds me of Bruno Giussani‘s “Promote Comments Plugin” idea. It also fits with the idea I insisted upon yesterday that there is an added value to making the discussion about something available in the same place as that thing.

It is also reminding me of one aspect that I hadn’t thought about covering in this post-become-series: managing who the audience is. I firmly believe that allowing conversations to take place in closed or semi-public spaces is vital (cf. context collapse) – proof the number of people who take part in closed groups on Facebook or who share updates to “friends only“. I might have to make this a fourth part…

Dave describes a future tool in which comments (responses) get posted to the commenter’s blog and sent privately to the author of the original blog post, who can then decide whether to make it visible or not. For me, the second part of this process is already widely implemented in blogging tools, and has been for over a decade: its upfront comment moderation. Some people activate it, some don’t. On this blog, for example, if you’re a first-time commenter, your comment is not published. It is sent to me and I decide whether it’s worth publishing or not.

The first part is more interesting. It addresses the “ownership” issue of the comment, as tools like coComment or Disqus have tried to by providing a place all a person’s comments are collected. But it goes one step further and says: that place is the commenter’s blog. This is great and has been long needed. It would be interesting examine why previous attempts to do this across platforms have not stuck.

And this leads us to the topic of today: show my comments on my blog, but in what way? My comments are not the same kind of content as my posts. I don’t want my posts to be mixed up with my comments, everything on the same level. I’ll explain why.

Finally, Dave identifies some of the challenges with blog comments that I covered in yesterday’s post, but I’m not sure the current situation is as “broken” as he thinks. All that is missing, really, is a way to collect-own-display the comments I make all over the place in a space that is mine. Moderate comments upfront, or not? Or even, not have comments? That’s already possible, and up to the blogger. And yes, moderating comments or limiting who can comment directly cuts down tremendously on the spam and other bad behaviour issue.

Comments are about interaction – so are links between blogs. And as I mentioned yesterday, one thing the socials are really great at is interaction. You can spend your whole day on there (don’t I know it) interacting.

A way to look at interactions

I’m going to start by sticking with 1-1 interactions, to make it simpler, but I think this can be applied to interactions with more actors.

I think we all agree that exchanging letters with somebody (which I’m old enough to have done in my youth) is very different from talking on an instant messaging system. The key dimension that varies here is how (a)synchronous the interaction is. This drives a lot of the features we have in our social tools, and what makes them different from one another – just like in martial arts, the distance between the practitioners constrains the kind of techniques, and therefor the kind of fighting (interaction) that can take place.

I’d like to summarise it this way:

The length of contributions in an interaction is inversely proportional to how synchronous, or how conversational it is. And vice-versa.

Let’s unpack this a bit.

When Twitter showed up with its 140-character limit (which didn’t come out of nowhere, it was SMS-based), and constrained how much we could write in one go, it quickly became a place where we were “talking” more than “writing”, as we had been doing on our blogs. It was not quite as immediate as instant messaging, but somewhere in between. Like text messages.

In the early days of Facebook, if my memory serves me right, there was a distinction between sending a message to somebody (sorry, I can’t remember the terminology that was used, I’m not even 100% sure I’m remembering right) as some kind of internal mail, and chatting (or maybe they transformed the former into the latter and it changed the way we used it). In Discourse, you have both: you can send a message to somebody, or chat. Like you can e-mail somebody, or instant message them.

And I suspect I am not the only person to feel some degree of annoyance when I receive an “instant message” that should have been “an e-mail”, because it requires me to sit down, absorb a “speech”, and then figure out how on earth I’m going to respond to all that was said in one go, particularly now the person who sent it is not online anymore, because I had to wait until I had enough time to properly read it, digest it, and figure out my response.

Instant messaging works when it’s used for short things that you can take in at a glance (or barely more) and answer without having to think too much. It is conversation, with an asynchronous twist. When both parties are connected and interacting (synchronous), it is very close to in-person (or “on the phone”) synchronous conversation, but with this “optional asynchronicity”, as there is a blind spot regarding the context of the other party, and how it impacts their availability to read or respond right now, or even, to keep the conversation going. (If you’re on the phone with them or in the same room: they are available.)

When in “conversation mode”, contributions can become a bit longer, but not too long: if you throw a 3-page essay at somebody in an instant message or chat conversation, chances are you’ll lose them. Just like in-person conversation: if you monologue for 10 minutes at the person you’re talking with, you don’t have a conversation anymore. And actually, this pretty much never happens: there are non-verbal cues that the person opposite you is going to give that will either interrupt your monologue, or reveal that it is in fact a dialogue, when taking into account non-verbal contributions of the listener. But when you’re typing in an instant-messaging box, there is none of that.

Back to blogs. A blog post does not have the same conversational qualities as a response to a tweet. Blogs live in a more asynchronous interaction space than the socials or chatting. Comments are generally more conversational than blog posts. But probably less than updates on the socials.

“Allowed length” of contribution plays a role in shaping the kind of interaction, as well as design. If you’re typing in a tiny box, you’re less likely to write an e-mail or a blog post. If you’re typing in a box that uses up the whole screen, you’re less likely to write only one sentence.

Why did so much conversation move from blogs and chats to socials? I think that it is because they are in some sweet space on the (a)synchronicity continuum. They allow belated responses, but also real-time interaction. Notifications are key here, as is the fact that writing/responding are pretty much the same thing (same on Twitter or Bluesky or Mastodon, not-quite-same on Facebook, but close enough) and in the same space as reading/listening. It’s super easy to jump in and out of conversation. Frictionless.

So, it’s not just about reducing friction around reading blogs, writing blog posts, and commenting on them: it’s also about how we integrate the blogosphere and the socialsphere. One cannot and should not replace the other. There will always be people who like writing stuff. And others who are just happy to interact or react. And it doesn’t make sense to corral them into separate spaces.

Does anybody remember Backtype? I didn’t. Well, I do now after reading my blog post. The idea was to find a way to bring “back to the blog post” conversation about it that was happening on the socials (gosh, I really hope it’s not too annoying for you all that I’ve started saying “the socials”, it’s just really practical; my apologies if it grates on you). What about Diigo comments?

There is a common theme here: somebody writes a blog post. There is discussion about it or prompted by it – in the comments, on other blogs, on Bluesky, Facebook, Twitter and Mastodon, even Threads. How do we give easy access to these fragmented conversations (I think conversation fragmentation is now something that we have accepted as inevitable and normal) to those who are reading the post? And how do we do that in a way that a) leaves some control in the blogger’s hands over what to show and not to show (less spam) and b) allow people participating in the conversation to keep ownership of their content, in the sense that even if it can be made invisible in a given context (e.g. on the blog post), it cannot be outright removed by a third party, and remains “on the record” of the person who wrote it?

Who owns the conversation?

There is a lot of talk about retaining rights or ownership to one’s content. But who owns a conversation? Or beyond that, a community? The whole is more than the sum of the parts. When people come together to create something together (including relationships), who owns that? I mentioned previously that when facebook allows you to “download your content”, that doesn’t seem to include comments (wait, I have a doubt now – I think the export used to, but not anymore, correct me if I’m wrong, as I can’t go and check easily). Or comments by others made on your posts. In any case, say you can download your comments: a lot of them are contributions to conversations, and make little or no sense without their context – the publication the conversation took place about, other people’s comments.

I think there needs to be some kind of “collective ownership” understanding, which is more nuanced than “I wrote it, I have power of life or death over it”. When does something you offer up to the collective cease to be completely yours? In my opinion, it remains yours in the sense that it cannot be taken away from you against your will. Corollary: if contributions to a conversation or a community also “belong” to the conversation or community, then it should not be possible to take it away from them unilaterally. This is something that needs to be thought out further: does it mean that I should not be allowed to remove my blog from the web?

What is clear at this point: we need to think beyond “atomic” contributions and also think about how our tools manage the collective creations that are conversations and communities.

So, let’s sum up today: interaction is not a monolith. Online conversations occur at varying speeds and are made up of contributions of varying nature. Reclaiming and rebooting the blogosphere and the open web needs to take that into account and embrace it, and figure out how to bring it together in an open way, with frameworks, standards, protocols or the like, not yet another “One Platform to Replace Them All”.

That will be tomorrow, in part 3.

Thanks for reading, and don’t hesitate to react: on the socials, here in the comments, or on your blog!

5 Lessons in Promoting Events Using Social Media (Back to Basics) [en]

[fr] Leçons apprises lors de la promotion de Going Solo:

  • communiquer directement avec les gens (messagerie instantanée, conversation offline, téléphone) est le mode de communication le plus efficace
  • ne pas négliger l'e-mail, les dossiers de presse, le matériel imprimable: tout le monde ne lira pas le blog ou Twiter
  • rien ne devient automatiquement "viral" parce que c'est sur internet: aider les gens à vous aider à passer l'info, par exemple avec un e-mail "forwardable"
  • aller où sont les gens, les retrouver dans leur communauté (Facebook, MySpace, Rezonance, LinkedIn... partout)
  • ça prend du temps... beaucoup de temps

J'ai été surprise à quel point tout ceci a été difficile pour moi, alors qu'une partie de mon métier consiste à expliquer aux gens comment utiliser les nouveaux médias pour communiquer plus efficacement. Une leçon d'humilité, et aussi un retour à certaines choses basiques mais qui fonctionnent, comme l'e-mail ou le chat. En récompense, par contre, un événement qui a été un succès incontesté, et tout cela sans le soutien des médias traditionnels (pour cause de communiqué de presse un poil tardif) -- mis à part nouvo, qui a répercuté l'annonce, mais qui trouvait que c'était cher!

One of the big lessons I learnt while organising Going Solo is that promoting and communicating about an event through social media requires a huge amount of time and energy. In this post, I’d like to share a few of the very practical things I (re-)discovered.

Even though part of what I do for a living is explain social media and its uses in marketing to my clients, I found it quite a challenge when I actually had to jump in and do it. (Yes, I’m aware this may sound pretty lame. By concentrating on the big picture and the inspiring success stories, one tends to forget some very basic things. Sending managers back to the floor every now and then is a good thing.)

The main lesson I learnt is the following:

  • 1. The absolute best channel to promote anything is one-on-one personal conversation with somebody you already have some sort of relationship with.

Any other solution is a shortcut. And all shortcuts have prices.

This means I ended up spending a lot of time:

  • talking to people on IM, IRC, and offline at conferences
  • sending out personal messages on LinkedIn and Facebook.

Anytime you do something to spare you this time (like sending out a collective e-mail, writing a blog post, or even tweeting — situations where you’re not adressing one specific individual directly) you dilute what you’re communicating. You open the door to:

  • imperfect understanding of what you’re trying to say
  • people not feeling like it’s really addressed to them (lack of interest, or lack of awareness that their actions are important to you)
  • people simply not seeing it.

I have many examples of this. I created a page with material people could use to promote Going Solo, in particular, blog sidebar badges. But not many people put them up spontanously, even amongst my friends. But when I started pinging people on IM and asking them if they would please put up a badge to support my event, they did it. They just hadn’t got around to doing it, hadn’t realised that them doing it was important for me, or it had simply slipped their mind. It’s perfectly understandable: it’s “my” event, not theirs.

Another example is when I started sending out my “forwardable e-mails” (lesson #3 is about them), most people stopped at “well, I’m not a freelancer” or “I can’t come”. It took some explaining to make sure they understood that the main reason I was sending them the e-mail was that they might know somebody who would like to come to the event, or who could blog about it, or help with promoting it. If I spared myself the personal conversation and just sent the e-mail, people were much less likely to really understand what I expected from them, even through it was spelled out in the e-mail itself.

And that was a big secondary lesson I learnt while preparing Going Solo: it’s not because people don’t get back to you, or don’t act, that they aren’t interested or don’t want to. The burden is on you to make it as easy as possible for them to help you.

Let’s continue on to the next lessons.

  • 2. Blogs and Twitter are essential, but don’t neglect less sexy forms of communication: newsletter, press release, printable material.

The first thing I did for Going Solo was to create a blog and a Twitter account. Getting a blog and Twitter account off the ground isn’t easy, and it took quite a lot of one-on-one communication (see lesson #1) (and blogging here on CTTS) to get enough people to link to them so that they started taking off.

But the lesson here is that not everybody is on Twitter, and not everbody reads blogs. We highly-connected types tend to forget that. It didn’t take me that long to get the feeling that I had “exhausted” my immediate, social-media-enabled network — meaning that all the people who knew me directly had heard what I was talking about, linked to stuff if they were going to, or registered for the event if they were interested.

So, here are some less “social media cutting-edge” forms of communication I used, most of them very late in the process (earlier next time):

Some comments.

Our press release came out so late that we got no coverage at all from traditional media, bar one exception, which focused on how expensive the event was. This means Going Solo Lausanne is a great case study of successful event promotion entirely through social media.

When I created the newsletter, I spent a lot of time following lesson #1 and inviting people personally to sign up, through IM most of the time. I sent out invitations through the Google Groups interface, of course (to the extent that I got flagged as a potential spammer). But I also went through the process of inviting people directly through IM.

A word of warning about newsletters: don’t add people to your newsletter unless you’ve checked beforehand that they were OK with it, or if you have a very good reason to do so (they are the speakers/attendees for your event) — but even then, it can be risky. I was recently added to a bunch of mailing-lists without having asked for it, rather than invited, and I find it really annoying. It’s way more impolite to unsubscribe from a newsletter than refuse an invitation to subscribe, so adding people can put them in an embarrassing situation (be impolite vs. be annoyed at getting newsletters one doesn’t want).

  • 3. Don’t expect “viral” or “organic” spreading of your promotion to happen, but prepare the field so it can: the forwardable e-mail.

There is so much talk about the fact that social media allows things to spread all by themselves (and indeed, there is an important potential for that, and when it happens, it’s very powerful) — that we tend to expect it to happen and be disappointed when it doesn’t. And let’s face it, it’s not something that we can control (sorry for stating the obvious again, I’m doing that a lot in this post) and it takes quite a bit of skill to create the right conditions so that it may happen.

So, now that we’ve set our expectations, what can be done to help things spread? I mentioned having exhausted my immediate network higher up, so I needed to come up with a solution which would help me reach beyond it. How could I get my friends to mention Going Solo to their friends?

Of course, our use of social media in general allows that. Blogs, Facebook Groups and Events, sidebar badges… all this is material which can spread. But again — what about the people who aren’t bathing in social media from morning to evening?

Back to basics: e-mail. E-mail, be it under the shape of a newsletter, a discussion list, or simple personal messages, has a huge advantage over other forms of online communication: you’re sure people know how to use it. It’s the basic, level 0 tool that anybody online has and understands.

So, I started sending out e-mail. A little bit of push is good, right? I composed a rather neutral e-mail explaining what Going Solo was about, who it was for, giving links to more information, and a call to action or two. I then sent this impersonal text to various people I knew, with a personal introduction asking them to see if they knew anybody who could be interested in information about this event, and inviting them to forward the message to these people. Nothing extraordinary in that, right?

I of course applied lesson #1 (you’re starting to know that one, right?) and tried as much as possible to check on IM, beforehand, if it was OK for me to send the “forwardable e-mail” to each person. So, basically, no mass-mailing, but an e-mail written in such a way that it was “forwardable” in a “here’s what my friend Steph is doing, could interest you” way, which I passed along as a follow-up to a direct chat with each person.

In a more “social media” spirit, of course, make sure that any videos you put online can easily be shared and linked to, etc. etc — but that will be pretty natural for anybody who’s familiar with blogging and “being online”.

  • 4. Go where people are. Be everywhere.

Unless your event is already very well known, you need to go to people, and not just wait for them to come to you. If you’ve set up a blog, Twitter account, newsletter, then you have a place where people can come to you. But that’s not enough. You need to go where people are:

  • Facebook
  • Upcoming
  • LinkedIn
  • Xing
  • MySpace
  • Pownce
  • Seesmic
  • Existing communities big and small… (blogs, forums, chatrooms)

Again, this is a very basic principle. But it’s not because it’s basic that it’s invalidated by the magic world of social media. Where you can create an event, create an event (Upcoming, Facebook, Pownce, Rezonance — a local networking thingy); where you can create a group, create a group — I waited a lot before creating a Facebook group for Going Solo, because I had a fan page for it already, but as you can see the group worked much better.

  • 5. It’s a full-time job.

Honestly, I didn’t think I’d spend weeks doing nothing else but send e-mails, update Facebook pages, blog, send e-mails, talk to people, IM, tweet, e-mail again… to promote Going Solo. It’s a huge amount of work. It’s so much work that one could imagine having somebody full time just to do it. So when you’re (mainly) a one-person shop, it’s important to plan that a significant amount of your time might be spent on promotion. It’s easy to underestimate that (I did, and in a major way).

Working this way doesn’t scale. At some point, one-on-one communication takes up too much time and energy to compensate for the benefits it brings over more impersonal forms of communication. But that only happens once your event is popular enough. Before you’ve held your first event (which was the situation I was in with Going Solo Lausanne), you don’t have a community of advocates for your work, you don’t have fans (you might have personal fans, but not fans of your event) or passionate attendees ;-), you don’t have other people doing your work for you.

At the beginning, every person who hears about your event is the result of sweat and hard work. Hopefully, at some point it’ll take off and you’ll start seeing more and more people blogging about the event you’re organising — but even then, it might take a while before you can just sit back and watch things happen. But in case this moment comes earlier than planned, you’re all set: you have a blog, a Twitter account, a Facebook group and a newsletter. Until then, though, you’re going to be stuck on IM and sending out e-mails.

A few last words

I hope that by sharing these lessons with you, I’ll have contributed to making things a little easier for somebody else in the same situation I was. You’ll have understood that I haven’t tried to be exhaustive about how to use social media for promotion — indeed, I’ve skipped most of the “advanced” stuff that is more often spoken about.

But I think it’s easy to get so taken up with the “latest and greatest” tools out there that we forget some of the basic stuff. I, for one, was guilty of that initially.

Also, one thing I haven’t spoken about is how to talk to people. Of course, some of what you’re doing is going to be impersonal. Own up to it, if you’re mass e-mailing. Don’t pretend to be personal when you aren’t — it’s hypocritical, doesn’t come across well, and can be smelled a mile away.

I haven’t quite finished reconciling my practical experience with how I believe things “should” work. I’ve learnt a lot, but I certainly haven’t figured everything out yet. I would have wanted to do a lot more, but time simply wasn’t available, so I tried to prioritize. I made choices, and some of them were maybe mistakes. But overall, I’m happy with how things went and what I learnt.

If you have had similar experiences, I’d be really happy to hear from you. Likewise, if you disagree with some of the things I’ve written, or think I’m wrong on certain counts, do use the comments. I’m open to debate, even though I’m a bit hard-headed ;-).