Tag Archives: vocal

Social Networks and Microblogging

Microblogging (Laconica, Twitter, etc.) is still a hot topic. For instance, during the past few episodes of This Week in Tech, comments were made about the preponderance of Twitter as a discussion theme: microblogging is so prominent on that show that some people complain that there’s too much talk about Twitter. Given the centrality of Leo Laporte’s podcast in geek culture (among Anglos, at least), such comments are significant.

The context for the latest comments about TWiT coverage of Twitter had to do with Twitter’s financials: during this financial crisis, Twitter is given funding without even asking for it. While it may seem surprising at first, given the fact that Twitter hasn’t publicized a business plan and doesn’t appear to be profitable at this time, 

Along with social networking, microblogging is even discussed in mainstream media. For instance, Médialogues (a media critique on Swiss national radio) recently had a segment about both Facebook and Twitter. Just yesterday, Comedy Central’s The Daily Show with Jon Stewart made fun of compulsive twittering and mainstream media coverage of Twitter (original, Canadian access).

Clearly, microblogging is getting some mindshare.

What the future holds for microblogging is clearly uncertain. Anything can happen. My guess is that microblogging will remain important for a while (at least a few years) but that it will transform itself rather radically. Chances are that other platforms will have microblogging features (something Facebook can do with status updates and something Automattic has been trying to do with some WordPress themes). In these troubled times, Montreal startup Identi.ca received some funding to continue developing its open microblogging platform.  Jaiku, bought by Google last year, is going open source, which may be good news for microblogging in general. Twitter itself might maintain its “marketshare” or other players may take over. There’s already a large number of third-party tools and services making use of Twitter, from Mahalo Answers to Remember the Milk, Twistory to TweetDeck.

Together, these all point to the current importance of microblogging and the potential for further development in that sphere. None of this means that microblogging is “The Next Big Thing.” But it’s reasonable to expect that microblogging will continue to grow in use.

(Those who are trying to grok microblogging, Common Craft’s Twitter in Plain English video is among the best-known descriptions of Twitter and it seems like an efficient way to “get the idea.”)

One thing which is rarely mentioned about microblogging is the prominent social structure supporting it. Like “Social Networking Systems” (LinkedIn, Facebook, Ning, MySpace…), microblogging makes it possible for people to “connect” to one another (as contacts/acquaintances/friends). Like blogs, microblogging platforms make it possible to link to somebody else’s material and get notifications for some of these links (a bit like pings and trackbacks). Like blogrolls, microblogging systems allow for lists of “favourite authors.” Unlike Social Networking Systems but similar to blogrolls, microblogging allow for asymmetrical relations, unreciprocated links: if I like somebody’s microblogging updates, I can subscribe to those (by “following” that person) and publicly show my appreciation of that person’s work, regardless of whether or not this microblogger likes my own updates.

There’s something strangely powerful there because it taps the power of social networks while avoiding tricky issues of reciprocity, “confidentiality,” and “intimacy.”

From the end user’s perspective, microblogging contacts may be easier to establish than contacts through Facebook or Orkut. From a social science perspective, microblogging links seem to approximate some of the fluidity found in social networks, without adding much complexity in the description of the relationships. Subscribing to someone’s updates gives me the role of “follower” with regards to that person. Conversely, those I follow receive the role of “following” (“followee” would seem logical, given the common “-er”/”-ee” pattern). The following and follower roles are complementary but each is sufficient by itself as a useful social link.

Typically, a microblogging system like Twitter or Identi.ca qualifies two-way connections as “friendship” while one-way connections could be labelled as “fandom” (if Andrew follows Betty’s updates but Betty doesn’t follow Andrew’s, Andrew is perceived as one of Betty’s “fans”). Profiles on microblogging systems are relatively simple and public, allowing for low-involvement online “presence.” As long as updates are kept public, anybody can connect to anybody else without even needing an introduction. In fact, because microblogging systems send notifications to users when they get new followers (through email and/or SMS), subscribing to someone’s update is often akin to introducing yourself to that person. 

