You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.
I hope this is implemented in a way that changing file's or bucket's name does not change its ID. Keeping the ID the same would help clients to determine that a file or bucket has been renamed and not deleted.
👋 Hey! Thanks for this contribution. Apologies for the delay in responding!
We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat.
As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks!
This currently depends on deprecating deterministic id, see notices in https://github.com/Storj/service-storage-models/blob/master/lib/models/bucketentry.js#L15-L18
Changing the bucket name or file name does not affect how the file is encrypted.
The text was updated successfully, but these errors were encountered: