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
Given ipfs/js-ipfs#3588 we should ensure pinning services are useful in browser context.
While we could add an endpoint for direct DAG upload, we already have all necessary infrastructure for running bitswap session over websockets.
We should add some text to the spec indicating that /wss multiaddr on PinStatus.delegates list is highly recommended for public pinning services, as it maximizes utility beyond regular TCP/UDP and enables interaction with thin clients running on web pages.
The text was updated successfully, but these errors were encountered:
lidel
changed the title
Make /wss delegates mandatory
Document need for /wss on delegates list
May 5, 2021
@obo20 we started formalizing this, nothing urgent but do you mind sharing thoughts on this?
Are there relevant docs you could use when setting this up, or should we create them to make it easier for pinning services to set this up?
Given ipfs/js-ipfs#3588 we should ensure pinning services are useful in browser context.
While we could add an endpoint for direct DAG upload, we already have all necessary infrastructure for running bitswap session over websockets.
We should add some text to the spec indicating that
/wss
multiaddr onPinStatus.delegates
list is highly recommended for public pinning services, as it maximizes utility beyond regular TCP/UDP and enables interaction with thin clients running on web pages.The text was updated successfully, but these errors were encountered: