Convert Figma logo to code with AI

dat-ecosystem logodat

:floppy_disk: peer-to-peer sharing & live syncronization of files via command line

8,245
449
8,245
104

Top Related Projects

Hypercore is a secure, distributed append-only log.

22,775

Peer-to-peer hypermedia protocol

66,967

Open Source Continuous File Synchronization

The gossip and replication server for Secure Scuttlebutt - a distributed social network

8,362

Peer-to-Peer Databases for the Decentralized Web

Quick Overview

Dat is a peer-to-peer protocol for sharing data between computers. It provides a distributed data synchronization mechanism that allows users to publish, share, and update data in a decentralized manner. Dat is designed to be fast, secure, and resilient, making it suitable for various applications, including scientific data sharing and offline-first web apps.

Pros

  • Decentralized and peer-to-peer, reducing reliance on central servers
  • Versioning and history tracking for data
  • Efficient partial replication and delta updates
  • Cryptographically secure, ensuring data integrity and authenticity

Cons

  • Limited adoption compared to more established file-sharing protocols
  • Requires specialized software or libraries for implementation
  • May face challenges in NAT traversal and firewall issues
  • Documentation and community support may be less extensive than more mainstream solutions

Code Examples

  1. Creating a Dat archive:
const Dat = require('dat-node')

Dat('./my-data-folder', (err, dat) => {
  if (err) throw err
  dat.importFiles()
  console.log('My Dat link is: dat://' + dat.key.toString('hex'))
})
  1. Joining a Dat archive:
const Dat = require('dat-node')

Dat('./download', { key: '<dat-key>' }, (err, dat) => {
  if (err) throw err
  dat.joinNetwork()
  dat.archive.readFile('/hello.txt', (err, content) => {
    if (err) throw err
    console.log(content.toString())
  })
})
  1. Watching for changes in a Dat archive:
const Dat = require('dat-node')

Dat('./my-data-folder', (err, dat) => {
  if (err) throw err
  dat.importFiles({ watch: true })
  dat.archive.on('content-added', (entry) => {
    console.log('New file added:', entry.name)
  })
})

Getting Started

To get started with Dat, follow these steps:

  1. Install Dat globally:

    npm install -g dat
    
  2. Create a new Dat archive:

    dat create ./my-data-folder
    
  3. Share the Dat archive:

    dat share ./my-data-folder
    
  4. On another computer, clone the Dat archive:

    dat clone <dat-link> ./download-folder
    

For more detailed information and advanced usage, refer to the official Dat documentation.

Competitor Comparisons

Hypercore is a secure, distributed append-only log.

Pros of Hypercore

  • More active development with recent updates and releases
  • Focused on a modular, lower-level approach for building decentralized applications
  • Better documentation and examples for developers

Cons of Hypercore

  • Steeper learning curve due to its lower-level nature
  • Less out-of-the-box functionality compared to Dat's more complete solution
  • Requires additional modules for full feature parity with Dat

Code Comparison

Dat example:

const Dat = require('dat-node')

Dat('./my-dataset', (err, dat) => {
  if (err) throw err
  dat.importFiles()
  dat.joinNetwork()
})

Hypercore example:

const Hypercore = require('hypercore')

const feed = new Hypercore('./my-dataset')
feed.append('Hello, World!', (err) => {
  if (err) throw err
  console.log('Data appended!')
})

Both projects aim to provide decentralized data sharing capabilities, but Hypercore offers a more modular and lower-level approach. Dat provides a more complete solution out-of-the-box, while Hypercore requires additional modules for similar functionality. Hypercore's active development and modular design make it more flexible for custom implementations, but it may require more effort to set up compared to Dat's simpler API.

22,775

Peer-to-peer hypermedia protocol

Pros of IPFS

  • Larger and more active community with broader adoption
  • Built-in content addressing and cryptographic verification
  • Supports a wider range of use cases beyond file sharing

Cons of IPFS

  • Higher complexity and steeper learning curve
  • Potentially slower performance for small-scale file sharing
  • More resource-intensive, especially for full nodes

