« Project Planner / Scheduler Za-Koenji Public Theatre by Toyo ItoStorytellingAdd comments »

The most annoying habit of Twitter users is the strategy of sending a DM aka direct message as a greeting to anyone who follows their tweets. Why would, what appears to be a smart method of introducing yourself to a new connection, a DM end up being detrimental to your ability to connect? The answer is automated response tools. 5 Reasons Not to Use Auto Direct Messaging Perception: you are immediately perceived as not caring enough to personalize your message to your new connection be

Twitter Strategies for Entrepreneurs: How Not to Use Direct Messages


Related with "Twitter Strategies for Entrepreneurs: How Not to Use Direct Messages"

Twitter Strategies for Realtors: Top 10 People to Follow

Courtesy TwitDir.com Twitter..com is rapidly changing the way companies and entrepreneurs showcase their businesses . With the right plan and purpose, anyone can broadcast news, generate leads, announce events, communicate internally, or become a go-to source of information for their audience. One[...]


Twitter Strategies: Hybrid ReTweets aka ReTweetCombos

Twitter Strategies: Hybrid ReTweets aka ReTweetCombos[...]


Twitter Signal to Noise Ratio Strategies: Many Fail Whale Efforts

Companies showing up on twitter to take advantage of the massive growth potential are often showing up without a strategy. In a vast majority of these cases, terrible mistakes are being made that weaken and even tarnish their brand.  The biggest problem, stemming from this lack of strategy, is[...]


101 new messages in 94 topics - abridged

101 new messages in 94 topics - abridged Posted on Sun, 03 Aug 2008 02:00:03 -0500 in Resume system architect and california Months* Rate : $50/HR System Architect The system architect is the technical auditor, leader, - Fri 1 Aug 2008 09:47 2 messages , 1 author[...]


Scaling Twitter: Making Twitter 10000 Percent Faster

Update 4: Improving Running Components at Twitter by Evan Weaver. Tells how Twitter changed their infrastructure to go from handling 3 requests to 139 requests a second. They moved to a messaging model, asynchronous process, 3 levels of cache, and moved their middleware to a mixture C and Scala/JVM.[...]