core/knotserver/db/ at caf7b4ca00102045e90feeeb96fd3031cdbbccef · alice.pds.demo.boltless.dev/core · Tangled

alice.pds.demo.boltless.dev / core

0

This repository has no description

0

core / knotserver / db

3 files

at caf7b4ca00102045e90feeeb96fd3031cdbbccef

Anirudh Oppiliappan knotserver: /init and /user endpoints 2y ago

knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.

2 years ago

knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.

2 years ago

knotserver: /init and /user endpoints When the knot is initialized, the h.init channel is closed signalling the Jetstream watcher to begin, with the owner DID in filter. There's no null filter so starting it without any DIDs will give us events for all DIDs. /init also checks if h.knotInitialized is true, and will 409 Conflict if /init is called again. PUT /user is similar, but will only trigger a call to UpdateDids.

2 years ago