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

Channels (newsletters): browse, follow and read

Open
#28 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
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
desktop

Research direction

Start with AGENTS.md for the privacy and translation rules, then find where @newsletter chats are classified as read-only. Check the newsletter() methods in the pinned whatsapp-rust revision ae3cefd. Done means followed channels can be listed, their history and live updates loaded, and follow, unfollow, mute and react work, with new strings translated to pt_BR. The issue is large and unclaimed, so confirm scope with a maintainer before starting.

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:

newsletter() offers list_subscribed, get_metadata, join, leave, get_messages, subscribe_live_updates, send_reaction and set_follower_mute.

What ZapTide does today

@newsletter chats are classified as read-only broadcast chats, and nothing more.

Proposed scope

  1. List followed channels and load their history and live updates.
  2. Follow and unfollow, mute, and react to posts.
  3. Open channel invite links.
  4. Channel creation and administration can wait.

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.