We need a "daemon mode" where a site owner can run an instance serverside of Orbiter from a data persistence standpoint - as opposed to just delivering an HTML/JS/CSS bundle.
Daemon mode
In daemon mode, the instance would do two major things:
Act as a WebRTC Star server
Centrally connect and help peer members of the network
[ ] #10
Act as a beacon
In beacon mode, the Orbiter instance would have a number of API endpoints that are useful for the Defederation system.
The following features would be required:
9 An endpoint where one can request a bundle of the entire metadata base of the site. This endpoint will simply return an Iroh CID, which can then be fetched which contains the entire definition of a site, and a subsection with the entire definition of all followed sites (recursively). The daemon is to build and publish these metadata bundles every 10 minutes by default (faster should also be possible, up to a certain point).
An endpoint where one can get a list of all pins by CID, as well as their current seeding status, so that one can assign their efforts to underseeded CIDs.
This will later form a replacement for IPFS Cluster.
An endpoint that shows data in a Lis-compatible format to allow direct integration into a filesystem.
We need a "daemon mode" where a site owner can run an instance serverside of Orbiter from a data persistence standpoint - as opposed to just delivering an HTML/JS/CSS bundle.
Daemon mode
In daemon mode, the instance would do two major things:
Act as a WebRTC Star server
Centrally connect and help peer members of the network
Act as a beacon
In beacon mode, the Orbiter instance would have a number of API endpoints that are useful for the Defederation system.
The following features would be required:
9 An endpoint where one can request a bundle of the entire metadata base of the site. This endpoint will simply return an Iroh CID, which can then be fetched which contains the entire definition of a site, and a subsection with the entire definition of all followed sites (recursively). The daemon is to build and publish these metadata bundles every 10 minutes by default (faster should also be possible, up to a certain point).