swicg / swicg/activitypub-e2ee

Data retention of MLS messages on the server

Open
#63 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
78
Forks
2
PR merge metrics
No merged PRs in 30d

Description

  • How do MLS messages get retained on the server?
  • When are they deleted, if ever?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points and only asks how MLS messages are retained and deleted on the server. Trace the server-side message lifecycle, then document the retention and deletion behavior, including any conditions or limitations found.

Written by the indexing model from the issue text.

Assessment

Domain
backend, security
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.