bitcore VS ipfs

bitcore-lib

https://github.com/bitpay/bitcore <-- server code the wallet communicates with

[4:28 PM] Jeroz: Also, the insight explorer was deprecated in 2019, and it might be a good idea to upgrade that to https://github.com/bitpay/bitcore/tree/master/packages/insight for that devkit bounty.

You can use bitpay's bitcore library, which includes support for Litecoin. I'm not sure why though, but the npm link is wrong and links to the archived repo. The actual mono repo is: https://github.com/bitpay/bitcore

All the bitcore-lib repos are part of the mono repo. It's all there at https://github.com/bitpay/bitcore/tree/master/packages

Thanks for the advice, I will try https://github.com/bitpay/bitcore then (I think this is the up-to-date version). I will try to figure out how to get it running for Litecoin.

Bitcore - Pure and powerful Bitcoin library.

I don't mind pinning, but back in the day I was having issues using IPFS to transfer small files between devices. I admit I haven't investigated to see if the problems were ever resolved.

I've been watching https://github.com/ipfs/helia which is going to replace https://github.com/ipfs/js-ipfs and hoping they can get an IPFS node working in the browser.

I haven't tried https://js.ipfs.tech/ (js-ipfs) in a while, what is the state of it?

On the topic of IPFS, but also slightly tangential -- how has nobody written an Activity Pub client/server in Javascript and distributed it as a Browser Addon?

If IPFS can be literally hosted via a Firefox Extension[1], how has nobody done the same for an arguably easier protocol like Activity Pub?

1: https://github.com/ipfs/js-ipfs

If you can load them up in js-ipfs that might be better?

Store the content in ipfs and just put the hash in the URL? I haven't used https://github.com/ipfs/js-ipfs in this capacity but I'm under the impression that that's what it's supposed to do.

js.ipfs.tech

You need an import statement instead of require since Node has upgraded to the new module system. Use import * as IPFS from 'ipfs-core'. Read more here: https://github.com/ipfs/js-ipfs

Please take a look at https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md for more understanding

You could include js-ipfs[0] and fetch all your resources from IPFS without going through a gateway. However, this approach would make the site fully dependent on JavaScript.

A PWA with a Service Worker could perhaps implement its own client-side "gateway", translating public gateway URLs into direct IPFS access. Without the Service Worker (or without JS) it would fall back to using the gateway.

[0] https://js.ipfs.io/

Of course,You can try it out. You can create some Hash to IPFS from this link Adding data to IPFS https://js.ipfs.io/ and then browse the hash in https://ipfs-gateway.cloud/ It is directly connected to IPFS Node.