Twitter Sort

Post by lloeki » Wed, Jan 14, 2015, 4:50 PM UTC

afandian wrote: post #42

TrainedMonkey wrote: post #2

While potentially more efficient than bogosort for larger input size, this sorting algorithm has a serious limitation. I am of course talking about being limited to 140 characters per tweet. This seriously restricts maximum input size you can sort, which in turn severely cuts down on potential applications of this technology. Moreover, without deployed SAAS (sorting as a service) bot, algorithm is not deterministic w…

Where's your imagination? Three immediate solutions: 1 - gzip content to store in a tweet. You could squeeze more out. 2 - store the content in an image and standardize on an OCR library 3 - use twitlonger.com for larger messages EDIT: Anyway I thought app.net was meant to solve all this?

Post by afandian » Wed, Jan 14, 2015, 5:44 PM UTC

lloeki wrote: post #51

afandian wrote: post #42

Earlier quoted context omitted.

Where's your imagination? Three immediate solutions: 1 - gzip content to store in a tweet. You could squeeze more out. 2 - store the content in an image and standardize on an OCR library 3 - use twitlonger.com for larger messages EDIT: Anyway I thought app.net was meant to solve all this?

OCR? dump the raw sequence as bytes and encode it into a valid PNG.

Post by emmanueloga_ » Thu, Jan 15, 2015, 3:33 AM UTC

wging wrote: post #44

Mahn wrote: post #4

Earlier quoted context omitted.

Regarding maximum input size, I'm sure it can be forked to implement a tweet-sharding approach.

Merging of tweet shards is also possible via the same mechanism. Just tweeterate through the retrieved shards and merge them one by one. To merge two lists, compare elements pairwise. To compare elements pairwise, construct a two element list and sort this list via the short-form tweetsort api.