Base 2048 • Hacker News Board

Re: Base 2048

#31

Post by Dylan16807 » Sat, May 07, 2022, 5:09 PM UTC

vonwoodson wrote: post #12

That’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.

Well you don't have to use such a decadent encoding! If you aim to upload 10 seconds a day you could be done in a year and a half. 900KB can handle 10 seconds just fine, especially with a cutting-edge codec.

Re: Base 2048

#32

Post by _Algernon_ » Sat, May 07, 2022, 5:14 PM UTC

vonwoodson wrote: post #12

That’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.

Ib4 some masochist makes a streaming platform that uses twitter as a backend.

Re: Base 2048

#33

Post by divbzero » Sat, May 07, 2022, 5:19 PM UTC

What about encoding data for image tweets? QR codes are limited to a few kB of storage [1] because they are designed for visual scans, but using higher resolution could get you more capacity.

[1]: https://en.wikipedia.org/wiki/QR_code#Storage

Re: Base 2048

#34

Post by btown » Sat, May 07, 2022, 6:21 PM UTC

teaearlgraycold wrote: post #26

inportb wrote: post #24

Earlier quoted context omitted.

There's no need to edit or delete. Treat Twitter as a changes feed. Encode your editions and deletions as new tweets.

Git on Twitter then

A Twit-chain, if you will

Re: Base 2048

#35

Post by zamadatix » Sat, May 07, 2022, 6:41 PM UTC

vonwoodson wrote: post #12

That’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.

One of the funniest encoding things I've ever seen is Shrek encoded to just under 8 MB (128x72, 8 FPS, with audio! Actually understandable to watch, if only just barely). With this that would look to be 21,655 tweets or, using the API to post base65536 tweets, 14,888 tweets.

At 2,400 tweets per day that's just over 9 days for base2048 or just under a week for base65536. Doable!

Re: Base 2048

#36

Post by dhosek » Sat, May 07, 2022, 6:45 PM UTC

Retr0id wrote: post #17

rpastuszak wrote: post #15

Earlier 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.

Or the 1000 characters of the Alt tag. Since you can have multiple images per tweet, your limit just jumped without having to worry about images getting edited.

Re: Base 2048

#37

Post by graderjs » Sat, May 07, 2022, 7:14 PM UTC

Encode the text as an image, Tweet it, then use OCR to pull the text out. No more bit fiddling

Re: Base 2048

#38

Post by cylinder714 » Sat, May 07, 2022, 7:49 PM UTC

codetrotter wrote: post #25

Related but opposite, a tool I made a couple of years ago. https://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 purpos…

...This is brilliant, actually.

Re: Base 2048

#39

Post by teaearlgraycold » Sat, May 07, 2022, 8:30 PM UTC

btown wrote: post #34

teaearlgraycold wrote: post #26

Earlier quoted context omitted.

Git on Twitter then

A Twit-chain, if you will

Delete this comment now before you have a dozen offers from various VCs.

Re: Base 2048

#40

Post by Beltalowda » Sun, May 08, 2022, 2:33 AM UTC

wongarsu wrote: post #3

For comparison: A sha512 hash in hex: 309ecc489c12d6eb4cc40f50c902f2b4d0ed77ee511a7c7a9bcd3ca86d4cd86f989dd35bc5ff499670da34255b45b0cfd830e81f605dcf7dc5542e93ae9cd76f Same in this Base2048: ЗཟǷњϳݫЬߦՏԈ௰ڿƫ௪தͶޡഺཀވࡌੳٿ༲৩ত༥၄ঙџڸࠑحϷгଘƩƴߢய߅ϚƐγ๓ۑఞ The encoding also seems to be HN-safe, using no emojis or other things HN filters. The font used here is lacking some of the characters, but that shouldn't matter if you just copy-pa…

That base2048 string is 114 bytes (vs 129 for hex), so it's only significantly "shorter" in what you see, which isn't exactly human-readable (actually, less than the hex string; for a quick visual inspection comparing just the first and last 2 or 3 characters is enough, but that's a lot harder to do with all those unfamiliar Cyrillic, Tibetan, Tamil, Armenian, Arabic, Samaritan, Greek, etc. characters in there).