mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Make 'all' working search plugins available by default #8682
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#8682
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lyndalopez544 on GitHub (May 14, 2019).
Thus:
@thalieht commented on GitHub (May 14, 2019):
Read #5766
@lyndalopez544 commented on GitHub (May 23, 2019):
@thalieht that doesn't solve the problem.
All those plugins have to become available by default to everyone to show the real power of the BitTorrent network.
No BitTorrent client has done such a thing before, especially the open-source ones.
@thalieht commented on GitHub (May 23, 2019):
But they are available to everyone just by checking for plugin updates! If i understand correctly that you propose to bundle the plugins with the installer then that tells me that you did not read that link. It used to be this way but was changed for reasons explained there and effort was put into changing it. Ergo, I'd say there is no chance of the devs wanting to revert that.
I don't like closing issues with suggestions without some dev reply, but in this case i'm sure that none of them want this.
p.s. if i misunderstood and that's not what you're proposing let me know and i'll reopen.
@lyndalopez544 commented on GitHub (May 30, 2019):
@thalieht All the search plugins should be bundled into the app like a native functionality with zero configuration and also updated automatically.
@Seeker2 commented on GitHub (May 30, 2019):
Is there any known problems with conflicting plugins? (where using one prevents/interferes with others)