I use TwitterTools. I also use the Category Excluder to remove the daily twitter posts from my home page RSS feed and archives. However, now all my Tweets are searchable from my blog!

I’ve also added to the side bar an RSS of search.twitter.com of all @stuarthenshall comments on twitter. They may not be in context of a post; they are part of my online public conversational life.

There are some other changes I am writing up in a new blog post.

When I first started using Twitter Tools, I really wasn’t participating in the community of Twitter (that took awhile for me to grasp), and I liked having some coherent, reasonably interesting content automatically appearing on my blog even if I didn’t have time to do a proper blog post. (Because some days that just can’t be done.)

But since I started using, with some frequency, the “@” function to participate in conversations on Twitter, I wince in horror at what gets posted to my blog, which isn’t going to make a lick of sense to anyone who isn’t already participating in Twitter. (In which case, they’d probably prefer to follow those lines of conversation through the Twitter interface!)

I would really, really LOVE having that as a feature. (Alas, messing around with your code in order to try to customize it would be WAY over my head.) Just an option where you could check off, “exclude @ replies.” I think that would be genius.

Thanks for your great work!

If I want my tweets to act like salt and pepper on my blog — where I can sprinkle them wherever — I think a separate table makes the most sense.

OTOH (and I really want this) if I’d rather use WP more as a Tumblelog — i.e. posts with no titles — I’d love to use Twitter as an input method that’s equal to a native posting UI… using Twitter you get the benefit of using Jabber, SMS and the web UI, let alone the API. And, as a separate modification of a WP install, I could run it independent from my main blog, giving me the freedom to experiment while still having my regular blog that might show off a tweet here and there but wouldn’t use that content as the *primary* content.

That’s where I’m at anyway.

However, if the data was added to a completely separate table, then it would be “easier” to play with on the side, without fear of tainting the WP tables. Additionally, by adding the data to a separate table, displaying the tweets is slightly more difficult for people that do not know much about SQL.

If I were to choose between the two, I would go for the latter. This way, the tweets could go in to a table that could be used to consolidate other similar data, which might be used to construct a more robust Lifestream-like page.

Just my $0.02.

By giving each tweet it’s own post (in WP), you’d have more control how it is displayed/represented.
As long as the tweets are categorised/tagged properly, they can be filtered out accordingly.

If there’s the ability to post within the WP Admin page and store in a local table as well as Twitter’s server via an API to take advantage of the social aspects of Twitter then I’m all for it.

I’ve seen another plugin called fquick which I was thinking of trying as well.

It’d be great to have the option of either generating individual posts, or a day’s archive…

That might be too many steps though. But the idea of having my tweets in a table I can do whatever I like with is compelling.