Overview

This week’s channel activity was centered on tg2web: its purpose, infrastructure efficiency, and message-stream reliability. The posts show a mix of product thinking and hands-on testing, especially around reconnect/replay behavior and browser differences. There were also a few short casual/test posts.

Key Themes

• tg2web product direction
  • A longer post explained tg2web as an SEO-friendly bridge between Telegram channels and the wider web.
  • Stated goals included easier publishing for creators, long-term content retention, and access in places where Telegram may be blocked.
  • The author said the current infrastructure cost is effectively zero due to free cloud credits.

• Infrastructure optimization
  • Monitoring screenshots were shared after service bus usage was optimized.
  • The accompanying note said container apps now have lower overhead.

• Reconnect and replay testing
  • Several March 1 posts tested whether messages replay correctly after disconnect/reconnect.
  • The sequence included tests for replay, reconnect behavior, and confirmation that it “works nice”.

• Browser-specific behavior
  • One post noted that Safari behaves differently from Chrome.
  • A later screenshot showed a request with `Last-Event-ID`, with the note that reconnecting and retransmitting were working as expected.

Notable Posts

• 2026-02-28 — *Optimization update*

“Optimized service bus usage, container apps even get lower overhead as well :D” Shared with monitoring screenshots showing request/message and container metrics.

• 2026-03-01 — *tg2web goals and rationale*

A detailed Chinese post described tg2web as the author’s own internet experiment, largely built with AI assistance, with architecture designed so most microservices are scalable. It outlined goals around SEO, creator convenience, long-term archives, and access outside Telegram.

• 2026-03-01 — *Replay/reconnect test series*

A cluster of posts tested replay after reconnecting:

• “test replay message”
• “Check if replay message comes back after reconnecting”
• “Test it again”
• “Safari has different behavior from Chrome”
• “Test a message with id”
• “Another message while disconnected”
• “Works nice 👍”

• 2026-03-01 — *Header-level confirmation*

A screenshot showed `Last-Event-ID` in the request headers to the stream endpoint, with the note that reconnecting and re-transmitting are working as expected.

Watchlist

• Safari vs. Chrome differences during stream/reconnect behavior.
• Ongoing validation of replay/retransmit flow, especially around `Last-Event-ID`.
• Whether service bus optimizations continue to reduce overhead in the shared monitoring dashboards.
• Further product updates for tg2web, especially around SEO-oriented publishing and broader web access.