Important, but also there should be a disincentive for nodes getting too full. Some way to make sure nodes don’t go over something like 50% of their capacity, otherwise, if global disaster strikes and a huge amount of data needs re-spreading, then there might not be enough space. I’d suggest having junk ‘bonus’ data designed specifically to occupy node storage space.
Maybe for every chunk of user data stored, an equally-sized random bonus chunk could be stored on the same node, and presentation of both could be necessary for the full GET reward (if those are still a thing, if not then some equivalent).
If a node is offered a user chunk but is already full (of user chunks and bonus chunks), then the node should tell the others in its section that it is full rather than risk not getting a bonus for another chunk. If the section needs the node to take the chunk (due to catastrophe maybe), then it could exchange two of the node’s bonus chunks for a single bonus chunk applicable to two different user chunks.
Uploading various sized files indicates the lag on startup (larger files are faster because they can use the existing connection from the early chunks)
Ok, update on this, re-tried to cat the file and it now works fine…not sure what was happening before but please ignore and don’t waste time investigating that…weird stuff
seems like your upload stoped at the letter b? I imagine you have more mp3s with other first letters too?
so far 1909 mp3 files!
edit: NO! I was wrong! now there are 1961 mp3s in the container! so the upload continues normally but I guess its just a huge collection and it takes time to upload!
I found out how to restart the download with preserving the existing data and downloading only the new!
OK I wont waste any more time on that.
If we get similar reports we can raise an issue if need be.
Or as @Vort says, develop a more suitable tool.
I always have thought of cat as a hacky “internal” tool that would not be directly exposed in the long awaited API.
Just something to use in the early stages for proving to ourselves that it worked. Or didnt…
I think cat would be useful only with downloads as in you click download and it uses cat and you set the filename, but it would need some other tool to get what kind of file it is (extention) like .mp3
Yes the logs will be interesting. Perhaps some nodes were adults then promoted, but most likely, they started storing while the network was loading, and with no adults they stored the data. Anyway we need to analyse these logs and update everyone with the results.
Then we move on to the next test. We want to push into DBCs and then, after that have to pay for uploads (interesting problem) and so on.
Nodes form home is likely where there are silly comms bugs and that testnet will be interesting, but we are doing a lot of work in coms in parallel so that it may pull together at the right time. At least then all we are testing is comms and nodes from home.