ssb-client v2
Scuttlebot client.
Create an rpc connection to an sbot running locally.
example
var ssbClient = var ssbKeys = // simplest usage, connect to localhost sbot// this will cb with an error if an sbot server is not running // configuration:var keys = ssbKeys
- Tutorials using this library to create basic clients: ssb-client-basic
- A simple command line wrapper around this library: ssb-client-cli
api
require('ssb-client') => createEasyClient
createEasyClient(cb(err, sbot))
Create a connection to the local ssb-server
instance, using the default keys.
Configuration and keys will be loaded from directory specified by ssb_appname
.
(by default ~/.ssb
)
The manifest will be the manifest provided by that server.
Calling this without arguments is handy for scripts, but applications should use the clearer apis.
there is a legacy api, that makes things as "easy" as possible, by loading configuration and defaults. This is useful for scripts but applications should probably use
createCustomClient({keys, config, manifest, remote}, cb(err, sbot))
Connect to a specific server with fixed settings. All fields are mandatory.
createLegacyClient(keys, opts, cb(err, sbot))
Connect to a client with some custom settings.
opts supports the keys:
remote
multiserver address to connect tohost, port, key
(legacy) if remote is not set, assemble address from host, port, key.manifest
use a custom manifest.
If you need custom options, it's recommended to use the createCustomClient
API
instead, but this is still provided for legacy support.
keys
See ssb-keys. The keys look like this:
id: String public: String private: String curve: 'ed25519'
caps
caps.shs
is a random string passed to secret-handshake. It determines which sbot you are able to connect to. It defaults to a magic string in this repo and also in scuttlebot
var appKey = Buffer
License
MIT, Copyright 2015 Paul Frazee and Dominic Tarr