← Home ← Back to /g/

Thread 106181746

26 posts 4 images /g/
Anonymous No.106181746 >>106181853 >>106181916 >>106182257 >>106182318 >>106182523 >>106182960 >>106183423 >>106183450 >>106183457 >>106185781 >>106186958
How did he do it?
Anonymous No.106181786 >>106182761 >>106183524
vector graphics, unironically
Anonymous No.106181853
>>106181746 (OP)
He misunderstood a basic concept and then lied to investors
Anonymous No.106181903 >>106182523 >>106184242
Same way stable diffusion can "encode" a 1024x1024 image in 50 chars.
Anonymous No.106181916 >>106182233 >>106185748
>>106181746 (OP)
>refuses to elaborate
>dies
Anonymous No.106182233
>>106181916
kek
Anonymous No.106182257
>>106181746 (OP)
Take a look at the file size of a shortcut file.
Anonymous No.106182318 >>106182523 >>106185421
>>106181746 (OP)
either the decoder algorithm is the same size as the original film divided by 8
or the algorithm generates random bytes and compare it to the 8kb hash until it finds the correct one
Anonymous No.106182523
>>106181746 (OP)
>How did he do it?
a very common technique: lying. anything is possible that way.

>>106181903
> no really i am this retarded and have no idea what is actually happening right now

>>106182318
might as well just use a random number generator and chance your way to same result via brute force. it's all utter nonsense.
Anonymous No.106182555 >>106182682
NEW AND IMPROVED compression algorithm, compressing to a fixed 128 bits!
Just crack the hash to uncompress it!
$ md5sum m.lua
(hash goes here FUCK YOU spamfilter) m.lua
Anonymous No.106182682 >>106182718
>>106182555
but really, could you explain to a nocoder how hashes can be unique but incapable of reversing themselves to the actual file?
Anonymous No.106182718 >>106182731
>>106182682
hashes are never unique, you're trying to map a big amount of data to merely 128 bits, you're bound to have repetitions until your hash becomes as big as your file itself
Anonymous No.106182731 >>106182742
>>106182718
i see so i just understood them wrong, thanks
Anonymous No.106182742
>>106182731
even md5 has collisions
Anonymous No.106182761
>>106181786
You are retarded if you think vector graphics can go that low and can be used for camera images.
sage No.106182960 >>106183804
>>106181746 (OP)
this is too fucking stupid to even be bait
my instinct tells me he made this up after typing "8,192/24" into a calculator.
Anonymous No.106183423
>>106181746 (OP)
Anonymous No.106183450 >>106183804
>>106181746 (OP)
This can actually be done
Via correct lookup tables, movies can be compressed to sqrt(n) size
Anonymous No.106183457
>>106181746 (OP)
magnet links (torrents)
Anonymous No.106183524
>>106181786
are u for real nigga
Anonymous No.106183804
>>106183450
wouldn't that be dope, and FPGA with every movie ever made on it, just so that it can decode a file thats encoded to react specifically to that LUT. well it would only take about a trillion transistors or so to save on physical data storage costs
>>106182960
bro you can watch the entire movie of starwars through terminal in ascii, your concept of compression sucks dicks
Anonymous No.106184242
>>106181903
Interesting take...
Anonymous No.106185421
>>106182318
>or the algorithm generates random bytes and compare it to the 8kb hash until it finds the correct one
You would hit a collision long before you hit the right combination of bytes for your movie.
Anonymous No.106185748
>>106181916
"It was revealed to me in life"
Anonymous No.106185781
>>106181746 (OP)
holographic matrix mathematics
Anonymous No.106186958
>>106181746 (OP)
Placebo