Set background color for specific trackers #15657

New issue

Open

opened 2026-02-22 02:21:46 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:21:46 -05:00

Owner

Originally created by @Symbai on GitHub (Apr 9, 2024).

Suggestion

Would be nice if we can define custom background colors for specific trackers making it easier when you have a +600 torrent list. (For the same reason why for example torrents with missing files have a different color)

Use case

Make it easier to see which torrents belongs to which tracker when viewing all torrents.

Extra info/examples/attachments

Previous request #13242 was closed as a duplicate but it's not a duplicate. The other mentioned issue is about specifically highlighting non-working torrents, while this request is about setting background color based on trackers.

Originally created by @Symbai on GitHub (Apr 9, 2024). ### Suggestion Would be nice if we can define custom background colors for specific trackers making it easier when you have a +600 torrent list. (For the same reason why for example torrents with missing files have a different color) ### Use case Make it easier to see which torrents belongs to which tracker when viewing all torrents. ### Extra info/examples/attachments Previous request #13242 was closed as a duplicate but it's not a duplicate. The other mentioned issue is about specifically highlighting **non-working** torrents, while this request is about setting background color based on trackers.

deekerman added the

Feature request

label

2026-02-22 02:21:46 -05:00

deekerman commented

2026-02-22 02:21:50 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**