type: rule
status: active
timestamp: 2026-06-22
tags: [rule, telegram, channels, india, geo, notifications, drafts]

Telegram channels and roles (restored 2026-06-22)

4 Telegram channels in Oriz namespace

Telegram channels and roles

Status: restored 2026-06-22

User confirmed Telegram is accessible from India again. Supersedes no-telegram-india-banned.md (now archived as superseded).

Four channels

ChannelVisibilityRole
@oriz_announcementsPublicEvery release, book drop, blog post auto-broadcast. Subscribers = audience.
@oriz_draftsPrivate (admin only)omni-publish queues X / Reddit / LinkedIn / Medium drafts here. Dual-written to GH Issues repo too.
@oriz_opsPrivate (admin only)Build / deploy / Dependabot / error / uptime alerts from all 51 repos.
@oriz_paisaPublicIndia finance content (Oriz Paisa book audience, FII/DII commentary, credit-card news).

Namespace = @oriz_* not @chirag127_* — brand-owned, easier to hand off, decoupled from the person.

Drafts: dual-write to TG + GH Issues

omni-publish writes manual-channel drafts (X, Reddit, LinkedIn, Medium) to BOTH @oriz_drafts Telegram channel AND chirag127/oriz-drafts GitHub Issues. Reason: TG = mobile notifications + speed; GH Issues = searchable history + audit trail. Either side can fail and the other survives.

Substack stays in addition

Substack remains the long-form newsletter (free tier; paid future deferred). Telegram is the high-frequency broadcast layer. They serve different audiences:

Cross-posting: every blog post auto-publishes to BOTH (omni-publish handles the fan-out).

Env vars

TELEGRAM_DRAFTS_BOT_TOKEN, TELEGRAM_DRAFTS_CHAT_ID — keep (no longer deprecated). Add TELEGRAM_ANNOUNCE_CHAT_ID, TELEGRAM_OPS_CHAT_ID, TELEGRAM_PAISA_CHAT_ID in templates/.env.example.

If user travels / TG re-banned

Switch to GH-Issues-only drafts (still dual-written, just stop reading TG). The rule auto-fails-back; no code change needed.

Cross-refs


Edit on GitHub · Back to index