Reciprocating is the object of relatively intense social pressure. A microblogger whose follower:following ratio is far from 1:1 may be regarded as either a snob (follower:following much higher than 1:1) or as something of a microblogging failure (follower:following much lower than 1:1). As in any social context, perceived snobbery may be associated with sophistication but it also carries opprobrium. Perry Belcher  made a video about what he calls “Twitter Snobs” and some French bloggers have elaborated on that concept. (Some are now claiming their right to be Twitter Snobs.) Low follower:following ratios can result from breach of etiquette (for instance, ostentatious self-promotion carried beyond the accepted limit) or even non-human status (many microblogging accounts are associated to “bots” producing automated content).

The result of the pressure for reciprocation is that contacts are reciprocated regardless of personal relations.  Some users even set up ways to automatically follow everyone who follows them. Despite being tricky, these methods escape the personal connection issue. Contrary to Social Networking Systems (and despite the term “friend” used for reciprocated contacts), following someone on a microblogging service implies little in terms of friendship.

One reason I personally find this fascinating is that specifying personal connections has been an important part of the development of social networks online. For instance, long-defunct SixDegrees.com (one of the earliest Social Networking Systems to appear online) required of users that they specified the precise nature of their relationship to users with whom they were connected. Details escape me but I distinctly remember that acquaintances, colleagues, and friends were distinguished. If I remember correctly, only one such personal connection was allowed for any pair of users and this connection had to be confirmed before the two users were linked through the system. Facebook’s method to account for personal connections is somewhat more sophisticated despite the fact that all contacts are labelled as “friends” regardless of the nature of the connection. The uniform use of the term “friend” has been decried by many public commentators of Facebook (including in the United States where “friend” is often applied to any person with whom one is simply on friendly terms).

In this context, the flexibility with which microblogging contacts are made merits consideration: by allowing unidirectional contacts, microblogging platforms may have solved a tricky social network problem. And while the strength of the connection between two microbloggers is left unacknowledged, there are several methods to assess it (for instance through replies and republished updates).

Social contacts are the very basis of social media. In this case, microblogging represents a step towards both simplified and complexified social contacts.

Which leads me to the theme which prompted me to start this blogpost: event-based microblogging.

I posted the following blog entry (in French) about event-based microblogging, back in November.

Microblogue d’événement

I haven’t received any direct feedback on it and the topic seems to have little echoes in the social media sphere.

During the last PodMtl meeting on February 18, I tried to throw my event-based microblogging idea in the ring. This generated a rather lengthy between a friend and myself. (Because I don’t want to put words in this friend’s mouth, who happens to be relatively high-profile, I won’t mention this friend’s name.) This friend voiced several objections to my main idea and I got to think about this basic notion a bit further. At the risk of sounding exceedingly opinionated, I must say that my friend’s objections actually comforted me in the notion that my “event microblog” idea makes a lot of sense.

The basic idea is quite simple: microblogging instances tied to specific events. There are technical issues in terms of hosting and such but I’m mostly thinking about associating microblogs and events.

What I had in mind during the PodMtl discussion has to do with grouping features, which are often requested by Twitter users (including by Perry Belcher who called out Twitter Snobs). And while I do insist on events as a basis for those instances (like groups), some of the same logic applies to specific interests. However, given the time-sensitivity of microblogging, I still think that events are more significant in this context than interests, however defined.

In the PodMtl discussion, I frequently referred to BarCamp-like events (in part because my friend and interlocutor had participated in a number of such events). The same concept applies to any event, including one which is just unfolding (say, assassination of Guinea-Bissau’s president or bombings in Mumbai).

