Limitations of TweetShrink API
We wanted to use TweetShrink in our iPhone app but ran into problems with very limited usability of the TweetShrink API. We cannot set target number of characters that we want returned - TweetShrink will shrink the whole message instead only shrinking until target character number is met. Also, if a character number cannot be met because text cannot be shrunk to it, it's good to have a flag that provides an error code. Also, it'd be very good customization feature of the API if the query could include level of shrinkage algorythm (from very conservative and least shrinking to wild and goofy and most shrinking).
Finally, and that's more of a feature request than simple API addition, allow the API query to tell TweetShrink what to do with text if maximum number of characters cannot be met - either to return it's best shot, or use a third-party or first-party feature similar to Twerbose and TweetLonger and ShortText to save text and return a link at the end of the query result that leads to the original, long text via web page.
Finally, and that's more of a feature request than simple API addition, allow the API query to tell TweetShrink what to do with text if maximum number of characters cannot be met - either to return it's best shot, or use a third-party or first-party feature similar to Twerbose and TweetLonger and ShortText to save text and return a link at the end of the query result that leads to the original, long text via web page.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?hi there, sorry i meant to respond to this earlier.
you give us too much credit, man. the tweetshrink "algorithm" is really just a simple word replacement program. we don't have different "levels" or anything like that. we programmed the whole thing in a day because we wanted something like it on Tweetdeck. since then a bunch of people have integrated it as is into their application. at this point, i think we've gone about as far as we're going to go with the service.
as it turns out Twitterific made their own shrinking algorithm instead of using ours. if you decide togo that route we strongly support you. also 140it.com is working on an API and they also sound kinda like what you want.
i hope that helps you, man.
The company and 1 other person say
this solves the problem
-
Inappropriate?Hi Ajit,
Sorry if my post sounded too demanding to your service, I fully understand your current commitment to the project and the "keep it simple" mentality to it. We have contacted several similar services and discovered one that fits our needs. Thanks a lot for the kind response.
I’m confident
Loading Profile...



EMPLOYEE