Add many more shorteners, and fix a few open issues #16
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
…and probably others behind Cloudflare, and maybe smfreegard#9)
…orter shortener list than here. Remove the shorteners already present upstream, so this config can (mostly) be used together with the updated plugin.
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.
Hey,
SpamAssassin's shortener list in 72_active.cf (see PDS_URISHORTENER) seems to be maintained, and has many more shorteners than the ones in this current config (but includes all of them), so I re-synced the list against SpamAssassin's. I also fixed some low-hanging fruit from the issues list, added a few shorteners that SpamAssassin was missing, and fixed the *_BLOCKED checks to also work with HTTPS (unreported).