base2048

Adding to that, cryptography is just mathematical obfuscation and often repeated here is that security through obscurity is not security at all. I will stick with my own principals of not fixating on a cipher. The only people that benefit are lazy spooks. Rather than what is accepted as the strongest ciphers I prefer ciphers not optimized by CPU's and GPU's. Spooks will have to cycle through every combination of protocol + cipher + mac + mode + passphrase + whatever other obfuscation I shim inside that tunnel. Keep 'em on their toes. Even better I will also cycle through these encoding methods [1] if I am in a good mood otherwise I will rot13 their ass and then force them to use a Drogan’s Decoder Wheel. [1] - https://github.com/qntm/base2048

I believe they are referring to using GPG to encrypt data before putting it into Slack, much like using the out of band OTR. In that case all the data shared between those using GPG or OTR would only be accessible to those with the right out of band keys. There are probably not a lot of people doing this, or not enough for governments to care. I do this in IRC using irssi-otr [1]. If that ever became illegal because encryption then groups of people could simply use scripts or addons to pipe through different types of encoding to make AI fuzzy searches harder. They can try to detect these chains of encoding but it will be CPU expensive to do every combination at scale given there are literally thousands of forms of encoding that could be chained in any order and number. Mon -> base64 -> base2048 [2] Tue -> base2048 -> base131072 [3] .

For fun there are other variants of base64 in a similar spirit [1][2] full unicode. [3] see other links in that repo... Not a stream cipher, just encoding but could be used in conjunction with a stream cipher to add compression. It could go turtles all the way down. [1] - https://github.com/qntm/base2048 [2] - https://github.com/qntm/base32768 [3] - https://github.com/qntm/base65536

Just putting this here for alternate baseX: https://github.com/qntm/base2048

Adding to this here [1] is a chart that shows how several encodings affect size ratios of utf-8, 16 and 32. Of course that gets into the discussions [2][3] of using utf in passwords and I have no idea how many password schemes support this beyond what I use. [1] - https://github.com/qntm/base2048 [2] - https://security.stackexchange.com/questions/85663/is-it-a-g... [3] - https://security.stackexchange.com/questions/4943/will-using...

I use https://github.com/qntm/base2048

They mention base64 encoding messages to evade filters. There were actually other base{n} methods [1] created specifically for Twitter to be more space optimized though not as readily available to operating systems. I guess this is less useful if they are really expanding the text limit to 4k soon but figured I would add it in the event they add a parser for base64. This assumes most people would be able to: npm install base2048 I think it might be interesting if Mastodon added a function to automatically detect and decode base2048 for browsers in javascript since JS is required to view a Mastodon site anyway. Bots would then have to adopt this logic, rendering most bots useless until they adapt and evolve. But I am not a developer and maybe this is just not possible. [1] - https://github.com/qntm/base2048

See also https://github.com/qntm/base2048. "Base2048 is a binary encoding optimised for transmitting data through Twitter."

I know of one case of Twitter doing client side validation [1]. Maybe there are more? 1 - https://github.com/qntm/base2048#note

I think the last line is a replay, encoded in base2048: https://github.com/qntm/base2048 But when I tried your replay, it didn't work. Perhaps HN's text editor mangled something.

There's base2048 [0], which can cram 11 bits into each code point, or 110 bytes into 80 characters. [0] https://github.com/qntm/base2048

This is what you're looking for: https://github.com/qntm/base2048 It can store 385 bytes per tweet. This link includes a bit more technical explanation of how Twitter counts characters towards the limit. Apparently, using the entire range of unicode characters does not improve compression because of the double weighting of emojis and other characters as described in TFA. It links to a base131072 encoding which can only store 297 bytes per tweet.

There are several of these. base65536 is the one that seems to pop up the most often on HN, although base2048 is more useful for Twitter. On the GitHub page the dev helpfully links to the various implementations: https://github.com/qntm/base2048