Entweet: Securing Twitter

For the curious and lazy: it works by rendering the signed message to an image and tweeting that [2].<p>Then it relies on the fixed grid [0] and font to do a &quot;poor man&#x27;s OCR&quot; [1] when decoding.<p>[0] <a href="http:&#x2F;&#x2F;git.io&#x2F;vIWll" rel="nofollow">http:&#x2F;&#x2F;git.io&#x2F;vIWll</a> [1] <a href="http:&#x2F;&#x2F;git.io&#x2F;vIWln" rel="nofollow">http:&#x2F;&#x2F;git.io&#x2F;vIWln</a> [2] <a href="https:&#x2F;&#x2F;twitter.com&#x2F;Lukasaoz&#x2F;status&#x2F;607632001210925056" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;Lukasaoz&#x2F;status&#x2F;607632001210925056</a>

Why not use the pixel values themselves to encode the data? Each pixel&#x27;s RGB can encode three characters (one for each byte value). The resulting image would be much smaller.<p>(Not sure how twitter might alter the image though, which would corrupt the data).

Not knowing much about the encryption used, would it end up using extra characters over a normal tweet?

Hah! Twitter for Enterprise, Bizniz, and Secrets!<p>Revolt and rejoice!<p>But... if this relies on fixed-ish protocol (fixed grid &amp; font), can&#x27;t The Man Upstairs censor it just as easily?

Twitter wanted to do end-to-end encrypted DMs once, until it gave up on the project with no explanation:<p><a href="http:&#x2F;&#x2F;www.theverge.com&#x2F;2014&#x2F;3&#x2F;19&#x2F;5523656&#x2F;twitter-gives-up-on-encrypting-direct-messages-at-least-for-now" rel="nofollow">http:&#x2F;&#x2F;www.theverge.com&#x2F;2014&#x2F;3&#x2F;19&#x2F;5523656&#x2F;twitter-gives-up-o...</a>

Could someone explain like I&#x27;m 5 how this works?<p>Is it just standard public&#x2F;private key?

LOL at &quot;GPG is famously easy to use&quot;

_inconvenient_ cannot be stressed enough

It seems that companion browser extensions should be first on the TODO list.