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

Send the recording indicator while recording a voice message

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start by finding where voice-message recording begins, ends and is cancelled in the GTK4 client, and check how the existing composing chat state is sent through the whatsapp-rust chatstate() API at revision ae3cefd. Call send_recording on start and send_paused on send or cancel, and read AGENTS.md for the privacy rules. Done means both states are sent at the right moments, new pt_BR strings are translated, and no message content appears in logs or tests.

Written by the indexing model from the issue text.

Description

enhancement

A WhatsApp feature that whatsapp-rust already supports but ZapTide does not use yet.

What whatsapp-rust provides

Checked against the pinned revision ae3cefd:

chatstate() offers send_composing, send_recording and send_paused.

What ZapTide does today

ZapTide sends composing while typing, but nothing while recording a voice message, so the other side never sees "recording audio".

Proposed scope

  1. Call send_recording when a recording starts and send_paused when it is sent or cancelled.

Notes

The privacy rules in AGENTS.md apply: no message content in logs or tests. New strings need a pt_BR translation.

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.