ipfs VS web3.storage

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.

https://web3.storage/ https://estuary.tech/

I'm building Flash — a service to deploy websites and apps on the new decentralized stack. It relies on public infrastructure (such as Estuary, web3.storage and others) instead of providing its own, making the bandwidth and storage very cheap and accessible.

https://web3.storage/ does everything you need

Web3.Storage and other similar projects run a network of IPFS nodes that allow users to store whatever content they like, as a kind of competitor to Dropbox or Google Drive: this could be their personal content, or again, any application content, because some apps integrate directly with this service via their API

You can file this as an issue in the repo here and perhaps mention to them that, as a user, it feels phishy to you.

Typically app developers would be the ones to build on Filecoin and you would choose an app like web3.storage to store your data. As a consumer you dont have to directly hold FIL but you benefit from the Filecoin ecosystem.

Filecoin may not have a front-end but our team has worked on https://estuary.tech and it has been easy for our users that have an invite to onboard to the Filecoin Network, another great option is https://web3.storage

clone repos to your computer, dont just fork them

the fork disappears when the parent repository is taken down, clones stay on your machine

upload to IPFS. you can pin on IPFS for free with filecoin. Use filecoin nodes to pin on ipfs at https://web3.storage

As for storing data on Filecoin directly, that would require making a deal with a Filecoin Storage Provider; doing so is currently a complex task but reading the documentation should get you somewhere. You will need a small amount of the FIL token to make the deal with an SP, who will then store your data. Keep in mind that something like web3.storage or Estuary.tech may be better for your needs if you need easy access to the files later; Filecoin can (currently) be thought of as closer to archival storage, but efforts are being made to make it more generally useful too.