I think that I had encountered a similar situation a while ago when we were first getting setup with our twitter apps. I'm not sure if this is the same problem but when we were sending tweets/DM's it would look like it came from our app and not our client which is what I think you have described. The problem for us was we needed to have the client authorize our app to send tweets/dm's on their behalf and then store that ouath data in our database to use when sending tweets/dm's out. here is a link to a post I made and the answer helped me so maybe it might be of some help to you.
http://forums.twitterizer.net/viewtopic.php?f=9&t=62 On Fri, Oct 8, 2010 at 11:28 AM, pulse00 <r.gruend...@gmail.com> wrote: > Hi all, > > we'v recently implemented some of the twitter api on our site, > including creation of automatic tweets for certain events of our > users. > > There's a strange behavior however, when publishing a status update to > the following url: > > http://api.twitter.com/version/statuses/update.format > > We would like to mention the official twitteraccount of our site in > the user's tweets, using "@someAccount". However, when we do so, the > tweet is being created by the account of the connected application, > and not by the user we're posting as. > > Is this behavior intended? > > > thanks! > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk