Conversation
Co-authored-by: Marcin Rataj <[email protected]>
lidel
left a comment
lidel
left a comment
There was a problem hiding this comment.
Thank you for filling this.
I suggested some cosmetic changes + want to emphasize that having support for remote pinning in JS makes NFTs use case easier for dapp developers.
Co-authored-by: Marcin Rataj <[email protected]>
|
|
||
| Support has not been implemented in js-ipfs making this feature unavailable for web nodes, so teams building web3 products will need to contiune providing persistence through a backend as opposed to letting their users choose where their data gets persisted. | ||
|
|
||
| By implementing `pin remote` commands in js-ipfs we can enable ecosystem of web applications in which product users are empowered to choose where their data is persisted with almost no effort on teams building them. |
There was a problem hiding this comment.
this sounds potentially very valuable to ease the adoption/persistence of sites using js-ipfs. Can you collect some data from end users like textile/pinata/fission/others on what adding this API would unlock for their users? Where would we integrate this into the js-ipfs usage/onboarding flow? is there an example application / onboarding example that would become MUCH easier by using this instead?
There was a problem hiding this comment.
@jnthnvctr can maybe help connect data points on this.
There was a problem hiding this comment.
following up with some folks for feedback - will circle back here with more detail!
| --> | ||
|
|
||
| - Web3 is all about making users in charge of their data. This makes it possible out of the box without any additional effort. | ||
| - Enables a class of web3 applications that run all of the business logic at the edge to be backend free (app is deployed as a static bundle of html+js, users bring their data storage through pinning services). |
There was a problem hiding this comment.
how would this handle pinning service API tokens?
There was a problem hiding this comment.
how would this handle pinning service API tokens?
Implementation-vise application will obtain service endpoint+token from the user and add it to embedded js-ipfs node which will persist it in the browser storage. That said I hope this would prompt things like sign-in with pinata/textile/etc.. style interaction where users has to do nothing other than click a link which will take them to the desired service and redirect back passing all the endpoint+token information through query arguments.
|
Seems that relevant work is happening in ipfs/js-ipfs#3588 |
mikeal
added
confidence:high
|
ipfs/js-ipfs#3588 is missing DRI and did not land – is there a plan for one of projects to pick it up? |
5 participants
No description provided.