swicg / swicg/activitypub-e2ee
KeyPackages that expire with no replacement
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 78
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
If the user has not used a client for a long time -- longer than the keypackage expiry, say 2-3 months? -- it's possible that a remote user will not be able to invite them to join a group.
I think that of the possibilities, this seems like the least worst outcome. Making keys that have very long expiry seems like a problem. If you're not using the client more than once every few months, it's not really an active key.
We should note this.
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
Start by locating the project's documentation for KeyPackages and expiry behavior; no file or test is named in the issue. Document the case where a long-unused client's KeyPackages expire without replacement, and ensure the wording explains that a remote user may then be unable to invite them to a group.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100