nextcloud / nextcloud/activity

Activities with E2EE (encrypted) files to display or to hide?

Open
#1,478 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
145
Forks
72
Avg merge
6d 9h
Merged PRs (30d)
42

Description

I have found that the activity log with encrypted files is almost useless, as it is not clear what is happening with files, when they are renamed, erased whatever.

image

Is that possible to make show the activities in a more friendly style:

  • place all events related to encrypted files in a special section of activities, which appears when the E2EE is turned on, and do not show them at all in the list of all events?
  • or do not display any event at all, as it is not possible to use E2EE in a webUI, at least for the moment?

Explain, what these suffixes .e2e-to-delete, .e2e-to-save mean?

Let me add, that the NC desktop client doesn't allow to display the activities with encrypted files!

image

Contributor guide

Open the contributing guide

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 does not name files, tests, or entry points. First clarify whether encrypted-file activities should be hidden, grouped, or explained, including the .e2e-to-delete and .e2e-to-save suffixes. Done should mean an agreed behavior for the activity list, with coverage for encrypted-file events and confirmation that the displayed wording is understandable.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, 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.