tangled.org / core
Monorepo for Tangled — https://tangled.org
fork atom

Spindle can be added / verified as a Knot, eventually fails on repo creation. #208

open
opened by moll.dev edited

For posterity:

While running through the hacking.md doc, I mistakenly tried to register my spindle instance, on port 6555, as a knot. The knot page allowed it to be verified, but when I went to create a repo it complained about xrpc incompatibility, because it's not a knot.

Akshay mentioned that it's probably because the xrpc can talk to the spindle and get xrpc/sh.tangled.owner as part of the verification flow, but there's no further verification that the service is actually a knot.

While going through hacking-on-tangled doc, I setup my local environment, ran the VM for a knot, verified that it was added and when I go to create a new repo I get "xrpc not supported on this knot" as an error in the repo/new page.

moll.dev (author)

Updated title / body to reflect a potential bug

oppi.li edited

thanks for the report! for my own reference, the issue is as follows:

  • all tangled services go through the same "verification" process:
    • a service is announced with its lexicon (sh.tangled.knot or sh.tangled.spindle)
    • the appview performs an ownership check using /xrpc/sh.tangled.owner and marks verified if ownership lines up
  • this means, any tangled service just needs to implement /xrpc/sh.tangled.owner to be registered and verified
  • this makes it possible to register a spindle in the /knots page and vice-versa.
sign up or login to add to the discussion
Labels

None yet.

area

None yet.

assignee

None yet.

Participants 2
AT URI
at://did:plc:vlblikmsgpx2i7fvxinrsvzu/sh.tangled.repo.issue/3lyt47ra3qq22