News for hackers. Stuff that matters.
Re:Twitter Sort by TrainedMonkey on Tuesday January 13, 2015 @08:17PM (#8883689)
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 which will complicate handling logic as you need to account for being forever alone without anyone to sort your numbers.

In short, I would advise against deploying this on production until technology is more mature.

Re:Twitter Sort by Mahn on Tuesday January 13, 2015 @08:30PM (#8883726)
Regarding maximum input size, I'm sure it can be forked to implement a tweet-sharding approach.
Re:Twitter Sort by wging on Wednesday January 14, 2015 @06:54AM (#8885666)
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.
Re:Twitter Sort by emmanueloga_ on Wednesday January 14, 2015 @10:33PM (#8890754)
For sorting big lists of numbers mergesort could be used, only resorting to twittersort when the list of numbers is small enough [1]. In fact, that's the way mergesort is generally implemented (except the "cutoff" algorithm is usually insertionsort, not tweetsort :p).

1: http://en.wikipedia.org/wiki/Merge_sort#Optimizing_merge_sor...

Re:Twitter Sort by jayp on Tuesday January 13, 2015 @08:45PM (#8883784)
Sharding via a Tweet Storm(TM).
Re:Twitter Sort by guelo on Wednesday January 14, 2015 @03:24AM (#8884970)
In the sorting world it's called a bucket, not a shard.
Re:Twitter Sort by afandian on Wednesday January 14, 2015 @04:54AM (#8885285)
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?

Re:Twitter Sort by lloeki on Wednesday January 14, 2015 @11:50AM (#8887380)
OCR? dump the raw sequence as bytes and encode it into a valid PNG.
Re:Twitter Sort by afandian on Wednesday January 14, 2015 @12:44PM (#8887767)
The trouble is that some mobile ISPs compress images (as I found to my surprise). I know it should be sacrosanct, but you can't rely on the same bytes coming out the other end. I think OCR would be more robust.

Otherwise you're potentially ruling out mobile users.

Re:Twitter Sort by anon4 on Wednesday January 14, 2015 @08:51AM (#8886177)
Put your numbers in a pastebin, then post a link to the pastebin. Then, when you get the sorted numbers, post the sorted sequence in the original pastebin, thus creating a cloud-backed repository of sorted variants of number sequences. After that, you can check if your sequence is already on pastebin before asking twitter!
Re:Twitter Sort by ant6n on Tuesday January 13, 2015 @11:01PM (#8884210)
Maybe each comparison could be done via a tweet request.
Re:Twitter Sort by danvayn on Tuesday January 13, 2015 @08:23PM (#8883703)
Thank you, TrainedMonkey.