Overview

The supplied material for this week contains a single product-maintenance update: a small fix was made to the PWA push notifications issue that had been causing occasional failures, with the aim of improving reliability.

Key Themes

• PWA maintenance
• Push notification reliability
• Fixing intermittent failures

Notable Posts

• PWA push notifications: A small issue was fixed in the PWA push notification system. The previously observed problem was intermittent notification failure, and the update is intended to make it work better.

Watchlist

• Whether the intermittent push notification failures become less frequent after the fix
• Any follow-up updates on PWA notification stability

Overview

This week’s supplied post focused on SEO, specifically a sudden surge in tg2web’s Google indexing. The attached Google Search Console screenshot shows a sharp jump to 860 indexed pages, alongside 50 not indexed pages. The same screenshot also shows limited video indexing (1 indexed, 14 not indexed).

Key Themes

• SEO / Google indexing
• Rapid growth in indexed pages
• Search Console performance monitoring

Notable Posts

• “tg2web 的谷歌索引一下子井喷了 #seo”

The post notes that tg2web’s Google indexing “suddenly exploded.” The attached screenshot supports this with a steep late-period rise in the indexed-pages line, reaching 860 indexed pages.

Watchlist

• Whether the indexing spike remains stable in later Search Console updates
• How the indexed vs. not indexed page counts change from the current 860 / 50
• Whether video indexing improves beyond the screenshot’s 1 indexed / 14 not indexed

Overview

I don’t have any posts or media supplied for Miscellaneous things (`chat_id -1003805326518`) in the window 2026-05-18 00:00 UTC → 2026-05-25 00:00 UTC, so I can’t produce a factual digest yet.

Key Themes

• Awaiting source posts/messages
• Awaiting attached media
• If needed, I can also account for images added in comments (`支持评论添加图片`) if those are included in the source data

Notable Posts

• None available from the provided context

Watchlist

Please send the source material in any of these formats:

• Message list with: `timestamp`, `post text`, `media type`, `media caption`
• Exported Telegram posts for that date range
• Links/files for images or videos that should be referenced

Once you provide them, I’ll return a concise markdown digest in the exact format you requested.

Overview

Only one text item was supplied for the requested window, and no post list or media bundle was included. Based on that limited material, the visible topic is a favorable remark linking Rust with AI-related programming.

Key Themes

• Rust and AI: Rust is described positively in relation to AI.
• Opinion-led posting: The supplied text is a personal judgment rather than a detailed technical explanation.

Notable Posts

• “不得不说，Rust真的是属于AI的编程语言”

A Chinese-language statement expressing the view that Rust is especially well-suited to AI-related programming.

Watchlist

• Whether Rust becomes a recurring topic in future posts.
• Any follow-up posts that clarify what “belongs to AI” refers to in practice.
• No media items were supplied for this digest.

Overview

Based on the supplied material, this week’s activity centered on a single post about Azure OpenAI usage and cost monitoring. The post’s caption — “最近燃烧了很多tokens😂 #azureopenai” — highlighted heavy recent token consumption, supported by a dashboard screenshot.

Key Themes

• Azure OpenAI
• Token usage / spend awareness
• Monitoring operational metrics such as requests, input/output tokens, and estimated cost

Notable Posts

• “最近燃烧了很多tokens😂 #azureopenai”
  • The attached Azure OpenAI monitoring screenshot shows:
    • 1.9K total requests
    • 101.04M total tokens
    • $521.53 estimated total cost
    • 100.62M input tokens
    • 418.33K output tokens
  • The charts in the image show a few clear usage spikes within the displayed reporting range.

Watchlist

• Any follow-up posts on Azure OpenAI usage or costs
• Additional context, if shared later, on the request/token spikes visible in the dashboard
• Whether #azureopenai becomes a recurring topic in future posts

Overview

For 2026-04-27 to 2026-05-04 UTC, the supplied material shows a single operational update: a switch from openclaw to Hermes. The stated reason was that openclaw had become slow enough to affect normal use. No other posts or media were provided in the supplied content.

Key Themes

• Tooling change: migration from openclaw to Hermes
• Performance issues: openclaw was reported as too slow for normal usage
• Practical impact: the change appears driven by usability rather than feature discussion

Notable Posts

