Open lidel opened 3 years ago
Regarding being able to POST to a gateway, I think it would be useful to support multipart/form-data
in order to upload a bunch of files at once.
E.g. using the FormData API in browsers: https://developer.mozilla.org/en-US/docs/Web/API/FormData
I've done some tests in the Agregore Browser and in the ipfs-protocol-compliance-suite and it's been pretty nice for ergonomics.
Here's what it could look like from a user's perspective:
const formData = new FormData()
formData.append('file', new Blob(['hello world!']), 'example1.txt')
formData.append('file', new Blob(['Goodbye World?']), 'example2.txt')
// Post to empty directory CID
const postResponse = await fetch('ipfs://bafybeiczsscdsbs7ffqz55asqdf3smv6klcw3gofszvwlyarci47bgf354/', {
method: 'POST',
body: formData
})
const newURL = await postResponse.text()
// newURL will be a directory with `example1.txt` and `example2.txt`
This will also play well with people using file inputs or drag and drop to upload data.
Created https://github.com/ipfs/specs/issues/375 for tracking ideas around "Writable Gateways"
We have distinct Gateway (/ipfs, /ipns) and API (/api/v0) endpoints today, and only the most basic read operations can be executed via Gateway.
Exposing
/api/v0
on the gateway was a mistake, and we need to work towards removing the need for it.The goal here would be to shift what is possible on the Gateway endpoints natively, so most popular operations like manipulating IPLD work without touching the advanced API.
Ordered improvements
Lower effort, high impact
Things well understood, with clear implementation plan:
/ipns/
"dropping only the branches that changed, not entire DAG" (https://github.com/ipfs/go-ipfs/pull/8720)High impact maintenance work
Things that do not add anything new, but need to happen to solve production issues, improve devexp, and create solid foundations for wider community to participate in Gateway work beyond MVP features listed in the section above.
Higher effort, high impact
Things that have extremely high impact, but need some additional research / design to happen.
POST /ipfs/
with support for IPLD content types (as a template foripfs://
behavior in browsers)"Mount any gateway CID root as a native read-only drive" (https://github.com/ipfs/in-web-browsers/issues/146)
Old Brainstorm
Below is the landscape of things worth considering.
No regrets
Things worth doing
?format=car|block|...
– https://github.com/ipfs/go-ipfs/issues/8234Other ideas
Big complexity and low impact for user running it on localhost.
resumable uploads
access controls?