element-hq / element-hq/element-meta

Allow more control over recipients of message encryption keys

Open
#393 2 comments 1 reaction 0 assignees View on GitHub
A-E2EE T-Enhancement
Dominant language
No language data
Stars
112
Forks
25
Avg merge
6h 6m
Merged PRs (30d)
4

Description

In some situations one does not want all room members to be able to read one's messages:
- In a reporting room, several people could each privately report to the room admin.
- For a party, people might want to report what they bought for whom - to all but the gift recipient.
- When playing diplomacy, this avoids having to create n² rooms for all the subsets of the players.
A nice interface would be nice, both on the sending and on the receiving side: one wouldn't want lots of "The server has sent no keys for this message - request them from your other devices" garbage.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named. Start by clarifying the sender and recipient-selection semantics for encrypted messages, including how excluded recipients should avoid missing-key warnings. Done should include agreed sending and receiving interfaces that support the reporting, gift, and diplomacy cases.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.