I've added a domain exception to the twitter rule, I could not see anything else being blocked that shouldn't be

Thanks!
If you have some suggestion I'd like to hear them

It is difficult for me to make suggestions because I lack the experience of creating/maintaining a filter list but in order to reduce the amount of "false positives" how about only blocking third-party requests? For example:
- example.com loads social network-related resources from Facebook/Twitter/etc. --> Antisocial blocks third-party requests which prevents tracking and wasting bandwidth. That's what it's already doing right now with great success!

- example.com loads social network-related resources from from its own (sub-)domain --> Antisocial should do nothing. Currently, Antisocial removes these resources too.
IMHO Antisocial is a bit too aggressive. It should focus more on the tracking/bandwidth aspect of filtering content. I "think" this would make it easier for you to maintain it in the long run (less false positives and thus less whitelisting).
To that end I have made the list fairly general, unfortunately the amount of sites which seem to use a similar naming convention for "legit" content is higher than I originally anticipated.
That's the whole point of my "complaint". I can report to you pretty much every day about websites with missing pictures, sometimes even leading to broken page layout. If Antisocial would be a bit less "trigger-happy", it could almost maintain itself!
