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