“Explicit deletions” is a very good and accurate term instead of direct deletes. I shall use that, that makes it more clear.
Well it is my understanding that one additional advantage would be that there does not have to be a trash for explicit deletions. If that is true or could be implemented in such way that for those files a trash with a layover over 7 days or more is not required, that would be a major advantage for the SNOs.
Yeah, I’m not so sure about that. Considering the complications with server side copy, it might be necessary to keep that safety margin. There could be other such scenarios in the future.
2 Likes
Aren’t such things normally solved with a journal or something?
The question is, how much time do we really need to verify that a piece can be deleted safely. I doubt this requires 7 days. If it would take let’s say 24 hours to have those pieces remaining in the trash this would still be a major improvement compared to today.
1 Like
I believe that 48h should be safe enough.
Using the network itself for delivering important data regarding the network might explode horribly at some point. If some update has an error or something. The whole network might collapse because it depends on itself.
3 Likes
For honestly we do backups to Storj too. And use it for BF.
You know, eat your own dog food.
1 Like