Add an exception list option to the preferred external downloader
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Start by locating the existing preferred external downloader setting and the download-selection flow it affects. Review how WebLibre currently chooses between its internal and external downloaders, then identify where host exceptions should be configured. Done means users can add host exceptions and downloads from those hosts retain the normal downloader choices while other downloads use the preferred external downloader.
Written by the indexing model from the issue text.
Description
The new “choose external downloader as preferred downloader” option is a very useful addition.
It would be great if this setting could also have an exception list for specific sites/hosts.
For example, I may want to use an external downloader as the preferred downloader in general, but for:
"drive.usercontent.google.com"
I may want WebLibre to not prefer the external downloader and instead keep its normal download behavior, including the usual internal/external downloader choices.
The 1DM Integration Module extension currently provides this functionality through its site exception list. Adding a similar exception list to WebLibre would cover the remaining part of the extension that I use.
For example:
Preferred downloader: External downloader
Exceptions:
"drive.usercontent.google.com"
"example.com"
This would allow users who currently use the 1DM Integration Module for this functionality to remove the extension entirely and have the functionality built directly into WebLibre.
Thanks for considering it!
Screenshot of 1DM Integration Module extension 👇
- Dominant language
- Dart
- Stars
- 1k
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FaFre/WebLibre
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
enhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 60/100
-
enhancement needs-triage
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
bug enhancement needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
needs-triage
Difficulty 4/5 1-2 days Newbie friendliness 48/100
Similar issues
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] JEFIT import fails because # characters are not recognisedPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day