256 byte packet and a 192 bit authentication hash, why use fast flux dns to run C&C on your botnet when you can just make them twitter followers.<p>EDIT: And in case that isn't clear. Imagine you have a botnet, and all of the individual members create a twitter account. All of the twitter botnet accounts follow the 'master'. Who can tweet a command (and corresponding authentication key) to the botnet to say "follow chuck and do up to n things for him, here is his public key". Now Chuck suddenly has all these followers and when the time is right he tweets out his command, "ddos my greatest enemy" and adds his 'proof'. Off they go and blast his enemy. If he was only allotted one command then they all un-follow him.<p>Basically its social media for botnets.
Yeah but what you <i>really</i> want is base-emoji. <a href="https://github.com/pfrazee/base-emoji" rel="nofollow">https://github.com/pfrazee/base-emoji</a>
See also:<p><a href="https://blogs.oracle.com/ksplice/the-1st-international-longest-tweet-contest" rel="nofollow">https://blogs.oracle.com/ksplice/the-1st-international-longe...</a><p>Twitter characters can actually store up to nearly 31 bits each, if you’re using the JSON API. (Or at least, this was true in 2010. I don’t know whether this is still true.)<p><a href="http://blog.kevinalbs.com/base122" rel="nofollow">http://blog.kevinalbs.com/base122</a><p><a href="https://news.ycombinator.com/item?id=13049329" rel="nofollow">https://news.ycombinator.com/item?id=13049329</a><p>Base-122 encoding is 87.5% efficient in UTF-8, better than anything listed in the base65536 repository’s comparison table.
I'm the one who made the C / UNIX Shell implementation - it was a fun and quick thing to make.<p><a href="https://github.com/girst/base65536" rel="nofollow">https://github.com/girst/base65536</a><p>I'd appreciate some feedback.
I don't seem to get the efficiency table (or how efficiency is defined here?). Since Base65536 encodes 16 bits, why can't it encode UTF-16 with 100% efficiency? It says the efficiency is 64% instead.<p>I'm sure it's true, just curious why.
I hate this game.<p>Manage to make 1 point at 𤄻𣺻𣼋耈𣺻興𣼫兊𠨋𢪄𡚻𡢁𢙌𢚻𠛀𣪻栌𤄋𤯄𤆻𤆠𠞠𤪇𤆻𠙀𤅴𤆧𣪤𡚻𥪹炌𤆀㶸聙𡊰𠨌𡪻𤇅𤆀薠嫊䂔𔔌𥩋㲼耈𠊁繈倘𤨸𣾔㼬𤚱𢩋𣿋𡉌膹敃ꎹ𡩋肐𠝒𠚬醸聛㰩<p><a href="https://qntm.org/files/hatetris/hatetris.html" rel="nofollow">https://qntm.org/files/hatetris/hatetris.html</a>
So, anyone got any good HATETRIS replays? I'll edit my post if I find myself getting a good one.
<a href="https://qntm.org/files/hatetris/hatetris.html" rel="nofollow">https://qntm.org/files/hatetris/hatetris.html</a><p>Edit: If you didn't look at the repo, this encoding was made to post HATERIS replays on Twitter.<p>Edit: Only 3 points so far 𤆂𤆻𡚻𤆥㲺着遈𥮸㼉𤄛皲𤆻孈𤇆𡊾缎𓍌𤂻职𢪻郇膻𤅋𠅌傺𢊰䡪𤇄𤪤𡪻ꋇ𥆸𤶹膺𢡋聜𠆬𤪄膹𠬋㿄𠘬臀㾤冹𣾻𡈰𠭀䂹𤄔㼌𤚐𤢰𢢻𤇀𤞁䂺㬅𢉋𤮹㼆𣛄𡫀𤚒㡋𤢀ᖠ
If you really want to put binary data on Twitter, why not encode it in an image? You could probably get several tens of kilobytes of binary data reliably encoded in a JPEG of the maximum size Twitter allows.
Neat. I see a lot of mention of Twitter but the first thing I thought of was packet compression. A ~50 byte packet shaves off around 20 bytes with this. Those are good savings although I haven't looked into the encoder / decoder enough to know if it's worth the tradeoff of having to translate every packet on both ends. I can also see UDP datagrams being a pain in the ass to work with when you're throwing around streams of Unicode characters.<p>Overall though, I like it and look forward to Base131072 being possible!
Last year, I did a similar project: <a href="https://github.com/gvx/base116676" rel="nofollow">https://github.com/gvx/base116676</a><p>It had a feature where it automatically would try a couple of compression algorithms on the text to be able to cram even more into a single tweet.<p>I don't think it has a practical use, but it was fun to make.
What surprises me is that this encoding was developed to allow people to share replays of an illegal, and very pathological, Tetris variant. Hackers gonna hack.