Skip to content

Fix: уведомления из заглушённых чатов всё равно пересылались - #1

Draft
erop39 wants to merge 3 commits into
mainfrom
cursor/fix-muted-notifications-ec4d
Draft

Fix: уведомления из заглушённых чатов всё равно пересылались#1
erop39 wants to merge 3 commits into
mainfrom
cursor/fix-muted-notifications-ec4d

Conversation

@erop39

@erop39 erop39 commented Jun 15, 2026

Copy link
Copy Markdown
Owner

Изменения

  • Исправлена загрузка mute из settings.chats + запрос CONFIG после логина
  • Обновление списка заглушённых чатов по NOTIF_CONFIG
  • Стартовое уведомление в Telegram при SKIP_MUTED=true:
    ✅ Max: подключён | чатов: 32 | 🔇 из них без звука: 7
Open in Web Open in Cursor 

cursoragent and others added 3 commits June 15, 2026 13:59
Mute state in Max is stored in settings.chats, but on connect we only
loaded the chats array from AUTH_SNAPSHOT. Chats muted via «без звука»
were therefore unknown until a live NOTIF_CONFIG arrived.

- Load mute state from both chats[] and settings.chats on snapshot
- Raise chatsCount from 10 to 40 and request full sync params
- Handle alternate NOTIF_CHAT / NOTIF_CONFIG payload shapes
- Add integration tests for skip-muted filtering

Co-authored-by: eGoR <erop39@users.noreply.github.com>
AUTH_SNAPSHOT often does not include settings.chats with dontDisturbUntil.
NOTIF_CONFIG (134) only sends a config hash, not mute data.

- Request settings with opcode 22 using snapshot hash after connect
- Refresh mute state when NOTIF_CONFIG arrives
- Warn in logs when mute list is still empty after CONFIG fetch

Co-authored-by: eGoR <erop39@users.noreply.github.com>
When SKIP_MUTED=true, first-connect message includes:
«🔇 из них без звука: N»

Co-authored-by: eGoR <erop39@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants