My original single computer design (see https://darkpi.com) was too simple and too easy to break.
The Trio uses a network of Raspberry Pi hardware (two rpi3 and one rpiZw unit(s), currently) to run tasks (compiling, file caching, encrypting, static site hosting, encrypted CDN, etc) distributed and cross verified between units before allowing data to be written to shared storage for the node.
Data written to storage is cached locally, and backed up in encrypted chunks wherever else in the network there is spare storage, using rsync and ssh/sftp/mosh and a globally distributed chunk hash index.
The minimum viable product is a distributed file cache, accessible for each user to write to via ssh/sftp/mosh [email protected], and accessible username.rheos.one if you choose to turn on public web access for your directory (via .
Each trio node has a one "public" dedicated hardware, running Debian Linux and a static page hosting load balancer, managed by the other two "backend" hardware units, which provide, clean, and manage data. If the case is broken open or tampered with (without ubikey authentication and a sysadmin override), the system closes external connections, cleanly syncs all data, and wipes the "public" hardware system, then does a full reboot and re-initialization, re-initializing the "public" hardware for re-use after verifying the case sensors aren't being tampered with.
The long range wifi adapter allows for reasonable rates of transfer between nodes, or to a public internet wireless network, from around 1km. With two or three of these per county, anyone can connect to a simple access network, and anyone who wants to build their own can do that too.
All of these designs are being released as open source, under a non-commercial license, but are currently considered proprietary until the project officially launches.
Please do not use this tech for doing harm.
Please do support your local library.
This is essentially the hardware we want to put into orbit.