Tangled (and other ATProto) claims can never be bidirectional
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication
Research direction
No source files, tests, or entry points are named. Start by tracing how Keytrace verifies claims against the PDS records shown in the issue, then establish whether same-account claims should be treated as verified by default and define tests for the chosen behavior.
Written by the indexing model from the issue text.
Description
Playing with Keytrace I realised that for any service which stores its data on my PDS, the claim can be verified by querying the PDS directly – and by the same token, the claim will never truly be bidirectional.
For example, the two sides of my Tangled claim are saved on my PDS at:
at://did:plc:6cbrxnrfmwpb7rhjkihqezzh/dev.keytrace.claim/3mtpfsbdp5h2jat://did:plc:6cbrxnrfmwpb7rhjkihqezzh/sh.tangled.string/3mtpfmtkpwj22.
I'm not sure how problematic this is, bus so far as I can see it is unavoidable.
What it does seem to imply though is that the second part of the claim is entirely unnecessary. For any claim relating to the same ATProto account as my Keytrace profile, it may as well be considered "verified by default" without needing to publish the other half of the claim.
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from orta/keytrace
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
mobile-next/mobile-mcp#526 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 73/100
redhat-developer/rhdh-plugin-export-overlays#4470 · 1 comment ·
Maintainers usually reply within 1 day