Overview

This week’s posts mixed personal reflection, cost-of-living concerns, and AI tooling updates. The channel touched on growing impatience at work, a conversation about how expensive buying a home in the UK has become, and progress in setting up an Azure/OpenClaw-based workflow for generating digests with GPT-5.4-class models at manageable cost.

Key Themes

• Work mindset: A brief personal note about becoming less tolerant of incompetence at work, alongside a reminder to stay patient with the world.
• Housing affordability: A conversation with a former Autodesk colleague now in the UK highlighted high mortgage costs there: a 2-year fixed rate of 5.2%, and a rough example of a £640k ordinary city house leading to about £3,200/month over 35 years.
• AI tooling setup: Company-provided Azure access was used to apply for Foundry and connect it to OpenClaw. The attached screenshot showed OpenClaw running with `azure-openai-responses/gpt-5.4`, reporting $0.0000 cost in that session and a 50% cache hit.
• Digest automation economics: A digest workflow was described as completed, with a reference link shared. Backfilling nearly two months of data using GPT-5.4 Pro was said to have an acceptable cost because it was tied to an existing subscription; the stated estimate for ongoing weekly runs was about $0.6–$0.7/week. The attached monitoring screenshot showed 21 requests, 234.88k total tokens, and $13.74 estimated total cost.

Notable Posts

• A short reflection on worsening impatience with “stupidity,” especially at work, and the need for more patience.
• A detailed note on UK home-buying pressure based on a friend’s experience: high rates, high prices, and the broader conclusion that financial anxiety is hard to avoid without substantial money.
• A post about successfully using a company Azure subscription to get Foundry access and hook it into OpenClaw, with a status screenshot attached.
• A follow-up saying the digest setup was already done, linking to a reference page and sharing cost observations from a GPT-5.4 Pro backfill, with an Azure metrics screenshot attached.

Watchlist

• Whether the weekly digest workflow actually stays near the stated $0.6–$0.7 per week.
• How the Azure Foundry + OpenClaw setup performs over time in real use.
• Continued attention to two recurring pressures surfaced this week: work frustration and housing/cost-of-living stress.

# Weekly Digest — Miscellaneous things Window: 2026-03-23 to 2026-03-30 UTC

Overview

This week’s posts were mainly operational updates around tg2web and Telegram API constraints, plus a note that AI-based weekly digest generation may be added in the future.

Key Themes

• Possible AI integration: considering adding AI functionality to generate weekly digests.
• Deletion workflow for tg2web: posts intended to be hidden from tg2web should be edited with `#tg2web下划线delete` instead of being deleted directly in the channel.
• Telegram API limitation: attachments of 20MB or larger were noted as unavailable for download via the API.

Notable Posts

• 2026-03-29 — AI weekly digest
  • The channel mentioned it is considering integrating AI features to generate a weekly digest.

• 2026-03-29 — tg2web deletion support
  • A deletion workaround was introduced: to prevent a post from showing on tg2web, do not delete it directly in Telegram; instead, edit the post and add `#tg2web下划线delete`.
  • Reason given: Telegram Bot API does not notify bots about deletions.

• 2026-03-27 — 20MB+ attachment download limit
  • A Telegram API restriction was noted: attachments 20MB and above are not offered for download.
  • The post added that this is not especially important for the tg2web product.

Watchlist

• Whether AI-generated weekly digests are actually implemented.
• Adoption of the new `#tg2web下划线delete` workflow for hiding posts from tg2web.
• Any future handling or workaround for the 20MB+ attachment download limitation.

Overview

In the 2026-03-09 to 2026-03-16 UTC window, the channel focused on product/site development updates. The main completed milestone was the comment system, which now allows publishing comments via Google login. The roadmap then shifted toward enhancement work: richer comments, multi-tenant hosting, link previews, and better navigation from replied messages.

Key Themes

• Comments launched: Comments were completed over the weekend and are available with Google login.
• Comment enhancements under consideration: Possible additions include one image per comment and rich-text formatting (for example bold, underline, italics).
• Multi-tenant support: Multi-tenant hosting was discussed as a likely next goal so the site could host content for others.
• Iteration roadmap: A follow-up post listed next-iteration goals, including:
  • comment rich text + image support
  • multi-tenant hosted content
  • click replied-to message to jump to the relevant location/details page ✅
  • link previews

Notable Posts

• 2026-03-11 — Comments completed
  • The author said comments were finished over the weekend and that publishing a comment only requires logging in with Google.
  • Rich text and image support for comments were described as possible, non-urgent enhancements.

• 2026-03-12 — Multi-tenant direction
  • The author suggested making multiple tenants the next goal, with the aim of extending the site to host content for other people who need it.

• 2026-03-12 — Next iteration goals
  • A roadmap was posted covering:

1. comment rich text + image support 2. multi-tenant hosted content 3. replied-message jump to location/details page ✅ 4. link preview display

Watchlist

• Whether rich-text + image support for comments moves from idea to implementation
• Progress on multi-tenant hosting
• Addition of link previews
• Further details or rollout status for the replied-message jump feature

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.

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.

Overview

• 7 posts were published during the covered window, all on 2026-02-21 to 2026-02-22 UTC.
• All posts were short, text-only updates; no media was shared.
• The week’s activity was concentrated in a brief weekend burst and centered on casual check-ins and mood/status messages.

Key Themes

• Introductory / presence-style posts:

“Another channel!”, “Hey”, “Second one!”, “Here”

• Personal status updates:

“I am good :-)”, “Feeling tired 🥱”

• Weekend sentiment:

“Weekend is always the best while too short...”

Notable Posts

• 2026-02-21 20:40 UTC — “Another channel!”

Earliest post in the supplied set.

• 2026-02-21 20:42 UTC — “I am good :-)”

A direct personal status update.

• 2026-02-22 19:43 UTC — “Weekend is always the best while too short...”

The clearest thematic post of the week.

• 2026-02-22 21:04 UTC — “Feeling tired 🥱”

Latest post in the window.

Watchlist

• Whether the recent weekend posting burst continues into the next week.
• Whether posts remain brief personal check-ins or develop into more defined recurring topics.
• Whether future updates include media, since this week was entirely text-only.