Code Comparison

IPFS (JavaScript):

import { create } from 'ipfs-core'

const ipfs = await create()
const { cid } = await ipfs.add('Hello, IPFS!')
console.log(cid.toString())

Dat (JavaScript):

import Hypercore from 'hypercore'

const feed = new Hypercore('./my-data')
await feed.append('Hello, Dat!')
console.log(feed.key.toString('hex'))

Key Differences

  • IPFS uses content-addressed storage, while Dat uses append-only logs
  • IPFS has a more complex network structure with DHT, while Dat uses a simpler discovery mechanism
  • IPFS focuses on global content distribution, while Dat emphasizes local-first and offline-first scenarios

Both projects aim to decentralize data storage and sharing, but they take different approaches. IPFS offers a more comprehensive solution for content-addressed data on a global scale, while Dat provides a simpler, more focused approach for peer-to-peer file sharing and syncing.

66,967

Open Source Continuous File Synchronization

Pros of Syncthing

  • More active development and larger community support
  • Cross-platform compatibility (Windows, macOS, Linux, Android)
  • Built-in encryption and security features

Cons of Syncthing

  • More complex setup and configuration process
  • Higher resource usage, especially for large numbers of files
  • Less suitable for public data sharing and distribution

Code Comparison

Dat:

const Dat = require('dat-node')

Dat('./my-dataset', (err, dat) => {
  if (err) throw err
  dat.importFiles()
  dat.joinNetwork()
})

Syncthing:

cfg := config.New(config.WithDefaults())
m := model.NewModel(cfg, protocol.LocalDeviceID, "syncthing", "1.0.0")
m.StartDevice(protocol.LocalDeviceID)
m.StartFolder("default")

Summary

Dat focuses on versioned, distributed data sharing with a simpler setup, while Syncthing offers robust file synchronization across devices with stronger security features. Dat is better suited for public data distribution, whereas Syncthing excels in private, multi-device file synchronization. The choice between them depends on specific use cases and requirements.

The gossip and replication server for Secure Scuttlebutt - a distributed social network

Pros of ssb-server

  • Designed for decentralized social networking, with built-in support for user identities and relationships
  • More mature project with a larger community and ecosystem of applications
  • Supports offline-first operations and local-first data storage

Cons of ssb-server

  • Higher complexity due to its focus on social networking features
  • Slower replication speed compared to Dat's more streamlined approach
  • Less suitable for large file sharing and distribution

Code comparison

ssb-server:

const Server = require('ssb-server')
const config = require('ssb-config')

const server = Server(config)

server.publish({ type: 'post', text: 'Hello, SSB!' }, (err, msg) => {
  console.log(msg)
})

dat:

const Dat = require('dat-node')

Dat('./my-dataset', (err, dat) => {
  dat.importFiles()
  dat.joinNetwork()
  console.log('My Dat link is: dat://' + dat.key.toString('hex'))
})

Summary

ssb-server is tailored for decentralized social networking with robust identity and relationship features, while Dat focuses on efficient peer-to-peer file sharing and versioning. ssb-server offers a more comprehensive solution for social applications but may be overkill for simple file sharing tasks. Dat provides a simpler API and faster replication for file-centric use cases but lacks built-in social networking capabilities.

8,362

Peer-to-Peer Databases for the Decentralized Web

Pros of OrbitDB

  • Supports multiple database types (key-value, log, feed, documents)
  • Built on IPFS, providing decentralized storage and content-addressing
  • Offers real-time replication and syncing between peers

Cons of OrbitDB

  • Less mature ecosystem compared to Dat
  • Potentially higher complexity due to IPFS integration
  • May have performance limitations for large datasets

Code Comparison

OrbitDB:

const orbitdb = await OrbitDB.createInstance(ipfs)
const db = await orbitdb.keyvalue('my-database')
await db.put('key', 'value')
const value = await db.get('key')

Dat:

const archive = await DatArchive.create()
await archive.writeFile('/file.txt', 'Hello World')
const content = await archive.readFile('/file.txt')

