Interesting and it’s useful data but obviously 50*73MB=3650MB c.f. 2000MB is little different.
Testnet4 appears stable but I don’t know really which bit of it needs pushing to the limit.
I wasn’t aware that limit is 500MB/vault… perhaps that follows from 5MB x 100 events.
If there was a trivial way to automate upload, I’d be tempted to try and break it but manual uploading individual files, is less fun. Perhaps need to look again at the API options … I recall seeing rust and Go flavours of those progressing somewhere that I wonder might lend themselves to testing.
Do you have the script/prog that generates the stats. ONe thing we have tried to figure is a good mechanism for network difficulty type setting. Well more what is network density, I suspect this is close to what you are doing, but I woudl be interested in accuracy. I suspect a few thousand nodes may have error, but the error will become manageable at some stage though. Finding that stage would be a big help.
Measuring network density around my vaults and averaging the results is exactly what I do. I also found out empirically that subtracting a fraction of standard deviation improved the result. See my post on the subject.
Yes, I think we can do better than that. But I am not specialist on the subject, you and people in your team are.
Finally the guilt of not running a vault consistently has gotten the better of me and I now have one running on a Windows 7 machine. The chunks I found placed in my vault was pretty immediate and of varying sizes.I need to install the vault software on a Raspberry Pi I have had for a while.
Will Test Net 4 be closed or could it be transitioned into being the stable developer network?
If I understand correctly Testnet 4 will be wiped at some point fairly soon so I’d keep local backups of all your proposed uploads, public and private.
Someone will correct me if I have this wrong, I’m sure.
The second is more common when requesting a subdomain that doesn’t exist but the first request was of a similar form and I think that the PublicID existed for both, so was expected two lots of the second error not mention of Core.
This links the url www.hob.safenet to the folder /www on the Safe network.
If you then try to access this service through a browser (e.g www.hob.safenet) it attempts to load www.hob.safenet/index.html which points to /www/index.html. If it fails to load this file then you will get the first error returned.
You can remove this error by posting to /nfs/file: