negodiy/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
929a3725d3bebd468adc42ba9d432ee7d7700bd1
openclaw/docs/experiments/plans/group-policy-hardening.md
Seb Slight 929a3725d3 docs: canonicalize docs paths and align zh navigation (#11428) 
* 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)
2026-02-07 15:40:35 -05:00

1009 B
Raw Blame History

summary, read_when, title
summary read_when title
Telegram allowlist hardening: prefix + whitespace normalization
Reviewing historical Telegram allowlist changes
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