arweave VS Peergos

For example, decentralized data storage projects like Filecoin, Arweave, and Sia posted 50-100% user growth, providing blockchain-powered alternatives to AWS, Google Cloud, and Dropbox for distributed app data security.

There are a few solutions:

https://www.arweave.org/

https://www.lighthouse.storage/

To me, they seem like the most useful stuff coming out of the blockchain industry.

Familiar DePIN initiatives include Helium, a Decentralized Wireless Network from 2019, Filecoin or Arweave for Cloud Storage.

Arweave is a permanent and decentralized web inside an open ledger.

The metadata in question is called “tags” on the Arweave blockchain. Tags are a list of keys and values you can add to your transactions to give the reader of that transaction additional information about it. They aren’t pre-defined by the protocol; you can add custom tags. But there are several specifications that try to standardize common tags.

Arweave

IPFS isn't the right use case for a dropbox clone. It behaves like a CDN with no persistence guarantees.

Arweave is better suited to archival storage. There are options for participants to ban particular types of content which may be illegal to host in their jurisdiction. This was designed to prevent the spread of CP, terrorism related info, etc. but that means it is also susceptible to DCMA issues too.

https://www.arweave.org/

Arweave is a community owned, decentralized and permanent data storage protocol. You can check it out here.

Another choice is Arweave.

A good Dropbox alternative is Peergos (founder here). Peergos is an E2EE P2P storage, sharing and application protocol. Fully open source, including the server, self-hostable, no VCs.

https://peergos.org

You can do that with peergos [1]- mount a peergos folder locally using FUSE. Or login to the web interface and share easily and privately.

[1] https://github.com/peergos/peergos

You might be interested in the p2p design of Peergos. You sign up to Peergos[0]. Your initial server is just responsible for storing your data (although you can run as many live mirrors as you like), and clients verify all updates. You can automatically move server (by running a command) and all your data is moved, and old links continue to work, and you keep your social graph and identity.

You can also log in through any instance, including localhost. Links also work on any server because they include a capability to the content in the link.

This is the beauty of content addressing plus public key based addressing.

[0] https://peergos.org

Totally agree! Shameless self promotion: have a look a Peergos - https://github.com/peergos/peergos

Our tech book might be a better starting point for this group: https://book.peergos.org

https://peergos.org

https://book.peergos.org

https://github.com/peergos/peergos

Features:

* audited by Cure53

* protects metadata (directory structure, file name and properties, file sizes, social graph)

* fine grained capability-based access control

* built-in social media

* sandboxed 3rd-party apps: e.g. word doc viewer, calendar, text editor, games etc.

* FUSE bindings

* CLI

* cross platform

* browser client

I use Peergos[0] for E2EE storage, doc editing, sharing media, calendar, kanban boards and social media. (Disclaimer: I also work on Peergos).

[0] https://peergos.org