Define a Centralized Model for Encrypted File and Folder Actions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Issue
End-to-end encrypted (E2E) files and folders require different handling rules compared to regular files and folders. Certain actions that are available for normal content (e.g., client integrations, Office integrations) may not be compatible with encrypted files or folders.
Currently, applications do not have a centralized way to determine which actions are allowed or restricted for encrypted files and folders. This creates inconsistencies across current and future applications, as each app may implement its own logic and validation rules.
This may cause issues in web or client applications, such as displaying actions that are not valid or supported for E2E encrypted content.
How can we centralize this?
@tobiasKaminsky @susnux CC
Screenshots
| Folder actions | File actions |
|---|---|
Contributor guide
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 file, test, or entry point is named. Start by locating how web and client applications currently decide which actions are available for E2E-encrypted files and folders, then compare those rules with regular content and integration restrictions. Done means a defined centralized model can consistently identify permitted and restricted actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100