network VS web3.storage

This is amazing, great work! I love that it does everything in-browser.

A handful of questions:

Your currently uploading to a gateway and are considering moving to your own gateway backed by filecoin. Have you considered ditching the gateway and using the libp2p WebRTC and/or WebSocket protocols to upload directly to the network via the browser tab?

Where are you hosting this and how are you protecting against "supply chain attacks" where your hosting provider (either maliciously or through their service being compromised) injects additional JS that exfiltrates secrets? Have you explored managed/trusted upgrades to the existing user's apps through browser storage and a service worker? I don't know of any surefire ways to protect against the first delivered page being compromised, or a compromised browser environment, but could you lock down the upgrade path for the app for returning users by moving it outside of the page load path?

What is the migration path off of this? If I have this metadata file, how do I use it locally to fetch my encrypted files directly from the IPFS pinning server without having to return to your site?

How does multi-user access work?

What do you think the path to beating Google Drive on UI/UX is with P2P software?

---

We are working on a very similar problem to this right now, using the guts of IPFS and some stuff borrowed from Secure Scuttlebutt et. al. to manage encrypted files, identities, and capabilities. We also have a way to encrypt a file once and share individual per-user encryption keys on-demand bound to the user's private key. This lets the decryption keys be mirrored by nodes (i.e. put it on IPFS!). Next we are exploring UCAN for managing capabilities and granting access. And an overlay network to power it all. I'd love to compare notes with you.

Do you want a job? There is an open spot on my team working on exactly this stuff. Our goal is to build an SDK that enables these exact types of applications to be created.

Salary bands max out at $250k. Fully remote team, nomad friendly, 4 day work weeks. Time is spent roughly 50/50 implementing stuff and reading research papers (like Filecoin, IPFS, Scuttlebutt, etc.).

https://gitlab.com/webai-open/network/interview-challenge

For anyone who is interested in peer-to-peer systems like this, and completes Sarp's course, I have an open interview challenge you can submit it to if you find that you want to continue building in this space as a profession:

https://gitlab.com/webai-open/network/interview-challenge

Take the guidelines to heart though. We evaluate you on demonstrating understanding of what you did, not that you completed the course.

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.