-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve naming in the blob spec #119
Comments
Hi @Gozala , is this issue still open? I'd love to work on it :) |
Hey @Khwahish29 I'm no longer with the team and not sure what is currently being worked on. I think @travis might be a good person to chat if you're interested in contributing to an ongoing project. |
Hi @Khwahish29! Yea unfortunately this isn't super actionable right now - we're probably not going to pursue name changes for abilities until after we transition to UCAN 1.0 at the very least. I'm going to leave this open so we don't lose this suggestion, but may close this after some project gardening in the future. |
Per storacha/w3up#1342 (comment)
I think it is worth doing, especially because while discussing federated storage network it came clear that w3up will likely look for a suitable storage node candidate(s) and perform allocation with them. That is to say
memory/allocate
andmemory/commit
would make even more sense then. On the other handspace
parameter makes very little sense in that context.The text was updated successfully, but these errors were encountered: