feat(filters): detect magnet links from feed entries #122
Conversation
This file contains 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.
This PR adds a new filter
magnetthat extracts magnet links from the body of the feed entry and store them in places recognized by bittorrent clients.For feeds in RSS format, the magnet links will be stored in the
<enclosure>. For feeds in Atom format, the magnet links will be stored in a new<link>.The filter has two configurations:
info_hash(boolean, default: false): whether or not to try detect info hash withoutmagnet:prefix. It's used when the magnet link is not directly given in the body in strict magnet link format but somehow extractable.override_existing(boolean, default: false): if the entry already contains a magnet link in its enclosure, whether or not to override it with the detected one.