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

Event messages (calendar invitations in chats)

Open
#34 0 comments 0 reactions 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
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

Start with AGENTS.md for the privacy rules and translation requirements, then find where event messages currently fall through to the unsupported-content display. Look at the events() API (create and respond) in the whatsapp-rust revision ae3cefd. Done means event messages show title, time, location and response counts, users can respond to or create an event in a group, and new strings have pt_BR entries with no message content 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:

events() offers create and respond.

What ZapTide does today

Nothing. Event messages are shown as unsupported content.

Proposed scope

  1. Render event messages with title, time, location and the going, maybe and not going counts.
  2. Respond to an event, and create one in a group chat.

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.