Closed lidel closed 3 years ago
Got approval for general direction from the first batch of stakeholders:
π£ It is ok to start implementing the API, and provide feedback / questions as you go (create issue in this repo)
FYSA we dont expect groundbreaking changes, but there are some field-specific tweaks/clarifications suggested during internal review, pending community review: /pulls β PRs with filtering by metadata, queued status, removal of unpinned state https://github.com/ipfs/pinning-services-api-spec/issues/33 β temperature check: should pin object include creation date?
I think the pulls link is auto-linking to something broken for some reason. Here is the fresh link: https://github.com/ipfs/pinning-services-api-spec/pulls
FYSA we will merge improved Error responses (https://github.com/ipfs/pinning-services-api-spec/pull/59) on Monday and release as v0.1.0
Client implementation in go-ipfs is wip.
About
This issue tracks overall finalization status of this spec from the perspective of being ready for stakeholders to start implementation of basic functionality.
cc @jacobheun @pooja @jessicaschilling
Stakeholders
Remaining Issues
While mostly ready, we need to resolve these issues before API can be fully implemented:
Additional endpoint for GUI apps that enables user onboarding without copying secrets as noted in https://github.com/ipfs/pinning-services-api-spec/issues/6#issuecomment-656404675Stakeholder Sign-offs