the costs of storing are the same if I split a file or not…
It’s not on web3 at the moment…
Wen implement?
Would like to increase my size now 
This is a poll, not a governance proposal, you still have two stages to pass
already on its way. enhancements beyond the neccessity of actually doing anything once implemented.
After contacting Nico and the foundation, it seems my approach has been a hack around how the scene is checked, so that’s worked for me for a while, but it’s not legitimate or formal. Maybe with the new client will not work even . So its definitely a good proposal to proceed with.
Not sure about the cost of storing an additional 15MB for each land, which would double our current storage size. This requires a feasibility study by whoever will be covering the storage expenses. I believe the DAO could help with covering the costs once this proposal is approved, with guidance and follow-up from the foundation.
In the worst case scenario, it might be good to do it like the Worlds—where more MANA in your wallet means more storage for your scene.
1 Like
True. The current World Server is run by the Foundation correct? With the 17 names and 1 land i have, i have 2.3gb of storage available. Not sure what would happen if I tried to deploy to only 1 name with over 1gb of a scene?
Regardless, it seems like there’s already a scalable solution in place from their side. We should continue to inspect and push towards greater scene limits to enhance player experiences with the new client.
The biggest world I deployed last month was around 800 MB. I faced problems during deployment, and each time I modify something, it took many attempts to re-deploy. I guess this is because it’s a centralized server related to the foundation and not like Genesis
Even though I deployed an 800 MB world, I remember they mentioned in the foundation server that the maximum size for a world is 500 MB. The documentation does not clearly state that the maximum is 500 MB and only mentions it in this paragraph.
1 Like
Interesting! So the cap in GC is 300mb…a 500mb ceiling for GC is a 66% increase…
At current limitations, that would be 500mb / (15mb per parcel) = 33 parcels
Potential per parcel limit increase: 15mb -> 20mb = 500 / 20 = 25 parcels
I personally like function (number of parcels) x (parcel limit) = total scene limit how its, but let’s bump up those limits a bit!
I used to upload a 2 hour dj set so that people wouldn’t get bored of the music…
I had room for more but that would crash the scene (especially with too many users)…
Anyone can cut music/video/.glb/picture into 15mb snippets but it makes the experience worse for everyone…
Is this a separate proposal?
Yes, this one is about total file storage size, not individual file storage size.
In the end, the pain-point mostly seems not to be storage per parcel, but storage of the files needed to run the whole collection of parcels (e.g. the javascript and streaming media).
So we really should have something like this:
total scene limit = base scene allowance + (number of parcels) x (parcel allowance)
Also the parcel allowance doesn’t necessarily have to be increased all the way to 30MB, smaller values should be considered as well.
Done
No. It’s both.
Increase the file size per parcel AND do not include the built index.js file towards that limitation.