lidel

5 ms·

1. 1.▲
   by lidel 3y ago

   My understanding is that the curl position was around making sure UX (defaults) are safe and don't tie the user to any third-party gateway. Default behavior in the merged curl PR got adjusted and now the only gateway that is used impli
2. 2.▲
   by lidel 3y ago

   Web Browser use cases without native ipfs:// and ipns:// should use subdomain HTTP gateways like localhost in Kubo, or public dweb.link, cf-ipfs.com, which provide Origin per root CID, sandboxing web apps from each other
3. 3.▲
   by lidel 5y ago

   These libdweb Browser Extension APIs never landed in any official Firefox Nightly build. Mozilla stopped working on libdweb in 2019 ( https://github.com/ipfs/ipfs-companion/pull/533#issuecomment... ).
4. 4.▲
   by lidel 7y ago

   > I just installed 0.10.2 for Mac and it's by default using (600,900) for the low and high watermarks and routing type is set to dht rather than dhtclient. (600,900) watermarks suggest you had an old config (ipfs-desktop will respe
5. 5.▲
   by lidel 8y ago

   Keep in mind that HTTP gateways are provided just for convenience. Due to WebExtension API limitations embedded node can't act as a local HTTP gateway and extension falls back to public gateway. I imagine it was what you were experienc
6. 6.▲
   IPFS Companion 2.2.0 brings window.ipfs to your Browser(blog.ipfs.io)

   93 points by lidel 8y ago|25 comments