Add adaptive hostile-network recovery and organization-owned upgrades - #1
Merged
Merged
Conversation
dead-man1
pushed a commit
to dead-man1/CottenDNS
that referenced
this pull request
Sep 2, 2026
…d-reliability Add adaptive hostile-network transport recovery
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.
What changed
WhiteDNS/CottenDns.Why
The Android application sources its native CottenDNS engine from
WhiteDNS/CottenDns. The engine improvements therefore need to live in the organization repository, while organization deployments must not redirect users to the personal fork.Validation
go test ./...passed.