We found a problem in Little Pork Chop, proving that even the simplest software snack can have bugs. This one is not so easy to address, so I decided to document it so people know how to work around it.
The problem occurs when you include a partial URL in your stream, something like buff.ly/1tHnJWW. When we shoot that up to Twitter as part of a storm, it recognizes it as a URL, replaces it with a t.co URL and then if we're right at the margin of 140 chars calls it an error because the tweet is longer than 140. Why? Because there's no http:// on the original URL so that didn't figure into our count of characters. Once it replaced it, the new URL has the http:// in front, and that appears to be what forces it over the limit.
I have to write code that recognizes that as a URL and figures in the number of extra characters, and not send so many to Twitter, but until that's in the product, you should always include the http:// at the beginning of URLs and everything should be okay.
Thanks to William Mougayar for very patiently working this out with me. And stay tuned for the fix.