YouTube has no limit on amount of video that you can upload. This means that it is effectively infinite cloud storage if you were able to embed files into video with some kind of tool. ISG (Infinite-Storage-Glitch) is the tool.
ISG is a program I wrote that lets you embed any files inside a video that survives compression on YouTube. They can be downloaded back and the files retrieved. This results in practically infinite storage space as long as YouTube doesn't start complaining.
This video is a demo of the program. Try the program on the video to see what files are inside (no it's not just a rick roll)
This seems like the other side of the coin to people exploiting free compute resources a la Github actions. Any website that hosts user data opens itself up to being used as storage. There's not...
This seems like the other side of the coin to people exploiting free compute resources a la Github actions. Any website that hosts user data opens itself up to being used as storage. There's not really a clear need for it for most. But a single file could be distributed across multiple sites being made up of reddit comments, youtube, comments, imgur pictures, and in this case youtube videos.
The encoding doesn't even need to be obvious if it's steganographically hidden. Which dramatically reduces the amount of data the medium could hold but likely wouldn't be noticed. The only people I can imagine interested in this are those looking to broadcast/store sensitive or illicit data.
Someone made a FUSE filesystem to store data in GMail, back when a few gigabytes of storage was a lot. You could also abuse the free tier of many data storage services via a Redundant Array of...
Any website that hosts user data opens itself up to being used as storage.
Someone made a FUSE filesystem to store data in GMail, back when a few gigabytes of storage was a lot.
You could also abuse the free tier of many data storage services via a Redundant Array of Independant Clouds, that's even simpler. I can't find the original blog post anymore, but someone signed up for Dropbox and just about every other free cloud storage service and made a RAID (or RAIC, I guess) out of all of them by striping data across the different sync folders...
There's not really a clear need for it for most. But a single file could be distributed across multiple sites being made up of reddit comments, youtube, comments, imgur pictures, and in this case youtube videos.
There's lots of creative ways to store data (see: Harder drives).
The encoding doesn't even need to be obvious if it's steganographically hidden. Which dramatically reduces the amount of data the medium could hold but likely wouldn't be noticed.
You could also apply some sort of forward error correction, such as Fountain codes, to guard against some of the posts/images getting removed.
That said, all of this is eminently impractical versus just uploading a file to Freenet or sharing it via .onion services...
Ultimately the result will be that services will be quota based. The end of “unlimited”. The Gmail trick is now pointless because Google now just has one storage quota across most services. There...
Ultimately the result will be that services will be quota based. The end of “unlimited”. The Gmail trick is now pointless because Google now just has one storage quota across most services. There is nothing to gain by embedding files in gmail.
YouTube is unlimited but there is no promise they will actually keep your files. If you upload 1TB of random noise videos, don’t be surprised if they just delete your channel.
This seems like the other side of the coin to people exploiting free compute resources a la Github actions. Any website that hosts user data opens itself up to being used as storage. There's not really a clear need for it for most. But a single file could be distributed across multiple sites being made up of reddit comments, youtube, comments, imgur pictures, and in this case youtube videos.
The encoding doesn't even need to be obvious if it's steganographically hidden. Which dramatically reduces the amount of data the medium could hold but likely wouldn't be noticed. The only people I can imagine interested in this are those looking to broadcast/store sensitive or illicit data.
Someone made a FUSE filesystem to store data in GMail, back when a few gigabytes of storage was a lot.
You could also abuse the free tier of many data storage services via a Redundant Array of Independant Clouds, that's even simpler. I can't find the original blog post anymore, but someone signed up for Dropbox and just about every other free cloud storage service and made a RAID (or RAIC, I guess) out of all of them by striping data across the different sync folders...
There's lots of creative ways to store data (see: Harder drives).
You could also apply some sort of forward error correction, such as Fountain codes, to guard against some of the posts/images getting removed.
That said, all of this is eminently impractical versus just uploading a file to Freenet or sharing it via .onion services...
Ultimately the result will be that services will be quota based. The end of “unlimited”. The Gmail trick is now pointless because Google now just has one storage quota across most services. There is nothing to gain by embedding files in gmail.
YouTube is unlimited but there is no promise they will actually keep your files. If you upload 1TB of random noise videos, don’t be surprised if they just delete your channel.