Legal community abuzz about LexTweet
Many of you (we hope) are familiar with LexTweet, the website LexBlog launched on New Years Day. As Kevin explained last Friday, the goal of the site is to showcase members of the legal community who are using Twitter as well as what they are tweeting.
There has been a lot of feedback and a fair share of suggestions for how to improve LexTweet. It still has a few kinks that need to be worked out, and look for faq and disclaimers coming soon -- but the early response has been overwhelmingly positive.
- Ed Adams (@edadams), Editor and Publisher of the ABA Journal, tweeted that LexTweet is a 'Massive game-changer for social media adoption by lawyers.'
- Edmund Scanlan (@edscanlan), CEO of Total Attorneys, called LexTweet 'a great business vertical specific site built around Twitter.'
- Author and legal commentator, Walter Olson, (@walterolson) tweets, 'Now we have faces: outstanding resource for anyone interested in law/lawyers and Twitter.'
- Attorney Alexis Neely (@AlexisNeely) had a rave response of 'Dude, I LOVE LexTweet.com. You are so awesome. Lawyers on Twitter go to LexTweet.com and join now.'
- M. Stucky, an ungrad with an interest in law (@stupub13) said, 'I'm incredibly pleased with LexTweet. A great tool to find people to follow when you're new to Twitter. Thanks!'
Along with the positive there has been constructive criticism.
- Attorney Daniel Schwartz (@ctemplawyer) questioned, 'Is ranking people on lextweet by followers the best way? You wouldn't rank blogs by lexblog by hits, would you?'
- Bruce Carton (@brucecarton), Editor of 'Securities Docket' noted, 'The truth: LexTweet is a brilliant concept, visually beautiful. But without groups, not very useful to me because way too broad.'
Both good points, and under consideration by the LexBlog development team.
If you have feedback and suggestions on LexTweet, we want to hear from you. Tweet your suggestions while referencing the term lextweet (we monitor our name), reply or direct a tweet to Kevin O'Keefe (@kevinokeefe), or email Kevin.