Telegram channel → Miscellaneous things · Weekly digest

Powered by AI · Summaries may miss nuance, so verify important details against the original posts.

Week 10 (2026)2026-03-02 to 2026-03-08

Overview

This week centered on development updates. The early part of the week continued SSR work, including an SSR-for-SSE launch and a fix so edits to posts with multiple media no longer show up as new posts. By mid-to-late week, attention shifted to rendering quality: entities were added, and a series of tests covered code blocks, inline code, italics, links, bold-linked text, and photo posts. By the end of the window, single-post pages were supported, and likes, sharing, and “view on Telegram” were reported as done; comments were the main remaining item. The feed also included two photo-based posts: a neighborhood scene and a sunset-lit shelf/bookshelf.

Key Themes

  • SSR progress: “More SSR” was followed by “SSR for SSE launched.”
  • Event/media handling: Editing posts with multiple media was fixed so it no longer emits a new-post event.
  • Rich text and entities: Entities were added, with follow-up tests for formatting and link behavior.
  • Post rendering: Support for one page per post and testing of multi-photo posts.
  • Engagement features: Likes (with real-time count updates), sharing, and “view on Telegram” were marked complete; the latter requires a public channel.
  • Visual interludes: A neighborhood photo and a warmly lit indoor shelf photo broke up the development posts.

Notable Posts

  • Mar 3 — Post 27: “SSR for SSE launched.”
  • Mar 3 — Post 28: Fix for edited posts with multiple media no longer being treated as new posts.
  • Mar 7 — Posts 32–40, 42: Entities were added and then tested across formatting cases: code blocks, inline code, italics, text links, raw links, bold-linked text, and photo posts.
  • Mar 7 — Post 44: “Support 1 page per post now!” with a screenshot of a single-post view.
  • Mar 8 — Post 45: Likes, sharing, and “view on Telegram” were reported as finished; comments were identified as the next major feature.

Watchlist

  • Comment system: explicitly noted as the main remaining task, with user authentication/login needed; current plan mentions Google only.
  • Rich text support: planned for later, with the goal of richer text presentation.
  • Further rendering polish: this week’s formatting and media tests suggest continued work on text/link/code/media behavior.
💬 Comment

Comments

No comments yet.