Twitter is highly ephemeral and I don't think it's a good idea to split support out into a series of venues. I see this same thing in other software groups with IRC instead of Twitter and I think it's *much* better to use something like Google groups for discussion or a permanent page on a jQuery (or your own) site for anything which is boiled down to an answer. Every time I see "that was answered on IRC" or "come ask us on IRC" I cringe because I know that valuable information was just "lost" to the community (searching irc logs for 100 different channels to find an answer is unreasonable) while it was disseminated to a single user or a clique.
Any time something like this comes up don't consider how you're helping an individual but how your work could be leveraged to help everyone involved for the foreseeable future and with the least amount of repetition. To me Twitter is right out for this. (By the way, love your plugins and really appreciate how much support you give on them; very impressive). -Ashley On Sep 13, 11:53 am, Mike Alsup <mal...@gmail.com> wrote: > Over the past few months I've been fielding an increasing number of > support requests via Twitter (for Cycle, BlockUI, and Form plugins). > In some ways it's a nice way to respond to simple questions but > obviously it's not well-suited for more in-depth questions and > responses. I generally direct people to this Google Group for > anything non-trivial but I'm wondering what others think about > leveraging Twitter for simple Q&A. Thoughts? > > Mike > > http://twitter.com/malsup