Key Differences

  • OrbitDB focuses on distributed databases, while Dat emphasizes file sharing
  • OrbitDB uses IPFS as its underlying network, Dat has its own custom protocol
  • Dat provides versioning out-of-the-box, OrbitDB requires additional setup
  • OrbitDB offers more flexibility in data structures, Dat is file-centric

Both projects aim to create decentralized data sharing solutions, but they approach the problem from different angles. OrbitDB is more suitable for applications requiring diverse database functionalities, while Dat excels in peer-to-peer file sharing and versioning.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

More info on active projects and modules at dat-ecosystem.org


Dat

npm install -g dat

Use dat command line to share files with version control, back up data to servers, browse remote files on demand, and automate long-term data preservation.

dat is the first application based upon the Hypercore Protocol, and drove the architectural design through iterative development between 2014 and 2017. There exists a large community around it.

Have questions? Join our chat via IRC or Gitter:

#dat IRC channel on freenode datproject/discussions

Thanks to our financial supporters!

OpenCollective

Table of Contents

Installation

Dat can be used as a command line tool or a javascript library:

  • Install the $ dat CLI to use in the command line.
  • require('dat') - dat-node, a library for downloading and sharing dat archives in javascript apps.

Installing the $ dat command line tool

The recommended way to install dat is through a single file binary distribution version of dat with the one line install command below. The binary includes a copy of node and dat packaged inside a single file, so you just have to download one file in order to start sharing data, with no other dependencies needed on your system:

wget -qO- https://raw.githubusercontent.com/datproject/dat/master/download.sh | bash

Next version

Try the next version of dat! This version (14.0.0) is not compatible with older versions (13.x) and below, and works on node v12.

npm install -g dat@next

Maintainers wanted!

NPM Prerequisites

  • Node: You'll need to install Node JS before installing Dat. Dat needs node version 4 or above and npm installed. You can run node -v to check your version.
  • npm: npm is installed with node. You can run npm -v to make sure it is installed.

Once you have npm ready, install dat from npm with the --global, -g option, npm install -g dat.

Getting started

What is Dat?

Share, backup, and publish your filesystem. You can turn any folder on your computer into a dat. Dat scans your folder, allowing you to:

  • Track your files with automatic version history.
  • Share files with others over a secure peer to peer network.
  • Automate live backups to external HDs or remote servers.
  • Publish and share files with built in HTTP server.

Dat allows you to focus on the fun work without worrying about moving files around. Secure, distributed, fast.

Desktop Applications

Rather not use the command line? Check out these options:

  • Beaker Browser - An experimental p2p browser with built-in support for the Hypercore Protocol.
  • Dat Desktop - A desktop app to manage multiple dats on your desktop machine.

JS Library

Add Dat to your package.json, npm install dat --save. Dat exports the dat-node API via require('dat'). Use it in your javascript applications! Dat Desktop and Dat command line both use dat-node to share and download dats.

Full API documentation is available in the dat-node repository on Github.

We have Dat installed, let's use it!

Dat's unique design works wherever you store your data. You can create a new dat from any folder on your computer.

A dat is some files from your computer and a .dat folder. Each dat has a unique dat:// link. With your dat link, other users can download your files and live sync any updates.

Sharing Data

You can start sharing your files with a single command. Unlike git, you do not have to initialize a repository first, dat share or simply dat will do that for you:

dat <dir>

Use dat to create a dat and sync your files from your computer to other users. Dat scans your files inside <dir>, creating metadata in <dir>/.dat. Dat stores the public link, version history, and file information inside the dat folder.

dat sync and dat share are aliases for the same command. share-gif

Downloading Data

dat dat://<link> <download-dir>

Use dat to download files from a remote computer sharing files with Dat. This will download the files from dat://<link> to your <download-dir>. The download exits after it completes but you can continue to update the files later after the clone is done. Use dat pull to update new files or dat sync to live sync changes.

dat clone is an alias for the same command.

clone-gif

Misc Commands