Microblogging users are expected to think about “hashtags,” those textual labels preceded with the ‘#’ symbol which are meant to categorize microblogging updates. But hashtags are problematic on several levels.

  • They require preliminary agreement among multiple microbloggers, a tricky proposition in any social media. “Let’s use #Bissau09. Everybody agrees with that?” It can get ugly and, even if it doesn’t, the process is awkward (especially for new users).
  • Even if agreement has been reached, there might be discrepancies in the way hashtags are typed. “Was it #TwestivalMtl or #TwestivalMontreal, I forgot.”
  • In terms of language economy, it’s unsurprising that the same hashtag would be used for different things. Is “#pcmtl” about Podcamp Montreal, about personal computers in Montreal, about PCM Transcoding Library…?
  • Hashtags are frequently misunderstood by many microbloggers. Just this week, a tweep of mine (a “peep” on Twitter) asked about them after having been on Twitter for months.
  • While there are multiple ways to track hashtags (including through SMS, in some regions), there is no way to further specify the tracked updates (for instance, by user).
  • The distinction between a hashtag and a keyword is too subtle to be really useful. Twitter Search, for instance, lumps the two together.
  • Hashtags take time to type. Even if microbloggers aren’t necessarily typing frantically, the time taken to type all those hashtags seems counterproductive and may even distract microbloggers.
  • Repetitively typing the same string is a very specific kind of task which seems to go against the microblogging ethos, if not the cognitive processes associated with microblogging.
  • The number of character in a hashtag decreases the amount of text in every update. When all you have is 140 characters at a time, the thirteen characters in “#TwestivalMtl” constitute almost 10% of your update.
  • If the same hashtag is used by a large number of people, the visual effect can be that this hashtag is actually dominating the microblogging stream. Since there currently isn’t a way to ignore updates containing a certain hashtag, this effect may even discourage people from using a microblogging service.

There are multiple solutions to these issues, of course. Some of them are surely discussed among developers of microblogging systems. And my notion of event-specific microblogs isn’t geared toward solving these issues. But I do think separate instances make more sense than hashtags, especially in terms of specific events.

My friend’s objections to my event microblogging idea had something to do with visibility. It seems that this friend wants all updates to be visible, regardless of the context. While I don’t disagree with this, I would claim that it would still be useful to “opt out” of certain discussions when people we follow are involved. If I know that Sean is participating in a PHP conference and that most of his updates will be about PHP for a period of time, I would enjoy the possibility to hide PHP-related updates for a specific period of time. The reason I talk about this specific case is simple: a friend of mine has manifested some frustration about the large number of updates made by participants in Podcamp Montreal (myself included). Partly in reaction to this, he stopped following me on Twitter and only resumed following me after Podcamp Montreal had ended. In this case, my friend could have hidden Podcamp Montreal updates and still have received other updates from the same microbloggers.

To a certain extent, event-specific instances are a bit similar to “rooms” in MMORPG and other forms of real-time many-to-many text-based communication such as the nostalgia-inducing Internet Relay Chat. Despite Dave Winer’s strong claim to the contrary (and attempt at defining microblogging away from IRC), a microblogging instance could, in fact, act as a de facto chatroom. When such a structure is needed. Taking advantage of the work done in microblogging over the past year (which seems to have advanced more rapidly than work on chatrooms has, during the past fifteen years). Instead of setting up an IRC channel, a Web-based chatroom, or even a session on MSN Messenger, users could use their microblogging platform of choice and either decide to follow all updates related to a given event or simply not “opt-out” of following those updates (depending on their preferences). Updates related to multiple events are visible simultaneously (which isn’t really the case with IRC or chatrooms) and there could be ways to make event-specific updates more prominent. In fact, there would be easy ways to keep real-time statistics of those updates and get a bird’s eye view of those conversations.

