I’ve been interested in different forms of communication for some time.  It’s part of what makes social networking so interesting to me.  I’ve been reading about others’ experiences too.  Of course there’s Tantek’s CommunicationProtocols page, which inspired my own Communication Protocols section on my main page (and, probably, @seanbonner’s PreferedMeansOfContact).  Trevor Creech recently challenged me on my Twitter usage, calling it “Twitterfail” (in reference to efail).  I would like to discuss some of they ways I’ve started thinking about communication.

First, a tip from my own main page: If you find a solution, from me or elsewhere, blog it. Someone else may benefit.  I have come to think of my Twitter and Ma.gnolia accounts as blogs (especially since they began to manifest their updates in the actionstream on my main page).  If I find an interesting tidbit, or have a potentially interesting thought, I tweet it.  This lead, one day, to >20 tweets in 24 hours, the condition which Trevor complained about.  In response, I have tried to consider first if something is really useful at all before I tweet (I don’t want to be the cause of a signal/noise problem) – but I have also started including better context in my tweets.  Interesting links go to Ma.gnolia.

Searchability has become key for me. This is one of the reasons I love my IM setup – everything anyone says to me, whether I’m online or off, at my computer or not, is archived in Gmail for easy search.  My tweets and blog posts are also searchable – in fact, if you just say “singpolyma” or link to me in a blog post, there’s a huge chance that I’ll see it.

When it comes to factors like immediacy, lifespan,  audience, bandwidth, and sychronity they are all important, but are different for different messages.  If I’m setting up a meeting or working on a project, immediacy and bandwidth are hugely important (thus, face to face or IM are best).  If I’m discussing something of interest to me, asychronity, lifespan, and audience are the most important factors (thus, mailing lists, forums, Pibb, and IRC are best).  There is no “perfect” communication form – all have their place.

I have requested that people use post/page comments for debugging/feature requests on my projects.  This is because a comment is almost as good as blogging something (it can be used by others who may benefit) and is searchable.  It also reduces the chances that I get asked for the same thing a bunch of times – others can see what is being discussed (which, incidentally, in the same reason I love GetSatisfaction).  Pages + comments are almost as good as (in fact, in many cases, I feel are better than) a wiki.

Part of the big buzz surrounding Web 2.0 has been pull alerts as opposed to push alerts.

Push alerts / messages –  I send you a message.  This is how email and IM work.  I choose when, where, and how the message is sent and largely control how you receive it.  I send an email, you get it in your inbox.

Pull alerts / messages – I send a message which may (or may not) be intended for you primarily.  You decide when, where, how, and IF you receive it.  This most common form of this is RSS/ATOM feeds.  I publish to my blog / Twitter / whatever and you subscribe to me if you want to.  You can receive alerts via email, IM, Xanga, Facebook, Google Reader, BoxtheWeb, Sage, or a myriad of other options.

Some have said that push alerts are dying.

This makes some sense.  When I post on a forum, I don’t want to have their system email me every time there is a reply (email/push).  What I really want is to have easy access to a list of posts replying to mine to look over (RSS/pull).

However, this can go a bit too far.  Pull IM does exist to some extent, but it defeats the purpose.  I want you to see something NOW, it’s URGENT, INSTANT.  Pull does not fit this.

Push alert systems, however, just refuse to die!  Facebook/Myspace messages/wall posts.  Blog comments.  New friend-group messaging systems like Pownce.  Push is extremely popular.

The masses are rarely right, but perhaps we shouldn’t brush off push alerting altogether at this point.

This is a good quote, too long for an excerpt.

Slashdot – perky
Things I want on a phone:
1. Small
2. Lots of space for contacts
3. Synch with Outlook
4. Some flash memory with a USB socket, like a USB memory stick
5. Well designed UI
6. Good audio quality
7. Shold look recognisably like a phone
8. Predictive text

Things I don’t want on a phone:
1. Camera
2. Video camera
3. Games
4. Audio recorder
5. mini qwerty keyboard
6. flashlight
7. GPS
8. Compass
9. Microsoft Office
10. A meda player

Things that are acceptable as long as they don’t get in the way:
1. GPRS
2. Some kind of WAP/internet thing
3. Bluetooth
4. a Java runtime

Someone is thinking, who wants a camara in a phone anyway??? Some of this stuff is okay, but some of it is rediculous! I must admit I have used some of these features on my dad’s phone, but they didn’t work really well. What we really need is a PDA that works as a phone, not a phone that works as a PDA. Incidentally, why did he want it to sync with Outlook? Outlook is pretty much useless and is getting worse every release.

Tags: Technology