feat(telegram): add telEgo backend - #5537
Draft
Scratch-net wants to merge 1 commit into
Draft
Scratch-net wants to merge 1 commit into
Scratch-net wants to merge 1 commit into
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.
Add telEgo v0.5.4 as a Hiddify Telegram proxy backend.
The service:
127.0.0.1:1001;127.0.0.1:10087.Depends on hiddify/hiddifypanel#36, which adds the panel selector, per-user links, and usage accounting. After that PR merges, this branch must update the Panel submodule before this PR is ready to merge.
The initial integration enables MTProxy only. Hiddify's current Telegram fake-domain setting is an external FakeTLS mask, not an owned WEB hostname with a certificate. Native WEB carrier support therefore needs a separate frontend and panel settings change.
Validation completed:
bash -n.