And there’s a point about event-specific microblogging which is likely to both displease “alpha geeks” and convince corporate users: updates about some events could be “protected” in the sense that they would not appear in the public stream in realtime. The simplest case for this could be a company-wide meeting during which backchannel is allowed and even expected “within the walls” of the event. The “nothing should leave this room” attitude seems contradictory to social media in general, but many cases can be made for “confidential microblogging.” Microblogged conversations can easily be archived and these archives could be made public at a later date. Event-specific microblogging allows for some control of the “permeability” of the boundaries surrounding the event. “But why would people use microblogging instead of simply talking to another?,” you ask. Several quick answers: participants aren’t in the same room, vocal communication is mostly single-channel, large groups of people are unlikely to communicate efficiently through oral means only, several things are more efficiently done through writing, written updates are easier to track and archive…

There are many other things I’d like to say about event-based microblogging but this post is already long. There’s one thing I want to explain, which connects back to the social network dimension of microblogging.

Events can be simplistically conceived as social contexts which bring people together. (Yes, duh!) Participants in a given event constitute a “community of experience” regardless of the personal connections between them. They may be strangers, ennemies, relatives, acquaintances, friends, etc. But they all share something. “Participation,” in this case, can be relatively passive and the difference between key participants (say, volunteers and lecturers in a conference) and attendees is relatively moot, at a certain level of analysis. The key, here, is the set of connections between people at the event.

These connections are a very powerful component of social networks. We typically meet people through “events,” albeit informal ones. Some events are explicitly meant to connect people who have something in common. In some circles, “networking” refers to something like this. The temporal dimension of social connections is an important one. By analogy to philosophy of language, the “first meeting” (and the set of “first impressions”) constitute the “baptism” of the personal (or social) connection. In social media especially, the nature of social connections tends to be monovalent enough that this “baptism event” gains special significance.

The online construction of social networks relies on a finite number of dimensions, including personal characteristics described in a profile, indirect connections (FOAF), shared interests, textual content, geographical location, and participation in certain activities. Depending on a variety of personal factors, people may be quite inclusive or rather exclusive, based on those dimensions. “I follow back everyone who lives in Austin” or “Only people I have met in person can belong to my inner circle.” The sophistication with which online personal connections are negotiated, along such dimensions, is a thing of beauty. In view of this sophistication, tools used in social media seem relatively crude and underdeveloped.

Going back to the (un)conference concept, the usefulness of having access to a list of all participants in a given event seems quite obvious. In an open event like BarCamp, it could greatly facilitate the event’s logistics. In a closed event with paid access, it could be linked to registration (despite geek resistance, closed events serve a purpose; one could even imagine events where attendance is free but the microblogging backchannel incurs a cost). In some events, everybody would be visible to everybody else. In others, there could be a sort of ACL for diverse types of participants. In some cases, people could be allowed to “lurk” without being seen while in others radically transparency could be enforced. For public events with all participants visible, lists of participants could be archived and used for several purposes (such as assessing which sessions in a conference are more popular or “tracking” event regulars).

One reason I keep thinking about event-specific microblogging is that I occasionally use microblogging like others use business cards. In a geek crowd, I may ask for someone’s Twitter username in order to establish a connection with that person. Typically, I will start following that person on Twitter and find opportunities to communicate with that person later on. Given the possibility for one-way relationships, it establishes a social connection without requiring personal involvement. In fact, that person may easily ignore me without the danger of a face threat.

If there were event-specific instances from microblogging platforms, we could manage connections and profiles in a more sophisticated way. For instance, someone could use a barebones profile for contacts made during an impersonal event and a full-fledged profile for contacts made during a more “intimate” event. After noticing a friend using an event-specific business card with an event-specific email address, I got to think that this event microblogging idea might serve as a way to fill a social need.


More than most of my other blogposts, I expect comments on this one. Objections are obviously welcomed, especially if they’re made thoughtfully (like my PodMtl friend made them). Suggestions would be especially useful. Or even questions about diverse points that I haven’t addressed (several of which I can already think about).



