My previous post just made me realize a fundamental flaw in automatic
crossposting (ie., what i write on my blog gets tweeted on Twitter
which in turn is echoed on Facebook). A tweet/status update of
"Comment ground" makes Absolutely No Sense At All when seen in that
context. It might have been another cute wordplay when it was a blog
post header but when migrated, all alone, to another platform -- it
just looks stupid.

So what to do? Give all my postings tweet-friendly titles or continue
confusing people with lyrical/musical/cultural references and not get
a discussion? A human-centered approach -- taking YOU into account,
before me -- would probably be the right one, but what will i be
losing in the process?

I have a system in place where my tweets are echoed as Facebook wall
posts. What is a bit surprising to me is that i get a fair amount of
comments to Facebook on these used-to-be-tweets, a lot more than i get
responses as tweets.

While an analysis of the reasons is way beyond the scope of article,
two things emerge. The phenomenon itself, and the redundance of data.
I think it's great that my words of wyrd echo out to where me mates
are, but the fact that the possibly ensuing discussion forks into two
unconnected branches sucks. In fact, there is even little evidence
that an update on Facebook originates from somewhere else. You may be
reading this very posting through Twitter or Facebook but it
originates from Posterous.

What i'm missing is the facility to recombine the responses into one
comment stream. I don't really care where this happens, as long as
there only is one stream.

Tear down the garden walls. Interoperability is playing nice.