You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report — confirmed regression range. The 709-line script you mentioned is the file state right before #953 (commit 072a917, "gzip cache bodies + status-aware TTL"), which enabled caching of medium-size responses (~26–100 KB) that previously bypassed the spreadsheet cache. Telegram Web's HTML and bundles fall in that range, so they're now being served stale from cache.
Quick test to confirm: in the new script, set CACHE_SPREADSHEET_ID back to "CHANGE_ME_TO_CACHE_SPREADSHEET_ID" to disable the cache entirely. If Telegram loads again, the cache is the culprit and we'll ship a fix to tighten what's cached. Please report back.
Activity
dazzling-no-more commentedon May 13, 2026
Thanks for the report — confirmed regression range. The 709-line script you mentioned is the file state right before #953 (commit
072a917, "gzip cache bodies + status-aware TTL"), which enabled caching of medium-size responses (~26–100 KB) that previously bypassed the spreadsheet cache. Telegram Web's HTML and bundles fall in that range, so they're now being served stale from cache.Quick test to confirm: in the new script, set
CACHE_SPREADSHEET_IDback to"CHANGE_ME_TO_CACHE_SPREADSHEET_ID"to disable the cache entirely. If Telegram loads again, the cache is the culprit and we'll ship a fix to tighten what's cached. Please report back.MR-Y-Programer commentedon May 14, 2026
توی اسکریپت جدید من اصلا تو قسمت کش تغییری ایجاد نکردم
همون دیفالت بود فقط Auth-key رو عوض کردم
دوباره تست میکنم ولی