[buildanduse]

For storage, My Cloud and other centralized systems (e.g. QNAP and Synology offerings) give some usability, but they are limited to storage and still use a central server. We are trying to get Diode tech widely adopted - it is a network that enables N to N private, fully trustless, tunnels. We implemented dDrive (https://support.diode.io/article/irhluyq82j) over it (in Alpha) that can map any storage (laptop, server, NAS, etc...) so that peers can privately access, or so that you can easily share files without having to use centralized storage / email. Telegram group at https://t.me/diode_chain.

[ajvs]

What's the pros/cons vs Syncthing?

[buildanduse]

Great question - probably three differences: 1) Syncthing is storage only - Diode has dDrive for storage, but also supports N other use cases as a true web3 backbone candidate (e.g. currently deployed: video streaming, VPN, decentralized web hosting, remote SSH, etc...) 2) Syncthing uses community relays/nodes without any incentive structure - it limits the scale of the network. Diode implements a relay incentive in proportion to the traffic handled (which is somewhat predicated on the QoS the relay is able to provide) 3) Syncthing is a closed system (an impact of #1), so it can't do things like link sharing, web viewers, etc... whereas Diode is able to provide all those things fully decentralized

There are certainly also specific UX/functionality differences on how the apps are implemented, but those are probably the macro considerations.