I might — ever since Twitter implemented universal shortening via their own t.co shortener, adding new shorteners has been a low priority. Also, obtaining an ow.ly API key isn’t automated, so I’m concerned about the method for getting users set up with the system.
Joe Dolson – any idea on the above? that would be really appreciated please 🙂
See this: http://www.joedolson.com/articles/2012/12/wp-to-twitter-the-next-step-forward/
My long-term plan is to remove URL shortening from WP to Twitter, for a wide variety of reasons. It would still be possible to use URL shortening with WP to Twitter, but it would no longer be built into the plug-in.
It could be a good idea to let users to add their own shortener, actually you need only a URL for the API method (that incorporate API keys) with a {url} parameter. Almost all shortener support the plain/text (return) format. A button TEST near the configuration could help people to configure the shortener.
es. https://my.shortener.api/shorten?url={url}&apikey=my_api_key
Also part of the long-term plan; but it’s going to take a while.
I’m adding a new shortener in the next release, but that’s mostly because the URL shortener people contributed the code themselves, which made it easy to add.
