Otherwise, your plugin is perfect!

Therefore, these are my top requests:

A. Ignore direct tweets (tweets beginning with ‘@’)

B. Shorten post title via index of last space before character limit

C. Link URLs in posts. Currently, my shortened URLs are not linking within the body of the post

I am not a fan of post each blog post to Twitter function. People should write their own tweets to Twitter with better content than “I just posted the post ‘Post title.’” Not that you should remove it.

I recommend that “best practices” should be commented on as a “very-informed” user of Twitter Tools, not as an author.

Thanks for the awesome plugin. It gets plenty of use from me!

I have to agree with a previous comment, that control over @ replies would be very nice.

Not only do I publish my tweets to my wp blog, but I then crosspost all of my blog entries to my livejournal. So as you can imagine, most people probably don’t care about my one-sided conversations that they see.

Thanks again!

First off, I have to echo all the others and say THANKS!

As for whether or not you should editorialize *within* the plugin, I think that it’s something best left for blogs and blog comments. If you felt strongly about it, you could always link back to a post on your blog with the necessary “Twittiquette”

Since everyone else has taken an opportunity to mention a new feature or two I’d just like to second a couple that were mentioned previously:
1. Ability to turn off broadcasting on a post-by-post (edit-by-edit) basis. I recently re-categorized a bunch of posts and didn’t realize I was spamming my twitter peeps.

2. Ability to edit the broadcast message.

All in all you’ve done fabulous work, not only with TT but many of your other plugins as well. Keep up the great work and thanks again on behalf of the WP community.

it would be fantastic if updates could be displayed anywhere on a page and were not confined to a widget in the sidebar. any plans along these lines?

greg

Generally speaking, I love TT. There are a few quirks that mildly irritate me, and it would be nice if they could be fixed or turned into optional features.

0) I really would like to have incoming tweet be automatically categorized (I have a category “tweets” that I manually move them into every few days). Auto-tagging of the tweet summary would be nice, too. Basically, if any existing tags are found in the message, add them to the new message. I wouldn’t want it to create new tags out of the blue (that could introduce typos or other problems), but an option to have TT scan the imported tweets for existing keywords and tag the message with any that were found, would be a very helpful feature and save me a lot of time.

1) As mentioned above, URLs or anything really long in the sidebars messes up the theme pretty badly. It would be nice if URLs could be truncated, ideally at a user-configurable length (in case somebody wants long URLs, and somebody else is really short on space).

2) I recategorized all of the messages in my blog, and I did not discover that TT was sending a notification for each and every message that was edited. To quote a friend, I created a “Twitter-splosion”. On the plus side, I did pick up some traffic and comments on some of my oldest posts. The problem is that I did not expect TT to send an announcement when I edited an old post–only on new ones when they are first “published”. If that could be a configurable option, that would be GREAT! Perhaps on a post-by-post basis, too. A checkbox that says, “Announce update on Twitter” that sends out a notice that says the already published message was updated (not in those words, but that’s the idea).

3) I don’t think that you need to enforce any policies within the plugin. PERHAPS you could implement a flood-control feature that would help people like me who accidentally generate a whole slew of updates within a certain period of time. It should be configurable, though. A high traffic blog with multiple authors would have very different flood thresholds compared to my fairly low traffic site.

4) I like the idea that someone posted about having the cut-off time being local time. I notice that in FeedBurner, all of my Twitter updates come through 2-days behind the actual posting. I guess that FB picks cuts off at midnight, then TT posts some of the daily tweets, and then the latests tweets don’t get picked up by FB until another day later. It’s not a big deal, but it’s probably a bit confusing if anyone actually reads them.

5) One twist on the “daily vs. weekly” debate you might consider… I think it would be nice to have a collection of weekly archived tweets, but have it updated daily. In other words, lets say Monday is the start of the new week. So on Monday a new post is created. When Tuesday’s tweets are ready to be posted, the Monday post is updated and the modified date is updated (but on the original posting date so that RSS readers wouldn’t get confused). This process repeats so that all 7 days are collected together in a single post (reducing clutter in the blog), but still keeping things current. It’s probably overkill, and I don’t know how many people would use it. Personally, daily updates are probably the way I will go even with a weekly update option. It helps my blog avoid those stretches of emptiness.

Thanks again for this great tool–probably the best out of the ones I have tried so far.

I recently began posting the tweets digest to my blog (would love to be able to control how often that posts – every two days, once per week – ! and whether to include @replies), and also the reverse. I asked my readers and followers to tell me what they thought. and have heard nothing yet. We’ll see.

Sometimes though, I do use it to tweet directly from within my blog.

I actually think that sending a notification of a blog post to Twitter is extremely useful. As for guidelines, I’m not sure that is really necessary, people who use Twitter will ultimately try and create a network and learn what the people they follow, and are followed by, accept. I think as a general guideline saying you shouldn’t use it to simply spam folks with your blog posts may seem innocuous enough, but what if a network of people are using Twitter as a one-stop shopping for all of their particular communities updates.

As is often the case, there is seldom any one right way to use these tools, and if you didn’t include this feature in your plugin, it goes without saying that someone else would. Only thing is, I’m not so sure they will be quite the developer that you have proven to be

As for guidelines, well I guess that would be up to you, but why should you be strapped with that onus? Let other people figure the tool out from playing around in it, if people don’t like they way they use Twitter, they will probably no have much of a network, and will figure it out from there.

Thanks for the plugin,
Jim

I use three column WP themes, and on some of them the Twitter URLs flow outside of the sidebars. The only theme that effectively solves this issue is K2. Is it possible for you to shorten the URLs with ellipses? For example; http://www.twitter…, it would be most helpful.

Thanks again.

Reading through the list of comments here, I echo the sentiment about a seperate css file for customizing the appearance, the repost on Twitter update, and I am glad someone else here mentioned about posting to our blogs weekly, like I originally emailed. This is the feature I want the most.

I see the focus more on the community features of Twitter, and incorporating those into the plugin. I personally don’t have anyone following me, so that is not all that important to me as of now. But would be to most people.

Perhaps a way to customise a new post announcement from the editor too.

Overall, a great tool. Thank you.

Like the other comments, I am using it for the digest function only. I’ve had to do the loop category filter for my digests myself within the old fluid theme I’m limping on until WP2.5. It’s not really the job of the plug-in to hide posts form the main index loop but I wanted to mention I do not push digests to my main index.

The only thing I would add to your footnote is an option to specify a custom CSS for the entry when the archive digest is posted. It would be nice to have a namespace for how I wish to create or display those entries specifically. Ideally, this could be an item or word one could enter into a text field that someone could go back and support within their style.css for their theme.