I’ve been considering how to connect a pod to DAT, so the data can be replicated/mirrored , initially from only my computer to my pod, but I’m not sure if I’m connecting concepts properly. has anyone else looked into this? https://docs.datproject.org/dat-node
Can Solid and DAT work together? might be a great way to have your central datastore stay up to date even if you access it through different PODs or your personal pc.
Can a solid server and a dat server live together on the same node.js?
Dat is a new p2p hypermedia protocol. It provides public-key-addressed file archives which can be synced securely and browsed on-demand.
Fast
Archives sync from multiple sources at once.
|Secure|All updates are signed and integrity-checked.|
|Resilient|Archives can change hosts without changing their URLs.|
|Versioned|Changes are written to an append-only version log.|
Is it possible to mount DAT as a Fuse Filse system? If so then you could do that and run NSS and you would have your DAT files on solid. Then you cpuld copy stuff each way
I’m not sure but doubt it. DAT is a protocol, currently implemented in Beaker Browser (see @Metahari’s post below) more a browser based OS/p2p ecosystem if I understand correctly, and requires the Beaker Browser.
There’s A FUSE for IPFS which I have not tried, and I’m building one myself for SAFE Network (SAFE Drive
is currently in public testing) .
Incremental Versioning - Datasets can
be efficiently synced, even in real time, to other peers.
Random Access - Huge file hierarchies can be efficiently traversed remotely.
DAT is a protocol, like HTTP is a protocol, meaning a dat link can start with dat://
It does offer a HTTP implementation to support the dat:// link discovery process, but does not require it.
Dat Links
Dat links are Ed25519 (Bernstein et al. 2012) public
keys which have a length of 32 bytes (64 characters
when Hex encoded). You can represent your Dat link
in the following ways and Dat clients will be able to
understand them:
The standalone public key:
8e1c7189b1b2dbb5c4ec2693787884771201da9…
Using the dat:// protocol:
dat://8e1c7189b1b2dbb5c4ec2693787884771…
My interest is of course, the Incremental Versioning, and syncing of data. It’s great to keep all your turtle links in your pods, but over time the changes to the data tell a fuller story, as well.
Thanks for the correction and info. I’ve updated my post. SAFE has versioning and gaurantees access to data (and old versions) forever, so it may also be of interest to you.
Coming here from searching a Solid FUSE adapter itself, but staying for sharing some news about FUSE on Dat.
The CoboxCloud Cooperative has a pre-release of a file sharing application similar to Syncthing that runs entirely on the hyper:// family of protocols. Fuse-binding the stores into the file system is their underpinning assumption and happens automatically when starting the daemon.