connector: add optional Telegram portal approval workflow#1071
Draft
nikolya-prodigy wants to merge 1 commit intomautrix:mainfrom
Draft
connector: add optional Telegram portal approval workflow#1071nikolya-prodigy wants to merge 1 commit intomautrix:mainfrom
nikolya-prodigy wants to merge 1 commit intomautrix:mainfrom
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
1 participant
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
Adds an optional Telegram portal approval workflow.
When
portal_approval.enabledis true, automatic portal creation can be controlled per chat type:Chats that are not auto-created can be stored in a pending list and managed from Matrix commands:
pendingalloweddeniedallow <number>deny <number>unallow <number>undeny <number>The pending list stores readable chat titles/usernames plus stable numeric approval IDs so admins do not have to copy raw Telegram IDs.
Additional changes
This branch also avoids creating ghost users from passive/background updates in several paths, so rejected or pending chats do not populate the Matrix user list before they are approved.
It also includes the
cleanup-usersadmin command as a conservative bridge-side cleanup tool.Compatibility
The feature is disabled by default. Existing behavior should be unchanged unless
portal_approval.enabledis set.Testing
go test ./pkg/connector/...Notes
This is opened as a draft because the feature is intentionally policy-heavy and I would like maintainer feedback on the preferred UX/config shape before polishing further.