nextcloud / nextcloud/spreed

Content-cleanup of the TALK Directory in the appropr. storage location

Open
#6,880 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: upload & shares & voice 📤🎙️
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
All the web stuff from Talk will - per user - saved in the "TALK" Directory.
This directory is growing ..

Describe the solution you'd like
i did not see any options to & how to control the cleaning of the Talk Directory.
Is there some kind of "hidden" functionality, where the Talk - directory content will be cleaned (or even archived) on a regular base ?

Describe alternatives you've considered
This would be a fine option .. if there would be a user control option for that and a administrator option
(where the Admin could control the cleanup behave on a global level)

Additional context
Add any other context or screenshots about the feature request here.

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 names no files, tests, or entry points. Start by locating where Talk stores per-user content and how retention or archiving is currently handled; clarify the desired user and administrator controls before implementation. Done would require an agreed cleanup or archive behavior and corresponding controls.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.