MaddyUnderStars / MaddyUnderStars/shoot
e2ee
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 61
- Forks
- 5
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
Someone [recommended](https://social.ujeenator.net/@ujeenator/statuses/01JY98FRBH4VXK78HGAY9VYT52) that Shoot considered PGP for encrypted messages. There is actually already some work put into this (see [one](https://github.com/swicg/activitypub-e2ee), [two](https://github.com/w3c/activitypub/issues/449), [three](https://swicg.github.io/activitypub-e2ee/mls)) and based on some descriptions of how it'd work, it seems like a pretty sound method.
TODO list:
- Does anyone else implement this?
- Pros/cons of using pgp specifically
- Pros/cons of only encrypting the message *content* vs the entire protocol? (is that even possible? likely not by me)
- How does this effect moderation tooling? Automod breaks entirely, is that something we care about?
- How do [embeds](https://github.com/MaddyUnderStars/shoot/tree/feat/embeds) work? I think Matrix allows the clients to request them independently?
- likely more
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 reviewing the linked ActivityPub E2EE, W3C, and MLS material, then inspect the linked embeds branch. Compare implementation options, moderation effects, and embed handling; done means the project has a decided scope and documented direction for encrypted messaging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100