929a3725d3
* docs(navigation): canonicalize paths and align zh nav * chore(docs): remove stray .DS_Store * docs(scripts): add non-mint docs link audit * docs(nav): fix zh source paths and preserve legacy redirects (#11428) (thanks @sebslight) * chore(docs): satisfy lint for docs link audit script (#11428) (thanks @sebslight)
41 lines
1009 B
Markdown
41 lines
1009 B
Markdown
---
|
|
summary: "Telegram allowlist hardening: prefix + whitespace normalization"
|
|
read_when:
|
|
- Reviewing historical Telegram allowlist changes
|
|
title: "Telegram Allowlist Hardening"
|
|
---
|
|
|
|
# Telegram Allowlist Hardening
|
|
|
|
**Date**: 2026-01-05
|
|
**Status**: Complete
|
|
**PR**: #216
|
|
|
|
## Summary
|
|
|
|
Telegram allowlists now accept `telegram:` and `tg:` prefixes case-insensitively, and tolerate
|
|
accidental whitespace. This aligns inbound allowlist checks with outbound send normalization.
|
|
|
|
## What changed
|
|
|
|
- Prefixes `telegram:` and `tg:` are treated the same (case-insensitive).
|
|
- Allowlist entries are trimmed; empty entries are ignored.
|
|
|
|
## Examples
|
|
|
|
All of these are accepted for the same ID:
|
|
|
|
- `telegram:123456`
|
|
- `TG:123456`
|
|
- `tg:123456`
|
|
|
|
## Why it matters
|
|
|
|
Copy/paste from logs or chat IDs often includes prefixes and whitespace. Normalizing avoids
|
|
false negatives when deciding whether to respond in DMs or groups.
|
|
|
|
## Related docs
|
|
|
|
- [Group Chats](/channels/groups)
|
|
- [Telegram Provider](/channels/telegram)
|