lordgrim77/postfixer

Purpose and deployment shape

PostFixer is a Telegram rich-message system deployed as three independent Cloudflare Workers: a bot backend, a formatting Web App, and a custom-emoji manager. The workers are manually deployed as self-contained JavaScript; frontends are embedded into worker artifacts rather than hosted separately.

Core deployable entry points:

• worker.js

• webapp_worker.js

• emoji_manager_worker.src.js (source; compiled target is expected as emoji_manager_worker.js, though that non-obfuscated root artifact is absent)

• obfuscated/emoji_manager_worker.js

Telegram bot backend

worker.js is the webhook-facing control plane. It receives Telegram updates, handles normal bot interactions and inline queries, applies rich formatting, and calls Gemini for AI-assisted formatting behavior. It also connects the bot experience to the formatting and emoji-management web apps through configured public URLs.

Relevant boundaries:

• Telegram Bot API through BOT_TOKEN

• Google Gemini through GEMINI_API_KEY

• Cloudflare bindings: KV, EMOJI_MANAGER_KV, and D1 DB

• Runtime configuration including BOT_USERNAME, ADMINS, and EMOJI_MANAGER_URL

Formatting Web App worker

The formatting Web App is an API-and-static-hosting worker. Its editable template is webapp_worker.src.js; webapp_worker.js is the generated deployable artifact. It serves the rich-text editor UI and coordinates API calls that require the bot token or the bot worker.

Paths:

• webapp_worker.src.js

• webapp_worker.js

• frontend/index.html

• frontend/app.js

• frontend/react_editor.js

The worker’s infrastructure boundary is Cloudflare WEBAPP_KV, with BOT_WORKER_URL used to reach the bot backend and BOT_TOKEN used for Telegram operations.

Emoji manager worker

The emoji manager is a separate Web App/API boundary for associating standard Unicode emojis with Telegram Premium custom emoji stickers. It retrieves sticker metadata from Telegram and supports personal mappings plus administrator-managed global fallback mappings. The UI uses hover-triggered Lottie animation behavior to limit client CPU use.

Paths:

• emoji_manager_worker.src.js

• emoji_manager_frontend/index.html

• emoji_manager_frontend/app.js

• emoji_manager_frontend/style.css

It uses EMOJI_MANAGER_KV for persisted mappings, ADMINS to authorize global edits, and BOT_TOKEN to query Telegram.

Frontend-to-worker asset pipeline

The source frontends are not independently deployed. build_all_obfuscated.js reads the formatting and emoji-manager frontend assets, encodes them into worker-served content, obfuscates JavaScript, and emits deployment artifacts. Any UI modification requires rebuilding before worker deployment.

Paths:

• build_all_obfuscated.js

• frontend/

• emoji_manager_frontend/

• obfuscated/webapp_worker.js

• obfuscated/emoji_manager_worker.js

build_combined.js and related patch scripts indicate an evolving generated-worker workflow, but the all-in-one build script is the documented primary pipeline.

Storage and cross-service flow

Primary request flow is: Telegram update → worker.js → Telegram/Gemini/KV/D1 as needed → Telegram response. For interactive editing, Telegram opens the formatting worker, which serves its embedded UI and communicates with the bot worker/Telgram APIs. Emoji-manager interactions remain isolated in their own worker and KV namespace binding, while the bot references its public URL to expose the feature.

D1 holds aggregate counters in global_stats; KV stores application state, web-app state, and emoji mappings. Cloudflare Workers provide the runtime, Telegram is the user-facing external platform, and Gemini is the AI dependency.