Editing public torrents#196
Open
L4cache wants to merge 3 commits into
Open
Conversation
public torrents don't have this field at all by default, adding it (even without changing to private) will change the info hash.
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.
Public torrents don't have this field at all by default, adding it (even without changing to private) will change the info hash.
argsis always populated with the keys, so even without doing anything related, the editing will always result in chaning of info hash, because of the additional private flag.This changes info hash so no worries of leaking?
Maybe the announce list should be automatically cleared?