ADVERTISEMENT



Google       

Home -> Law Blog Directory -> Legal Research Blogs -> LI Issues

OR PHONE (866) 635-1838 for Bankruptcy Help, (866) 635-6190 for Divorce,
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense

Find a Local Lawyer

Bankruptcy (866) 635-1838
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402

Bookmark

Legal Research

: LI Issues

Thnking about Twitter lists

ADVERTISEMENTS
If you're thinking about or are using Twitter lists, you might want to take a look at Chris Brogan's blog post "Twitter lists I'm not down"

In his post Chris' describes how yes Twitter lists are useful but when it comes to using them to list people there is a problem, as Chris explains "In talking with friends about it on Twitter, people immediately started DM-ing me, telling me that they felt left out or even LESS important because they weren?t on any lists. Lists are exclusionary by nature. They?re static. There?s a lot of reasons why they might not be all that pleasant for people"

I have to admit I'd never really thought about Twitter lists in this way. I can see now how they will be exclusionary. So what are other people doing, are you creating Twitter lists?

Full post as published by LI Issues on November 05, 2009 (boomark / email).

Bloggers, promote your law blog by nominating your blog for inclusion in USLaw.com's Law Blog Directory and RSS Reader. Benefits described.
Related Searches

























































































































US Law
#1 Online Legal Resource













Your Blog Subscriptions
Subscribe to blogs

10,000+ Law Job Listings
Lawyer . Police . Paralegal . Etc
Earn a law-related degree
Are you the author of this blog? Adding USLaw.com to your Blogroll increases relevance. You qualify to display a USLaw Network badge.
Suggest changes to this blog's description or nominate another for inclusion. Register for updates.


Practice Area
Zip Code:

Contact a Lawyer Now!






0.0126 secs (new cache)