TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Unlimited Google Drive storage by splitting binary files into base64

585 pointsby lordpankakeabout 6 years ago

49 comments

reaperducerabout 6 years ago
Base64 is such a wonderful gift.<p>Back when the commercial internet was just getting its act together there were companies that would give you free online access on Windows 3.1 machines in exchange for displaying ads in the e-mail client. (I think one was called Juno.)<p>The hitch was that you could only use e-mail. No web surfing. No downloading files. No fun stuff.<p>But that&#x27;s OK, since there were usenet- and FTP-to-email gateways that you could ping and would happily return lists of files and messages. And if you sent another mail would happily send you base64-encoded versions of those binaries that you could decode on your machine.<p>The free e-mail service became slow-motion file sharing. But that was OK because you&#x27;d set it up before you went to bed and it would run overnight.<p>Thank you, whomever came up with base64.
评论 #19916745 未加载
评论 #19916623 未加载
评论 #19916361 未加载
评论 #19920010 未加载
评论 #19916630 未加载
评论 #19916628 未加载
评论 #19916818 未加载
whackabout 6 years ago
For anyone else who&#x27;s as confused as I initially was: Google Drive allows unlimited storage for anything stored as &quot;google docs&quot;. Ie, their version of Word. This hack works by converting your binary files into base64 encoded text, and then storing the text in collection of google-doc files.<p>Ie, it&#x27;s actually increasing the amount of storage space needed to store the same binary, but it&#x27;s getting around the drive-quota by storing it in a format that has no quota.
评论 #19919783 未加载
评论 #19919854 未加载
binwiederhierabout 6 years ago
In the same spirit, I made a few &quot;just for fun&quot; plugins for my (now abandoned) encrypted-arbitrary-storage Dropbox-like application Syncany:<p>The Flickr plugin [1] stores data (deduped and encrypted before upload) as PNG images. This was great because Flickr gave you 1 TB of free image storage. This was actually super cool, because the overhead was really small. No base64.<p>The SMTP&#x2F;POP plugin [2] was even nastier. It used SMTP and POP3 to store data in a mailbox. Same for [3], but that used IMAP.<p>The Picasa plugin [4] encoded data as BMP images. Similar to Flickr, but different image format. No overhead here either.<p>All of this was strictly for fun of course, but hey it worked.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;syncany&#x2F;syncany-plugin-flickr" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;syncany&#x2F;syncany-plugin-flickr</a><p>[2] <a href="http:&#x2F;&#x2F;bazaar.launchpad.net&#x2F;~binwiederhier&#x2F;syncany&#x2F;trunk&#x2F;files&#x2F;head:&#x2F;syncany&#x2F;src&#x2F;org&#x2F;syncany&#x2F;connection&#x2F;plugins&#x2F;pop3_smtp&#x2F;" rel="nofollow">http:&#x2F;&#x2F;bazaar.launchpad.net&#x2F;~binwiederhier&#x2F;syncany&#x2F;trunk&#x2F;fil...</a><p>[3] <a href="http:&#x2F;&#x2F;bazaar.launchpad.net&#x2F;~binwiederhier&#x2F;syncany&#x2F;trunk&#x2F;files&#x2F;head:&#x2F;syncany&#x2F;src&#x2F;org&#x2F;syncany&#x2F;connection&#x2F;plugins&#x2F;imap&#x2F;" rel="nofollow">http:&#x2F;&#x2F;bazaar.launchpad.net&#x2F;~binwiederhier&#x2F;syncany&#x2F;trunk&#x2F;fil...</a><p>[4] <a href="http:&#x2F;&#x2F;bazaar.launchpad.net&#x2F;~binwiederhier&#x2F;syncany&#x2F;trunk&#x2F;files&#x2F;head:&#x2F;syncany&#x2F;src&#x2F;org&#x2F;syncany&#x2F;connection&#x2F;plugins&#x2F;picasa&#x2F;" rel="nofollow">http:&#x2F;&#x2F;bazaar.launchpad.net&#x2F;~binwiederhier&#x2F;syncany&#x2F;trunk&#x2F;fil...</a>
评论 #19916196 未加载
评论 #19921555 未加载
justinjlynnabout 6 years ago
Sounds like a great way to lose your Google account (and all your other linked Google services) for ToS violations to me.
评论 #19916750 未加载
评论 #19916694 未加载
评论 #19918384 未加载
评论 #19916683 未加载
userbinatorabout 6 years ago
Base85 would probably be a better choice for storing binary as text, since it has a ratio of 5:4 instead of 4:3.<p>On the topic of &quot;unusual and free large file hosting&quot;, YouTube would probably be the largest, although you&#x27;d need to find a resilient way of encoding the data since their re-encoding processes are lossy.<p>I like the &quot;Linux ISO&quot; and &quot;1337 Docs&quot; references ;-)
评论 #19916205 未加载
评论 #19916167 未加载
评论 #19917815 未加载
评论 #19917359 未加载
评论 #19916162 未加载
评论 #19917116 未加载
furyofantaresabout 6 years ago
Even URL shorteners offer unlimited storage if you jump through enough hoops.<p>To encode ABCDEFGHIJKLMNOPQRSTUVWXYZ first get a short url for <a href="http:&#x2F;&#x2F;example.com&#x2F;ABC" rel="nofollow">http:&#x2F;&#x2F;example.com&#x2F;ABC</a>, then take the resulting url and append DEF and run it through the service again. Repeat until you run out of payload, presumably doing quite a few more than 3 bytes at a time.<p>The final short url is the your link to the data, which can be unpacked by stripping the payload bytes then following the links backwards until you get to your initial example.com node.
评论 #19920157 未加载
DonHopkinsabout 6 years ago
In 1998, the EFF and John Gilmore published the book about &quot;Deep Crack&quot; called &quot;Cracking DES: Secrets of Encryption Research, Wiretap Politics, and Chip Design&quot;. 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 &quot;Deep Crack&quot; DES cracker source code and VHDL in digital form.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;EFF_DES_cracker" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;EFF_DES_cracker</a><p><a href="https:&#x2F;&#x2F;www.foo.be&#x2F;docs&#x2F;eff-des-cracker&#x2F;book&#x2F;crackingdessecre00elec.pdf" rel="nofollow">https:&#x2F;&#x2F;www.foo.be&#x2F;docs&#x2F;eff-des-cracker&#x2F;book&#x2F;crackingdessecr...</a><p>&gt;&quot;We would like to publish this book in the same form, but we can&#x27;t yet, until our court case succeeds in having this research censorship law overturned. Publishing a paper book&#x27;s exact same information electronically is seriously illegal in the United States, if it contains cryptographic software. Even communicating it privately to a friend or colleague, who happens to not live in the United States, is considered by the government to be illegal in electronic form.&quot;<p>So to get around the export control laws that prohibited international distribution of DES source code on digital media like CDROMS, but not in written books (thanks to the First Amendment and the Paper Publishing Exception), they developed a system for printing the code and data on paper with checksums, with scripts for scanning, calibrating, validating and correcting the text.<p>The book had the call to action &quot;Scan this book!&quot; on the cover (undoubtedly a reference to Abby Hoffman&#x27;s &quot;Steal This book&quot;).<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Steal_This_Book" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Steal_This_Book</a><p>A large portion of the book included chapter 4, &quot;Scanning the Source Code&quot; with instructions on scanning the book, and chapters 5, 6, and 7 on &quot;Software Source Code,&quot; &quot;Chip Source Code,&quot; and &quot;Chip Simulator Source Code,&quot; which consisted of pages and pages of listings and uuencoded data, with an inconspicuous column of checksums running down the left edge.<p>The checksums in the left column of the listings innocuously looked to the casual observer kind of like line numbers, which may have contributed to their true subversive purpose flying under the radar.<p>Scans of the cover and instructions and test pages for scanning and bootstrapping from Chapter 4:<p><a href="https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;7pHSAT1" rel="nofollow">https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;7pHSAT1</a><p>(My small contribution to the project was coming up with the name &quot;Deep Crack&quot;, which was silkscreened on all of the chips, as a pun on &quot;Deep Thought&quot; and &quot;Deep Blue&quot;, which was intended to demonstrate that there was a deep crack in the United States Export Control policies.)<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;EFF_DES_cracker#&#x2F;media&#x2F;File:Chip300.jpg" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;EFF_DES_cracker#&#x2F;media&#x2F;File:Ch...</a><p>The exposition about US export control policies and the solution for working around them that they developed for the book was quite interesting -- I love John Gilmore&#x27;s attitude, which still rings true today: &quot;All too often, convincing Congress to violate the Constitution is like convincing a cat to follow a squeaking can opener, but that doesn&#x27;t excuse the agencies for doing it.&quot;<p><a href="https:&#x2F;&#x2F;dl.packetstormsecurity.net&#x2F;cracked&#x2F;des&#x2F;cracking-des.htm" rel="nofollow">https:&#x2F;&#x2F;dl.packetstormsecurity.net&#x2F;cracked&#x2F;des&#x2F;cracking-des....</a><p>Chapter 4: Scanning the Source Code<p>In This chapter:<p>The Politics of Cryptographic Source Code<p>The Paper Publishing Exception<p>Scanning<p>Bootstrapping<p>The next few chapters of this book contain specially formatted versions of the documents that we wrote to design the DES Cracker. These documents are the primary sources of our research in brute-force cryptanalysis, which other researchers would need in order to duplicate or validate our research results.<p>The Politics of Cryptographic Source Code<p>Since we are interested in the rapid progress of the science of cryptography, as well as in educating the public about the benefits and dangers of cryptographic technology, we would have preferred to put all the information in this book on the World Wide Web. There it would be instantly accessible to anyone worldwide who has an interest in learning about cryptography.<p>Unfortunately the authors live and work in a country whose policies on cryptography have been shaped by decades of a secrecy mentality and covert control. Powerful agencies which depend on wiretapping to do their jobs--as well as to do things that aren&#x27;t part of their jobs, but which keep them in power--have compromised both the Congress and several Executive Branch agencies. They convinced Congress to pass unconstitutional laws which limit the freedom of researchers--such as ourselves--to publish their work. (All too often, convincing Congress to violate the Constitution is like convincing a cat to follow a squeaking can opener, but that doesn&#x27;t excuse the agencies for doing it.) They pressured agencies such as the Commerce Department, State Department, and Department of Justice to not only subvert their oaths of office by supporting these unconstitutional laws, but to act as front-men in their repressive censorship scheme, creating unconstitutional regulations and enforcing them against ordinary researchers and authors of software.<p>The National Security Agency is the main agency involved, though they seem to have recruited the Federal Bureau of Investigation in the last several years. From the outside we can only speculate what pressures they brought to bear on these other parts of the government. The FBI has a long history of illicit wiretapping, followed by use of the information gained for blackmail, including blackmail of Congressmen and Presidents. FBI spokesmen say that was &quot;the old bad FBI&quot; and that all that stuff has been cleaned up after J. Edgar Hoover died and President Nixon was thrown out of office. But these agencies still do everything in their power to prevent ordinary citizens from being able to examine their activities, e.g. stonewalling those of us who try to use the Freedom of Information Act to find out exactly what they are doing.<p>Anyway, these agencies influenced laws and regulations which now make it illegal for U.S. crypto researchers to publish their results on the World Wide Web (or elsewhere in electronic form).<p>The Paper Publishing Exception<p>Several cryptographers have brought lawsuits against the US Government because their work has been censored by the laws restricting the export of cryptography. (The Electronic Frontier Foundation is sponsoring one of these suits, Bernstein v. Department of Justice, et al ).* One result of bringing these practices under judicial scrutiny is that some of the most egregious past practices have been eliminated.<p>For example, between the 1970&#x27;s and early 1990&#x27;s, NSA actually did threaten people with prosecution if they published certain scientific papers, or put them into libraries. They also had a &quot;voluntary&quot; censorship scheme for people who were willing to sign up for it. Once they were sued, the Government realized that their chances of losing a court battle over the export controls would be much greater if they continued censoring books, technical papers, and such.<p>Judges understand books. They understand that when the government denies people the ability to write, distribute, or sell books, there is something very fishy going on. The government might be able to pull the wool over a few judges&#x27; eyes about jazzy modern technologies like the Internet, floppy disks, fax machines, telephones, and such. But they are unlikely to fool the judges about whether it&#x27;s constitutional to jail or punish someone for putting ink onto paper in this free country.<p>* See <a href="http:&#x2F;&#x2F;www.eff.org&#x2F;pub&#x2F;Privacy&#x2F;ITAR_export&#x2F;Bernstein_case&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.eff.org&#x2F;pub&#x2F;Privacy&#x2F;ITAR_export&#x2F;Bernstein_case&#x2F;</a> .<p>Therefore, the last serious update of the cryptography export controls (in 1996) made it explicit that these regulations do not attempt to regulate the publication of information in books (or on paper in any format). They waffled by claiming that they &quot;might&quot; later decide to regulate books--presumably if they won all their court cases -- but in the meantime, the First Amendment of the United States Constitution is still in effect for books, and we are free to publish any kind of cryptographic information in a book. Such as the one in your hand.<p>Therefore, cryptographic research, which has traditionally been published on paper, shows a trend to continue publishing on paper, while other forms of scientific research are rapidly moving online.<p>The Electronic Frontier Foundation has always published most of its information electronically. We produce a regular electronic newsletter, communicate with our members and the public largely by electronic mail and telephone, and have built a massive archive of electronically stored information about civil rights and responsibilities, which is published for instant Web or FTP access from anywhere in the world.<p>We would like to publish this book in the same form, but we can&#x27;t yet, until our court case succeeds in having this research censorship law overturned. Publishing a paper book&#x27;s exact same information electronically is seriously illegal in the United States, if it contains cryptographic software. Even communicating it privately to a friend or colleague, who happens to not live in the United States, is considered by the government to be illegal in electronic form.<p>The US Department of Commerce has officially stated that publishing a World Wide Web page containing links to foreign locations which contain cryptographic software &quot;is not an export that is subject to the Export Administration Regulations (EAR).&quot;* This makes sense to us--a quick reductio ad absurdum shows that to make a ban on links effective, they would also have to ban the mere mention of foreign Universal Resource Locators. URLs are simple strings of characters, like <a href="http:&#x2F;&#x2F;www.eff.org;" rel="nofollow">http:&#x2F;&#x2F;www.eff.org;</a> it&#x27;s unlikely that any American court would uphold a ban on the mere naming of a location where some piece of information can be found.<p>Therefore, the Electronic Frontier Foundation is free to publish links to where electronic copies of this book might exist in free countries. If we ever find out about such an overseas electronic version, we will publish such a link to it from the page at <a href="http:&#x2F;&#x2F;www.eff.org&#x2F;pub&#x2F;Privacy&#x2F;Crypto_misc&#x2F;DESCracker&#x2F;" rel="nofollow">http:&#x2F;&#x2F;www.eff.org&#x2F;pub&#x2F;Privacy&#x2F;Crypto_misc&#x2F;DESCracker&#x2F;</a> .<p>* In the letter at <a href="http:&#x2F;&#x2F;samsara.law.cwru.edu&#x2F;comp_law&#x2F;jvd&#x2F;pdj-bxa-gjs070397.htm" rel="nofollow">http:&#x2F;&#x2F;samsara.law.cwru.edu&#x2F;comp_law&#x2F;jvd&#x2F;pdj-bxa-gjs070397.h...</a>, which is part of Professor Peter Junger&#x27;s First Amendment lawsuit over the crypto export control regulations.<p>[...]
评论 #19919126 未加载
评论 #19917184 未加载
评论 #19918452 未加载
评论 #19917328 未加载
评论 #19921898 未加载
reneberlinabout 6 years ago
I think in the long run, the user could risk the complete google-account if they begin rating the uploads a violation of TOS.<p>I advise a totally seperate account when using this tool.<p>But anyways, something inside me likes it. Nicely done. Good job :)
评论 #19916195 未加载
评论 #19917667 未加载
评论 #19916585 未加载
nemosaltatabout 6 years ago
Anyone remember Gdrive? I can’t find it now, but I think it was probably early or mid 2000s. It let you store files as a local disk (FUSE) via Gmail attachments.
评论 #19916272 未加载
评论 #19917018 未加载
评论 #19918570 未加载
joebergeronabout 6 years ago
Me and a friend came up with a similar idea of a sort of distributed file system implemented across a huge array of blog comment sections. Of course you’d need a bunch of replication and fault tolerance and the ability to automatically scrape for new blogs to post spammy-looking comments on, but I thought it was a pretty funny and neat idea when we came up with it.
评论 #19917580 未加载
评论 #19919423 未加载
评论 #19916601 未加载
评论 #19916800 未加载
评论 #19916792 未加载
markbnjabout 6 years ago
Very neat, but it seems to me the issue with all wink-wink schemes like this is that you&#x27;re ultimately getting something that wasn&#x27;t explicitly promised, and so might be taken away at any time. So while interesting you couldn&#x27;t really ever feel secure storing anything that mattered this way.
评论 #19917306 未加载
Scaevolusabout 6 years ago
You can also just use GSuite with a few users to get unlimited Google Drive storage.<p><a href="https:&#x2F;&#x2F;support.google.com&#x2F;a&#x2F;answer&#x2F;139019?hl=en#6_storage" rel="nofollow">https:&#x2F;&#x2F;support.google.com&#x2F;a&#x2F;answer&#x2F;139019?hl=en#6_storage</a>
评论 #19916611 未加载
评论 #19916111 未加载
评论 #19917719 未加载
wmichelinabout 6 years ago
Someone is going to notice a few accounts with insanely high storage usage, and then comes the ban-hammer. Enjoy losing your Google account!
评论 #19916454 未加载
评论 #19916637 未加载
thrownaway954about 6 years ago
Honestly this isn&#x27;t ground breaking, we have been using BASE64 to convert binary to ASCII as a way of &quot;sharing&quot; files all the way to USENET days. While applications like these make it easy for the masses to participate in the idea, they don&#x27;t bring anything new to the table.<p>That all said, this is really cool from a design perspective and I poured over the code learned a lot.
评论 #19917661 未加载
kccqzyabout 6 years ago
Google doc allows you to upload images from your computer. Why not just do that? With proper steganography no one will bat an eye on a few docs with some multi-megabyte pictures.
_bxg1about 6 years ago
I had an (evil; don&#x27;t do this) idea a while back to create a Dropbox-like program that stores all your data as binary chunks attached to draft emails spread across an arbitrary number of free email accounts.
评论 #19916087 未加载
评论 #19917213 未加载
评论 #19917059 未加载
评论 #19919449 未加载
robador51about 6 years ago
I may be mistaken, but as far as I&#x27;m aware Google docs synced to your local machine are nothing more than links to documents in the Google Drive cloud. None of the data inside those docs is actually stored locally. I found this out the hard way when I decided to move away from GD and lost a lot of files.<p>So buyer beware I guess.
评论 #19917639 未加载
morpheuskafkaabout 6 years ago
You could do the same thing with QR codes in Google Photos, the compression required for unlimited storage wouldn&#x27;t affect them.
retroplasmaabout 6 years ago
Related: unlimited private incremental storage on Usenet (concept):<p><a href="https:&#x2F;&#x2F;gist.github.com&#x2F;retroplasma&#x2F;264d9fed2350feb19f977575981bb914#idea" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;retroplasma&#x2F;264d9fed2350feb19f977575...</a><p>TL;DR: An alternative to NZB, RAR and PAR2. Private &quot;magnet-link&quot; that points to encrypted incremental data.
Causality1about 6 years ago
Reminds me of the old programs that would turn your Gmail storage into a network drive by splitting everything into 25MB chunks. Utterly miserable experience with terrible latency and reliability.
评论 #19917040 未加载
评论 #19916641 未加载
评论 #19919001 未加载
MatthewRayfieldabout 6 years ago
I couldn&#x27;t find it with a quick search, but I remember many years ago someone creating a similar scheme for storing files inside of TinyURLs.<p>You would run the uploader and get back a list of TinyURLs that could then be used to retrieve the files later with a downloader.<p>But you couldn&#x27;t store too much in each URL so the resulting list could be pretty big.
评论 #19917942 未加载
评论 #19918124 未加载
anonuser123456about 6 years ago
Because I&#x27;m sure Google has NO data on pathalogical docs file sizes. I can&#x27;t wait for the follow on &#x27;Google banned my account with all my life&#x27;s data that I didn&#x27;t back up anywhere for no good reason&#x27;
blackflame7000about 6 years ago
I wonder if this could be used to create a P2P network like bit torrent except trackers point to blocks at google doc urls instead of peers&#x2F;seeds
评论 #19917490 未加载
loftiesabout 6 years ago
Very cool! About a year ago I had a similar idea, but to store arbitrary data in PNG chunks[1] and upload them to &quot;unlimited&quot; image hosts like IMGUR and Reddit.<p>[1] <a href="http:&#x2F;&#x2F;blog.brian.jp&#x2F;python&#x2F;png&#x2F;2016&#x2F;07&#x2F;07&#x2F;file-fun-with-pyhon.html" rel="nofollow">http:&#x2F;&#x2F;blog.brian.jp&#x2F;python&#x2F;png&#x2F;2016&#x2F;07&#x2F;07&#x2F;file-fun-with-pyh...</a>
评论 #19921551 未加载
mikorymabout 6 years ago
So, are the +- 700 kB files too small to register as taking up any space?
评论 #19917633 未加载
kyrraabout 6 years ago
Not so unlimited given these restrictions: <a href="https:&#x2F;&#x2F;developers.google.com&#x2F;apps-script&#x2F;guides&#x2F;services&#x2F;quotas" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;apps-script&#x2F;guides&#x2F;services&#x2F;qu...</a>
mirimirabout 6 years ago
Could someone please ELI5 how Google Drive doesn&#x27;t include text files toward usage?
评论 #19916203 未加载
irrationalabout 6 years ago
I&#x27;ve wondered if someone could do the same thing with videos and jpgs. Amazon prime, as one example, allows you to store an unlimited number of image files for &quot;free&quot;. What if there was a program that would take a video file and split it up into its individual frames as jpgs and stored them on Amazon prime. When you wanted to watch the video the program would rebuild the video file from the individual jpgs on AWS.
评论 #19919164 未加载
giomasceabout 6 years ago
To me it looks like iodine (<a href="https:&#x2F;&#x2F;code.kryo.se&#x2F;iodine&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.kryo.se&#x2F;iodine&#x2F;</a>): very nice as a hacking tool to prove a point, but unlikely to be actually helpful in all but very peculiar situations. As a hacker, of course, I value a lot the first part of it!
oldman123456789about 6 years ago
I do the same on a different cloud storage provider. I won&#x27;t name it because I don&#x27;t want to be banned from it!
yeukhonabout 6 years ago
I don’t know anyone remember but some years ago I remember seeing a file compressed from 1GB to 1mb. And I was amazed.
评论 #19917387 未加载
评论 #19921044 未加载
评论 #19917120 未加载
wsgreenabout 6 years ago
Nice! I did a similar hack to get unlimited Dropbox space by creating many accounts and distributing the files across the accounts.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;WarrenGreen&#x2F;InfiniteDrop" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;WarrenGreen&#x2F;InfiniteDrop</a>
yaloginabout 6 years ago
How is this different from encrypting the binary locally, and store the result as hex strings?
评论 #19919299 未加载
anilakarabout 6 years ago
Correction: unlimited as long as it takes Google to fix this oversight in quota calculation.
评论 #19917659 未加载
baroffoosabout 6 years ago
Has anyone actually tried storing a large amount of data like this? I feel like creating a new google account and using it as a backup for a 300gb folder I have.
评论 #19923841 未加载
评论 #19918505 未加载
nichocharabout 6 years ago
This is very clever, and a neat interface.<p>On the one hand, I think this is great, on the other, I hope it doesn&#x27;t force google to add limits that bother me in the future :P
zelon88about 6 years ago
Couldn&#x27;t you also embed data into images and upload them to Google photos, or is that discarded when they convert and compress the image in the backend?
评论 #19916039 未加载
评论 #19917652 未加载
kevingrahlabout 6 years ago
I think I already saw this a few (&gt;6) months ago on reddit, have you changed&#x2F;improved anything in the meantime?
purplezooeyabout 6 years ago
Damn 4:3? That ain&#x27;t too bad.
评论 #19917220 未加载
localhostdotdevabout 6 years ago
already better than s3 :) makes me think of <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;DataHoarder&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;DataHoarder&#x2F;</a>
borplkabout 6 years ago
So what makes the data not count against the usage?
karjudevabout 6 years ago
It&#x27;s such a weird trick that I love it!
dogma1138about 6 years ago
Google UseNet.
laylomo2about 6 years ago
Thinking outside the box.
sdanabout 6 years ago
Nice!
gaspoweredcatabout 6 years ago
very clever, well done!
评论 #19917658 未加载
评论 #19916058 未加载
oyebennyabout 6 years ago
ELI5 please?
评论 #19917420 未加载
booleandilemmaabout 6 years ago
Google, give this man a job!
jonnycomputerabout 6 years ago
Too bad there is no similar trick for atmospheric carbon.
评论 #19949966 未加载