• Platform switch: “从openclaw切换到了Hermes，前者实在是慢到了影响正常使用了。”
  • English summary: switched from openclaw to Hermes because the former had become so slow that it affected normal use.

Watchlist

• Whether Hermes improves speed and day-to-day usability
• Any follow-up notes on migration outcomes or remaining performance issues

Overview

This week in Miscellaneous things, posts centered on tg2web/web app product updates. The main focus was on comments, notification support for logged-in users, and browser push notifications, with repeated notes about iOS/PWA instability.

Key Themes

• Comments and notifications
  • Comments were reported as ready.
  • Notification support was mentioned as available or being added for logged-in users only.

• Web app push notifications
  • Users can enable browser push by tapping the bell icon on a channel page and allowing browser notifications.
  • Notifications can open the related message detail page.

• iOS-specific issues
  • On iOS, notification clicks were described as buggy and not always able to jump directly to a specific post like on desktop.
  • A later update said iOS seemed to work again, but was unstable.

Notable Posts

• Comments ready; notifications limited to logged-in users
  • A post said comments were already implemented, and notifications would also be available, but only for logged-in users.
  • Attached media showed a Notifications screen with comment-related alerts inside tg2web.

• Web app notification flow added
  • Another post explained that web app notifications were implemented: users just need to tap the small bell on the channel page and grant browser push permission.
  • Attached media showed an iOS-style notification preview for a new post in *Miscellaneous things*.

• Follow-up on iOS reliability
  • A follow-up said browser notifications were still worth doing even with reduced iOS usability.
  • Future work mentioned: push notifications for comments and replies.
  • A Stacker News issue was linked as context for the iOS/PWA notification behavior.

Watchlist

• Rollout of comment and reply push notifications
• Whether iOS deep-linking from notifications becomes stable
• Ongoing limitation of notification features to logged-in users

Overview

This week centered on tg2web infrastructure changes, feature progress, and cost control. The author said AI helped revive several old toy projects and recalculated the operating cost of “AI builds everything” to about $3/week, since there are four channels and usually at least three receive updates. A tg2web test site went live, and the main infrastructure direction shifted from an Azure-heavy setup toward an Oracle Always Free ARM server shared with openclaw. Azure credits were also exhausted early due to AI-related usage, which will delay some weekly reports.

Key Themes

• Simpler architecture over overdesign
  • Reflection that many projects do not need full “cloud-native” or distributed complexity.
  • The earlier Azure microservices setup was stable, but platform overhead was seen as high relative to workload.

• Performance and developer experience
  • A webhook-related message bus was changed from Azure Service Bus to Redis.
  • Reported result: faster performance and a more comfortable development workflow.

• tg2web feature progress
  • Planned/search-related enhancements include:
    • hashtag search
    • ticker search using `$` prefixes such as `$BTC` and `$QQQ`
  • Listed milestones:

1. permalink ✅ 2. ticker/hashtag aggregation ✅ 3. delete protocol ✅ 4. comments ✅

• Integration with openclaw
  • Since tg2web and openclaw are now on the same machine, the plan is to connect their networking and expose some internal APIs from tg2web for operations and management.

Notable Posts

• Weekend plan
  • Migrate tg2web from Azure to an Oracle free ARM server
  • Test direct cooperation between tg2web and openclaw
  • Test site shared: https://test.tg2web.live/

• Architecture reflection
  • The author described starting with a cloud-native Azure microservices approach, then concluding that for many workloads a simpler single-machine setup is more appropriate.
  • Azure container minimum resource sizes were described as more than the project usually needs.

• Oracle host status screenshot
  • The attached image showed multiple running containers on the Oracle server, including tg2web-related services, openclaw, Redis, Postgres, reverse proxy, and other apps.

• Azure spending limit reached
  • An attached Azure screenshot showed services disabled on 2026-04-11 after hitting the spending limit.
  • This was attributed to recent AI-related usage and will delay weekly report updates.

• Next iteration target
  • Comment notifications, in two categories:

1. admin notifications for any post comment 2. reply notifications, excluding self-replies

Watchlist

• Whether the tg2web test site remains stable enough for full migration
• Progress on tg2web ↔ openclaw integration through internal APIs
• Delivery of comment notification features
• Practical impact of moving more workload off Azure after the spending limit was hit
• Adoption of the new hashtag/ticker search workflow for historical lookup

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.