Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature Request] Automatic cleanup option for local WhatsApp media

Open
#10 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

The payload names no files or modules. Start by finding where the app stores downloaded WhatsApp media in the installation folder and where the settings screen is built. The feature needs a retention-days setting, a background job that deletes only local files older than that age, and optional notification. Done means the setting persists, old local media is removed on schedule, and remote messages are untouched. Confirm the design with a maintainer before coding, since background execution and notifications are not yet specified.

Written by the indexing model from the issue text.

Description

enhancement

Currently, all WhatsApp media (audio, videos, photos) are stored in the zaptide installation folder indefinitely, accumulating disk space.

I suggest adding a user-enabled option in the app settings for automatic cleanup:

  • The user defines a retention period in days (e.g., 30, 60, 90 days)
  • Local media older than that period is removed automatically
  • Cleanup affects only local files — it does not delete messages or media on WhatsApp
  • Background execution, silent or with optional notification

This prevents unnecessary accumulation and gives users control over local storage.

Dominant language
Rust
Stars
29
Forks
1
Avg merge
2h 39m
Merged PRs (30d)
28

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from luminusOS/zaptide

All issues in luminusOS/zaptide

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.