•  

  • Me_normal

     

  • Alex_sm2_normal

     

  • Alex_sm2_normal

     

  • Me_normal

     

  • Me_normal

     

  • Alex_sm2_normal

     

  • Me_normal

     

  • Alex_sm2_normal

     

  • Me_normal

     

  • Alex_sm2_normal

     

  • Me_normal

     

  • Alex_sm2_normal

     

  • Alex_sm2_normal
  • I was just reminded of something important by Scott (@unmarketing), and learned something in the process:

    There is a real conflict in the Twitter design/API regarding @replies vs. RTs (which are themselves a “crowd-sourced” , emergent add-on, which wouldn’t have even been necessary if Twitter had been a better job with “Favorites”).

    Since Twitter will by default hide @replies from users UNLESS they follow both parties in the exchange (kind of a bug in my view as a default, and I highly recommend setting it to “All @ replies”), my experimental RT format of “@username RT: ..” doesn’t work as intended.

    So it’s a forced choice between Retweet spread & threading/context information remaining intact. Some may argue that the latter doesn’t matter that much since Twitter moves so fast, but I would hold that in quite a few cases, having the threading/temporal context persist is very insightful/valuable.

    Twitter is both synchronous (chat/IM-like) AND asynchronous (more like email, blogging), wherein lies a lot of its power and appeal. Too bad this is making us choose right now.

     

    Advertisements