Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a private Telegram chat flow for channel creation and updates.
This lets the owner talk to the bot directly and add or update channel records in Mongo without editing files or running manual scripts.
What Changed
Why
The current receiver only supports one rigid message format and only inserts new channels. It also polls hourly, which makes a private “conversation” impractical. This
change makes channel intake usable as an actual bot conversation and keeps the DB as the source of truth.
Validation
Notes
This is restricted to the configured owner account (telegram.papa, currently XXXXX).
After merge, restart the consumer so the running process picks up the new receiver flow.