Loading Profile...
Shrunk tweet translation via api
I've implemented tweet shrinking in Twitulater but since I can't read the shrunk garble very easily and can thus fairly assume that there are others out there who cannot I doubt many people will be using the feature.
But if there was a simple way to automatically detect what tweets were shrunk, then send them to the API and get a translation back, so the whole shrinking would be transparent to the user that would be AWESOME.
Think about it, you send a shrunk tweet, and the other end sees it as normal language. Wouldn't that be great?
The heuristic to discover shrunk tweets is probably very simplistic, translation not so much, but whomever made the shrinking algorithm can easily make a deshrinker no?
But if there was a simple way to automatically detect what tweets were shrunk, then send them to the API and get a translation back, so the whole shrinking would be transparent to the user that would be AWESOME.
Think about it, you send a shrunk tweet, and the other end sees it as normal language. Wouldn't that be great?
The heuristic to discover shrunk tweets is probably very simplistic, translation not so much, but whomever made the shrinking algorithm can easily make a deshrinker no?
I’m idealising
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Ok, I think I see what you're saying. Using Twitulater, you would detect a shrunken tweet and then attempt to unshrink it using our service, thus bypassing the 140 car limit and showing a tweet that has been unshrunk to possibly more than 140 chars. I like the idea.
So to me, the main question becomes how to detect a shrunken tweet. I'm guessing you wouldn't want to make one API call for that and another to unshrink it. And I suppose you could send every tweet to this proposed unshrinker, but that's inefficient as well as irrseponsible. What are your thoughts on this?
I’m on the fence
-
Inappropriate?If I made an API call for detection then I might as well send everything to the deshrinker.
But perhaps the solution is that when the app starts I make an API call to fetch the translation dictionary you use, or some most-used list of words to look out for. If the tweet contains anything from there it needs unshrinking.
I think that would be quite an optimal solution. -
Inappropriate?ok, we're going to take some time to discuss this one. but i wouldn't hold up your release or for it or anything. maybe we can work out how this should work for your next release?
-
Inappropriate?Go at the pace you feel comfortable with. I have tons of other features that need implementing really.
After all, software is done when it's done, nobody should push it.
EMPLOYEE
