web3.storage VS js-libp2p

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.

You can check out the full release notes at https://github.com/libp2p/js-libp2p/releases/tag/v0.31.0

It might not be what you are looking for, but you could have a look and experiment with libp2p. Plenty of stuff to build with that.

It takes place through the libp2p networking stack we use.

I am quite new to ipfs and peer to peer work. I am trying to build a simple app that leverages the P2P platform. I have an up and running nodejs libp2p node that can dial and connect with a second node on a separate test device. I am trying to save the second node to my primary node's peerstore. However I noticed that it is not persisted on restart. I followed the instructions here on configuring my node for peerstore persistence to the letter: https://github.com/libp2p/js-libp2p/blob/8e1fc78353cba194c86102dafcd68373b3f9a796/doc/CONFIGURATION.md#configuring-peerstore. However, when I set the secondary node again into my peerstore it still doesn't persist on restart. The setup above did create a mydb folder with log input however so it has definitely implemented a datastore. However I am not sure why my peerstore isn't saving to it.