Unlimited Google Drive storage by splitting binary files into base64

Post by giomasce » Wed, May 15, 2019, 5:35 PM UTC

askl wrote: post #110

userbinator wrote: post #21

Base85 would probably be a better choice for storing binary as text, since it has a ratio of 5:4 instead of 4:3. On the topic of "unusual and free large file hosting", YouTube would probably be the largest, although you'd need to find a resilient way of encoding the data since their re-encoding processes are lossy. I like the "Linux ISO" and "1337 Docs" references ;-)

Or you could use BandcampFS https://github.com/tuxxy/BandcampFS https://bullswillriot.bandcamp.com/album/arch-linux-07-01

Post by JudgeWapner » Wed, May 15, 2019, 5:45 PM UTC

croon wrote: post #125

sagebird wrote: post #97

Earlier quoted context omitted.

It seems like a cute and irrelevant distinction that electronic software would be published in a book. If researchers created a computer that processed information using proteins in plant cells instead of electrons, and such a computer could execute programs on this book directly instead of “scanning” it, would not the textbook be software? When laws say “electronic versions” I don’t think they literally mean to refe…

IANAL, but if the distinction clashes with the crypto export laws, does it not follow that crypto export laws clash with the first amendment? Which then makes them unconstitutional and the focus should be on whether that is wanted behavior and the constitution should be amended, or not.

Post by mrmuagi » Wed, May 15, 2019, 5:47 PM UTC

DonHopkins wrote: post #76

In 1998, the EFF and John Gilmore published the book about "Deep Crack" called "Cracking DES: Secrets of Encryption Research, Wiretap Politics, and Chip Design". But at the time, it would have been illegal to publish the code on a web site, or include a CDROM with the book publishing the "Deep Crack" DES cracker source code and VHDL in digital form. https://en.wikipedia.org/wiki/EFF_DES_cracker https://www.foo.be/doc…

Post by beatgammit » Wed, May 15, 2019, 6:25 PM UTC

jerf wrote: post #202

markstos wrote: post #194

Earlier quoted context omitted.

Seems like a good way to earn yourself a Terms-of-Service ban. If this considered an abuse-of-services now, the terms could be updated to clarify. The finger print of big chunks of base-64 encoded blobs in Google Docs could be easy to spot. If Google cares to notice this and take action, they can and will.

It's an arms race situation. Once you give me an information channel like a "word document", I've got an endless variety of ways to encode other things into it. I can encode bits as English sentences or other things that will be arbitrarily hard to pick up by scanning. If I were Google, I wouldn't try to pick up on the content, I'd be looking for characteristic access patterns. It's harder to catch uploads, since "ne…

Post by wsgreen » Wed, May 15, 2019, 6:31 PM UTC