`sh.tangled.knot.version` -> `sh.tangled.knot.describeKnot` #327

Closed

boltless.me 11mo ago

Closed opened by and assigned to

boltless.me 11mo ago

descibeKnot can be used for more flexible use-cases.

For example, knot can show its git endpoints here.

{
  "version": "1.11.0-alpha",
  "gitEndpoints": [
    "user@knot.example.com",
    "ssh://user@knot.example.com:1234",
    "https://knot.example.com"
  ]
}

anirudh.fi 11mo ago

Perhaps getInfo or something similar? I still think a basic version endpoint is of value, however.

boltless.me 11mo ago

I'm following the nsid com.atproto.server.describeServer here which is used to fetch the capability of PDS. sh.tangled.knot.version (and many other tangled lexicons) is not following nsid guidelines.

anirudh.fi 11mo ago

Okay, that's good precedent in that case. And yes, we aren't following NSID guidelines in a good chunk of our lexicon—we should fix this before getting out of alpha.

This sounds good to me then.

boltless.me 1w ago

we now have org.tangled.knot.describeKnot