What do you think of this idea of event-based microblogging? Would you use a microblogging instance linked to an event, say at an unconference? Can you think of fun features an event-based microblogging instance could have? If you think about similar ideas you’ve seen proposed online, care to share some links?


Thanks in advance!

iRiver H120 (Digital Audio Jukebox)

Recently purchased a brand new iRiver H120 with remote control on eBay from OutletMP3. Paid 132.50$ plus 18$ shipping. Also purchased a 3-year warranty through SquareTrade for 16$.
Item arrived as described, with both the European power adapter (in the original box) and a North American power adapter (in the shipping box). The remote control is included in the package but is outside of the original box. OutletMP3 sells those iRiver H120 devices with or without remote control (usually at about the same price).
Yes. “Would do business with OutletMP3 again.” (As it turns out, they sell iriver products quite frequently on eBay and they have an eBay store with “Buy It Now” iRiver H120 devices without remote for 150$ each.)
The best things about this device are its recording features. Those iRiver H1x0 models can record uncompressed sound in WAV format at 16bit with a sampling rate of 48 kHz (so-called “DAT quality”), 44.1 kHz (so-called “CD-quality”), or lower (“FM-quality,” “voice quality”). It also records directly to MP3 files (with the official firmware) in a variety of encoding settings (up to 320 kbps). It has an internal microphone for voice dictation as well as an input for external microphone, analog line in, or optical in.
The box includes a surprisingly decent lavaliere-style monophonic microphone. Not an excellent microphone in any way but clearly better than one might expect (though Laith Ulaby had told me that this microphone was decent).

In terms of operation, the unit has some strengths. The overall interface is much less convenient than that of the iPod, say, but the battery lasts longer than most iPods (for playback). The iRiver H120’s remote has a small LCD screen which shows enough information for most needs making it possible for me to keep the H120 in my pant pocket and operate the device with the remote. While, among portable players, only the iPod has native support for AAC and lossless formats, iRiver players support Ogg Vorbis and WMA. Haven’t done anything in Ogg format yet but it might be an interesting option (though it does make files less compatible with other players).

Apart from navigation and interface, the main differences with my previous iPod 2G have to do with iTunes integration. The iPod‘s synchronization with iTunes made it rather convenient to create and update playlists or to transfer podcasts. iRiver’s models may not be used in the same fashion. However, the iRiver H120 can in fact be used with iTunes through a plugin meant for Archos players. However, this plugin seems to have some problems with a few files (probably because of invalid characters like ‘/’ and ‘:’ in filenames), generates non-working playlists on Mac OS X, and puts all filed in an “Artist/Album” hierarchy which makes iRiver navigation more complicated.

What surprised me somewhat was that the H120, a USB 2.0 device, works perfectly well with my old iBook (Dual USB) which only has USB 1.1 ports. No need for special drivers and the device then works pretty much like a (20GB) USB drive. Since the iRiver H120 works as a USB drive, it’s easy to transfer files to and from the device (contrary to the iPod which makes somewhat more difficult). All audio files can be put at the root level on the iRiver and audio recordings made on the iRiver are in the “RECORD” folder at the root level of the drive. While the iBook’s USB 1.1 ports are much slower than USB 2.0 ones, they do the job well enough for my needs. (Will be going back to my entry-level emachines H3070 in a few days.) A 400 MB file recorded on the iRiver (about 40 minutes of 16 bit stereo sound at 44.1 kHz) transferred to the iBook through USB 1.1 in less than ten minutes. Slow, but bearable. My old iPod used a Firewire 400 (aka IEEE 1394 or i.Link) connection which is about the same speed as USB 2.0 in most conditions. My entry-level emachines desktop has both USB 2.0 and Firewire 400 ports (thanks to an inexpensive Firewire card).

