Gabriel Cruz
Gabriel Cruz
I feel like the best way to implement this is creating and giving an "inviter" key to the parent. Then they could just get other non-inviter keys for their "children"....
@fbac there's already a PR in for that (https://github.com/application-research/estuary/pull/388), but you're more than welcome to review that or take another issue :)
Yup closed on #388
I was thinking maybe having a `base API communicator` which implements endpoints necessary to talk to other players (such as a shuttle or a main node), then we'll have files...
@whyrusleeping this might have something to do with our boost throttling issue? TL;DR: boost does not rate limit so we end up with several concurrent deals that are slow (since...
@TMoMoreau `#ecosystem-dev` is the best place! https://filecoinproject.slack.com/archives/C016APFREQK
@TMoMoreau I think we should do: - Setup - building process instructions here - Running your own node - instructions on running your own node here - Running as a...
@en0ma we should document both the version and the health endpoints
I mean we should have those endpoints on https://docs.estuary.tech
Still, the docs should exist for the team. Not sure where these would go though