I think the sanest compromise here is an opt-in alternative, either by providing direction to the RSS and/or Atom feeds your Twitter account generates for assorted views, or pointing LoudTwitter at a separate weblog (extant or new) and making a feed for those specific entries available.
The latter makes the most sense to me in the abstract (blog-topic feed will not update with every post, but rather supply the aggregate content as and when LoudTwitter disgorges the digest to it), but concerns me in the specific. You'd need appropriate robots.txt so that Google doesn't ding pagerank (assuming extant blog option) for duplicated content belonging to multiple Eric Burnses.
This isn't a you-crit; it's progressed to a technicial concern.
no subject
The latter makes the most sense to me in the abstract (blog-topic feed will not update with every post, but rather supply the aggregate content as and when LoudTwitter disgorges the digest to it), but concerns me in the specific. You'd need appropriate robots.txt so that Google doesn't ding pagerank (assuming extant blog option) for duplicated content belonging to multiple Eric Burnses.
This isn't a you-crit; it's progressed to a technicial concern.