Was thinking about putting Rockbox on the H120 but SquareTrade tells me that it may void their warranty, which would be an inconvenient. The Rockbox has some neat features and seems safe enough to use on “production machines,” but its features aren’t that compelling for me at this point.
The H120 has a radio (FM) tuner, which could be useful to some people but isn’t really a compelling feature for me. Haven’t listen to much radio in the past several years. Podcasts are soooo much better!

Speaking of podcasts… One of my reasons for purchasing this machine (instead of a more recent iPod) was the ease of recording. This is clearly not a professional recording device but the sound quality seems quite decent for my needs at this point. Should be using it to record lectures and distribute them as podcasts or “lecturecasts” (yeah, ugly name, sorry!). In my mind, educational podcasting can supplement lectures quite nicely. Have been to a few workshops and presentations on technology use in teaching and most people seem to agree that technology is no replacement for good pedagogy but that good pedagogy can be supplemented and complemented (if not complimented!) by interesting tools. Had been thinking about a recording iPod to integrate podcasts with course material. It would have been quite useful, especially in connection with iLife and iWork. But an iPod 5G (with video) is already much more expensive than my iRiver H120 and the add-ons to enable 44.1 kHz / 16 bit recording on the iPod are only now getting to market at a price almost half that of my brand new iRiver H120. Plus, though the iPod is well-integrated with iTunes on Windows, iLife and iWork applications are only available on Mac OS X 10.4 and, thus, will not run on the entry-level emachines H3070 which will become my primary machine again in a few days.
In other words, my ideal podcasting/lecturecasting solution is out of my reach at this point. And contrary to tenure-track faculty, lecturers and adjunct faculty get no technology budget for their own use.
Ah, well…

Still, my iRiver H120 will work fine as a recorder. Already did a few essays with voice and environmental sounds. The lavaliere microphone was quite convenient to record myself while taking a walk which sounds like an unusual activity but was in fact quite relaxing and rather pleasant. In terms of environmental sounds, the same microphone picked up a number of bird songs (as well as fan noises).
Among the things that distinguish the H120 from a professional recorder is the lack of a proper calibration mechanism. It’s not possible to adjust the recording levels of the two channels independently and it’s even not possible to adjust volume during recording. (There’s a guide offering some guidance on how to work within those constraints.) Quite unsurprisingly (for what is mostly an MP3 player) but also making the device less of a professional device, its jacks are 3.5 mm “stereo mini-plugs” (instead of, say, XLR jacks). For that matter, the iRiver H120 compares favourably to several comparably-priced MiniDisc recorders, even Hi-MD models. Did field research with a used ATRAC 4.0 MiniDisc recorder. That setup worked somewhat adequately but this iRiver H120 is much of an improvement for me.

Got a few pet peeves about the iRiver H120. For instance, it has no actual clock so recorded files do not carry a timestamp. A minor quibble, of course, but it would have been useful. The overall navigation is as awkward as that of my first MP3 device, the RioVolt (which also used iRiver firmware). One navigational issue is that navigating up and down in the folder hierarchy is done through the stop and play buttons instead of, say, using one of the three jog switches on the remote. Some functions only work when the device is stopped while others work while it’s playing. Switching from hard-disk playing to recording or to FM is a bit awkward and cumbersome. The unit takes a while to turn on and doesn’t really have a convenient sleep mode. While it is possible to resume playing on a track that has been stopped, this feature seems not to work every time. Fast forwarding rate (“scan speed”) is set in a menu instead of being dynamic as on the iPod. The device doesn’t support ratings or, really, descriptions (although Rockbox might be able to support those).

Also got a few well-appreciated features, apart from those stated above. The EQ and SRS presets are appropriate and relatively easy to use. Contrary to the iPod 2G it is possible to play files at a higher rate (increasing the “playback speed”) making it possible to listen to voice at a higher speech rate (and higher frequency). It’s also possible to delete files directly from the device.

At any rate, that’s already a long entry and experience with my H120 will probably push me to write more about the device.

Feel free to comment or send questions through email.