parakeet.at
mia.pds.parakeet.at
Currently the ‘control’ for parakeet instances is the env var soup, a few DB bits, and manual pokes into redis.
Not sure on the architecture of control API just yet (I don’t want more binaries) but I do want them exposed over xrpc. Given the list of stuff below, I think it might just go in parakeet and require service auth from the PDS. That admin list can be hard-coded in env.
I think the panel will be a simple HTMX(?) and Tailwind affair. There should be tools for:
- manually backfilling / resyncing
- appview takedowns(?)
- controlling the verifiers list
- controlling the appview DID allowlist (and enabling/disabling it)
- controlling consumer allowlist, once this is something we support.