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
What if we enable WebRTC in fallback js-ipfs node?
In the past browsers had stability issues when js-ipfs run with webrtc transport for a long time.
We had various changes since then across the stack and the tab with share app will usually be closed after user is done with upload/download minimizing risk of it running for long enough to cause trouble.
Could WebRTC potentially..
improve discovery and performance of sharing app
give more merit to p2p claims made in copy/docs :)
build better understanding of how stable WebRTC transport is today, identify pain points and work towards addressing them in ipfs/libp2p/browser stack.
I'm for this, but not yet. I think we need to make "understanding WebRTC limits and tuning" a high priority. I'd rather have us dedicate focused time to understandting the root causes of the problem and the effects of the tuning options before enabling it again on an app.
What if we enable WebRTC in fallback js-ipfs node?
In the past browsers had stability issues when js-ipfs run with webrtc transport for a long time.
We had various changes since then across the stack and the tab with share app will usually be closed after user is done with upload/download minimizing risk of it running for long enough to cause trouble.
Could WebRTC potentially..
?
Refs:
The text was updated successfully, but these errors were encountered: