Solid and DAT Together?


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?

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
* Resilient
* Versioned
* Decentralized

List of DAT community projects


I guess you could have an app that allows you to publish resources on Dat? but right now it would require either:

  1. a browser-compatible version of dat-node, or
  2. a service that publishes the resources for you (using dat-node in the background)


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) .



does DAT have any concept of a symlink?


DAT does not require Beaker Browser to use.
Beaker Browser is a cool experiment based on DAT

Dat is a nonprofit-backed data sharing protocol for applications of the future.

^ from the Dat Project

Dat is a dataset synchronization protocol that does
not assume a dataset is static or that the entire dataset
will be downloaded.

The protocol is agnostic to the underlying transport
e.g. you could implement Dat over carrier pigeon.

^ From the whitepaper PDF

Key properties of the Dat design:

  • Content Integrity
  • Decentralized Mirroring
  • Network Privacy
  • 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:
  • Using the dat:// protocol:
  • As part of an HTTP URL:

^ From the whitepaper PDF


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. :slight_smile: 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.


If you are interested in this conversation, perhaps you would be interested in joining the External Interop and Outreach Panel.


I’m no expert, but am curious about the possibilities.