Add an entry for a newly available obfuscator #108
Closed
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
Member
|
That page isn't where that would belong and given that I literally maintain the unpackager, you should have a good idea what I think about this |
Member
|
it would not be completely unreasonable to mention obfuscators on the unpackager, though |
Author
|
k |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposed Changes
I've made an obfuscator that may be helpful for Scratch users. I want to add entry for the obfuscator so everyone can use this.
Reason of Changes
There was no (public or open source) obfuscator for Scratch before, while many users need obfuscation, so I think adding a new obfuscator here is reasonable.