A few other highlights. Run dat help to see the full usage guide.

  • dat create or dat init - Create an empty dat and dat.json file.
  • dat log ~/data/dat-folder/ or dat log dat://<key> - view the history and metadata information for a dat.

Quick Demos

To get started using Dat, you can try downloading a dat and then sharing a dat of your own.

Download Demo

We made a demo folder just for this exercise. Inside the demo folder is a dat.json file and a gif. We shared these files via Dat and now you can download them with our dat key!

Similar to git, you can download somebody's dat by running dat clone <link>. You can also specify the directory:

❯ dat clone dat://778f8d955175c92e4ced5e4f5563f69bfec0c86cc6f670352c457943666fe639 ~/Downloads/dat-demo
dat v13.5.0
Created new dat in /Users/joe/Downloads/dat-demo/.dat
Cloning: 2 files (1.4 MB)

2 connections | Download 614 KB/s Upload 0 B/s

dat sync complete.
Version 4

This will download our demo files to the ~/Downloads/dat-demo folder. These files are being shared by a server over Dat (to ensure high availability) but you may connect to any number of users also hosting the content.

You can also also view the files online: datbase.org/778f8d955175c92e4ced5e4f5563f69bfec0c86cc6f670352c457943666fe639. datbase.org can download files over Dat and display them on HTTP as long as someone is hosting it. The website temporarily caches data for any visited links (do not view your dat on datbase.org if you do not want us to cache your data).

Sharing Demo

Dat can share files from your computer to anywhere. If you have a friend going through this demo with you, try sharing to them! If not we'll see what we can do.

Find a folder on your computer to share. Inside the folder can be anything, Dat can handle all sorts of files (Dat works with really big folders too!).

First, you can create a new dat inside that folder. Using the dat create command also walks us through making a dat.json file:

❯ dat create
Welcome to dat program!
You can turn any folder on your computer into a Dat.
A dat is a folder with some magic.

This will create a new (empty) dat. Dat will print a link, share this link to give others access to view your files.

Once we have our dat, run dat <dir> to scan your files and sync them to the network. Share the link with your friend to instantly start downloading files.

Bonus HTTP Demo

Dat makes it really easy to share live files on a HTTP server. This is a cool demo because we can also see how version history works! Serve dat files on HTTP with the --http option. For example, dat --http, serves your files to a HTTP website with live reloading and version history! This even works for dats you're downloading (add the --sparse option to only download files you select via HTTP). The default HTTP port is 8080.

Hint: Use localhost:8080/?version=10 to view a specific version.

Get started using Dat today with the share and clone commands or read below for more details.

Usage

The first time you run a command, a .dat folder is created to store the dat metadata. Once a dat is created, you can run all the commands inside that folder, similar to git.

Dat keeps secret keys in the ~/.dat/secret_keys folder. These are required to write to any dats you create.

Creating a dat & dat.json

dat create [<dir>]

The create command prompts you to make a dat.json file and creates a new dat. Import the files with sync or share.

Optionally bypass Title and Description prompt:

dat create --title "MY BITS" --description "are ready to synchronize! 😎"

Optionally bypass dat.json creation:

dat create --yes
dat create -y

Sharing

The quickest way to get started sharing files is to share:

❯ dat 
dat://3e830227b4b2be197679ff1b573cc85e689f202c0884eb8bdb0e1fcecbd93119
Sharing dat: 24 files (383 MB)

0 connections | Download 0 B/s Upload 0 B/s

Importing 528 files to Archive (165 MB/s)
[=-----------------------------------------] 3%
ADD: data/expn_cd.csv (403 MB / 920 MB)
dat [<dir>] [--no-import] [--no-watch]

Start sharing your dat archive over the network. It will import new or updated files since you last ran create or sync. Dat watches files for changes and imports updated files.

  • Use --no-import to not import any new or updated files.
  • Use --no-watch to not watch directory for changes. --import must be true for --watch to work.

Ignoring Files

