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
{{ message }}
This repository was archived by the owner on Feb 12, 2024. It is now read-only.
Platform: Darwin neojuneui-MacBook-Pro-146.local 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64
Subsystem: -
Type: Question
Severity: very low
Description:
I've been trying to use js-ipfs functions without a daemon, I don't know if there's a way or not.
I wrote browser-side js code right below. and I share this code and result.
'ls' as well as other features like 'get', 'cat' didn't work.
No way to use js-ipfs without local daemon ever?
The text was updated successfully, but these errors were encountered:
hapsody
changed the title
A way which uses 'CDN' type to using js-ipfs in browser doesn't work.
A way which uses 'CDN' type to use js-ipfs in browser doesn't work.
Jul 5, 2019
There's no error here, your browser node is just not able to find or connect to a peer that has the content you're looking for.
You could use webrtc or websocket star rendezvous and relays to get better connectivity.
Please also note that JS IPFS doesn't have a DHT just yet so finding nodes with content is also more difficult from the browser.
We need better docs to explain the state of IPFS in the browser for people who don't know what the limitiations are. I'll open an issue and hopefulyl we can get it sorted.
Type: Question
Severity: very low
Description:
I've been trying to use js-ipfs functions without a daemon, I don't know if there's a way or not.
I wrote browser-side js code right below. and I share this code and result.
result>

I think it may because of config.Addresses attributes.
so I set some config attributes likt this but I couldn't make it.
'ls' as well as other features like 'get', 'cat' didn't work.
No way to use js-ipfs without local daemon ever?
The text was updated successfully, but these errors were encountered: