So here's the idea: I store a block and sound into my browser using the "Database" blocks from the "Libraries" section, and then I can take that data and play it onto another project, this way I can store as much as I want without worrying about the 10MB storage issues.
although, this is very much uncompressed. You can compress the costume/sound much more since there's quite a lot of repeating values. I just didn't want to go to the hassle of creating a script to compress them.
although, about why you wanted this
browser storage is saved locally on your machine, in your browser, so no one else will be able to get the data, including you if you use a different browser, or another device.
What if you told someone to download the same data you had (By storing said data on a different project and making them run it to store it on THEIR browser)?
Yes and no
Right now you can store only text so everything must be serialized.
Images/costumes can be serialized with "pixels of" reporter and "new costume".
Sounds with "samples of sound" and "new sound".
For blocks some form of codification/reverse must be used or XML format (requires JS).
So you'd have to include some form of codification and reverse codification to save and load blocks in browser storage. Blocks are a little harder than costumes and sounds.