Tangled (and other ATProto) claims can never be bidirectional
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
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.
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.
Assessment
- Tech stack
- typescript
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100