Earlier quoted context omitted.
Twitter’s limit used to be 140 characters. Then it became 280. By simple arithmetic progression the next limit will be…
Knowing Musk he'd totally be down for changing it to 420.
Base 2048
21–30 of 42 posts
Re: Base 2048
#22That’s 2,598 tweets to transmit a single megabyte. So, if I wanted to tweet the movie Spaceballs, encoded at 4K UHD (20MB/s), I estimate that I will need to make 20,945,455 tweets. Twitter limits the posts made by nobodys (like me) to 2,400 tweets per day… so, it is going to take me just under 24 years to complete my task. I’d better get started.
You can fit much more in a single tweet! You can do that with base64 + gzip + (and that’s the important one) _wrapping the content in a url_. Here’s pong (3.5kb) stored in a single tweet: https://twitter.com/rafalpast/status/1316836397903474688?s=2... Source: I was bored, curious if I could turn twitter into a CDN
Re: Base 2048
#23Earlier quoted context omitted.
You can fit much more in a single tweet! You can do that with base64 + gzip + (and that’s the important one) _wrapping the content in a url_. Here’s pong (3.5kb) stored in a single tweet: https://twitter.com/rafalpast/status/1316836397903474688?s=2... Source: I was bored, curious if I could turn twitter into a CDN
You can fit much more into a tweet if you consider image data, too.
Inside the range of characters support by twitter, your data is "guaranteed" to not change
Re: Base 2048
#24Earlier quoted context omitted.
You can fit much more in a single tweet! You can do that with base64 + gzip + (and that’s the important one) _wrapping the content in a url_. Here’s pong (3.5kb) stored in a single tweet: https://twitter.com/rafalpast/status/1316836397903474688?s=2... Source: I was bored, curious if I could turn twitter into a CDN
If/when we get an edit button, I feel like twitter could be a CDN and a CMS. Could make a "severless" blog that is just hijacking Twitter's server. Comments and media hosting built in!
Re: Base 2048
#25https://github.com/ctsrc/Base256
> Encode and decode data in base 256
> […]
> You might expect data encoded in base 256 to be more space efficient than data encoded in base 16, but with this particular set of symbols, that is not the case! Likewise, you have to type more, not less, than you would if you use my base 256 instead of base 16. So why?
> The purpose […] is to make manual input of binary data onto a computer less error-prone compared to typing in the base 16 or base 64 encoding of said data. Whereas manually typing out base 64 is painful, and base 16 makes it easy to lose track of where you are while typing, [this program] attempts to remedy both of these problems by using 256 different words from the EFF autocomplete-friendly wordlist.
Disclaimer: I am not using this base 256 program myself, even though I authored it. It just serves as a fun little experiment.
Re: Base 2048
#26Earlier quoted context omitted.
If/when we get an edit button, I feel like twitter could be a CDN and a CMS. Could make a "severless" blog that is just hijacking Twitter's server. Comments and media hosting built in!
There's no need to edit or delete. Treat Twitter as a changes feed. Encode your editions and deletions as new tweets.
Re: Base 2048
#27Re: Base 2048
#28Earlier quoted context omitted.
You can fit much more into a tweet if you consider image data, too.
Problem is that there's no guarantee that twitter won't apply lossy transformations to your data (in fact, it's guaranteed that it does). So either you would have to encode the data with lots of redundancy and/or error correction, or you have to encode in like, QR code or something similar, and rely on image recognition to extract it. Inside the range of characters support by twitter, your data is "guaranteed" to not…
[1] https://twitter.com/David3141593/status/1057042085029822464
[2] https://www.trendmicro.com/en_us/research/18/l/cybercriminal...
[3] https://twitter.com/miltinh0c/status/1392944896760238080
Re: Base 2048
#29Re: Base 2048
#30Earlier quoted context omitted.
Problem is that there's no guarantee that twitter won't apply lossy transformations to your data (in fact, it's guaranteed that it does). So either you would have to encode the data with lots of redundancy and/or error correction, or you have to encode in like, QR code or something similar, and rely on image recognition to extract it. Inside the range of characters support by twitter, your data is "guaranteed" to not…
In 2018 people discovered that Twitter would recompress images but leave the embedded ICC profile, if present, intact, and used that to make a Twitter-surviving JPEG+ZIP polyglot[1], although that got patched out once someone used it as a C&C channel[2]. Apparently that still worked (and was utilized for the same purpose) on Steam user profiles in 2021[3]. [1] https://twitter.com/David3141593/status/10570420850298224…