3 ms·
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 s
by afandian 12y ago
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?
- lloeki 12y agoOCR? dump the raw sequence as bytes and encode it into a valid PNG.
- afandian 12y agoThe 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.