By default, Dat will ignore any files in a .datignore file, similar to git. Each file should be separated by a newline. Dat also ignores all hidden folders and files. Supports pattern wildcards (/*.png) and directory-wildcards (/**/cache).

Selecting Files

By default, Dat will download all files. If you want to only download a subset, you can create a .datdownload file which downloads only the files and folders specified. Each should be separated by a newline.

Downloading

Start downloading by running the clone command. This creates a folder, downloads the content and metadata, and a .dat folder inside. Once you started the download, you can resume at any time.

dat <link> [<dir>] [--temp]

Clone a remote dat archive to a local folder. This will create a folder with the key name if no folder is specified.

Downloading via dat.json key

You can use a dat.json file to clone also. This is useful when combining Dat and git, for example. To clone a dat you can specify the path to a folder containing a dat.json:

git git@github.com:joehand/dat-clone-sparse-test.git
dat ./dat-clone-sparse-test

This will download the dat specified in the dat.json file.

Updating Downloaded Archives

Once a dat is clone, you can run either dat pull or dat sync in the folder to update the archive.

dat pull [<dir>]

Download latest files and keep connection open to continue updating as remote source is updated.

Shortcut commands

  • dat <link> <dir> will run dat clone for new dats or resume the existing dat in <dir>
  • dat <dir> is the same as running dat sync <dir>

Key Management & Moving dats

dat keys provides a few commands to help you move or backup your dats.

Writing to a dat requires the secret key, stored in the ~/.dat folder. You can export and import these keys between dats. First, clone your dat to the new location:

  • (original) dat share
  • (duplicate) dat clone <link>

Then transfer the secret key:

  • (original) dat keys export - copy the secret key printed out.
  • (duplicate) dat keys import - this will prompt you for the secret key, paste it in here.

Troubleshooting

We've provided some troubleshooting tips based on issues users have seen. Please open an issue or ask us in our chat room if you need help troubleshooting and it is not covered here.

If you have trouble sharing/downloading in a directory with a .dat folder, try deleting it and running the command again.

Check Your Dat Version

Knowing the version is really helpful if you run into any bugs, and will help us troubleshoot your issue.

Check your Dat version:

dat -v

You should see the Dat semantic version printed, e.g. 14.0.0.

Installation Issues

Node & npm

To use the Dat command line tool you will need to have node and npm installed. Make sure those are installed correctly before installing Dat. You can check the version of each:

node -v
npm -v

Global Install

The -g option installs Dat globally, allowing you to run it as a command. Make sure you installed with that option.

  • If you receive an EACCES error, read this guide on fixing npm permissions.
  • If you receive an EACCES error, you may also install Dat with sudo: sudo npm install -g dat.
  • Have other installation issues? Let us know, you can open an issue or ask us in our chat room.

Debugging Output

If you are having trouble with a specific command, run with the debug environment variable set to dat (and optionally also dat-node). This will help us debug any issues:

DEBUG=dat,dat-node dat dat://<link> dir

Networking Issues

Networking capabilities vary widely with each computer, network, and configuration. Whenever you run Dat there are several steps to share or download files with peers:

  1. Discovering Peers
  2. Connecting to Peers
  3. Sending & Receiving Data

With successful use, Dat will show Connected to 1 peer after connection. If you never see a peer connected, your network may be restricting discovery or connection.

JS API

You can use Dat in your javascript application:

var Dat = require('dat')

Dat('/data', function (err, dat) {
  // use dat
})

Read more about the JS usage provided via dat-node.

For Developers

Please see guidelines on contributing before submitting an issue or PR.

This command line library uses dat-node to create and manage the archives and networking. If you'd like to build your own Dat application that is compatible with this command line tool, we suggest using dat-node.

Installing from source

Clone this repository and in a terminal inside of the folder you cloned run this command:

npm link

This should add a dat command line command to your PATH. Now you can run the dat command to try it out.

The contribution guide also has more tips on our development workflow.

  • npm run test to run tests
  • npm run auth-server to run a local auth server for testing

License

BSD-3-Clause

NPM DownloadsLast 30 Days