telegramdesktop / telegramdesktop/tdesktop
Merge new closely consecutive messages from one author with older message without triggering new sound notifications.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33k
- Forks
- 7.2k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 12
Description
The problem: A lot of group conversation members write many line-wise part-messages rather than full multi-line messages. This results in an annoying spam of sound (& vibration) notifications, leading in a rather painful Telegram experience.
The solution: Merge new line-wise part-messages if they are still in a certain time threshold (e.g. 5 seconds) with the old message. Do not trigger a new sound notification.
Additional Thoughs: Such an enhancement SHOULD be available on every Telegram Client (and MAY be eanbled through settings). There could be even a way to trigger a sound notification only in case of a new message subject: E.g. My mates trolling about ponies for 5 minutes SHOULD trigger only one sound notification IF I did not open Telegram during this message subject.
Or the Clients could be aware of the Users attention (mouse movements, selecting the client window) to trigger closely following sound notifications only in the user's presence.
Last but not least, devices on the same LAN should synchronize their notifications and sound triggering.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by narrowing the requested behavior to message merging and notification suppression, separating the optional settings, attention-awareness, and LAN synchronization ideas. Done requires an agreed scope and an explicit testable definition of when consecutive messages merge and when sound or vibration is suppressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100