8000 [FR] Option to add leecher automatically to the blacklist · Issue #1347 · slskd/slskd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[FR] Option to add leecher automatically to the blacklist #1347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
quorn23 opened this issue May 10, 20 8000 25 · 1 comment
Open

[FR] Option to add leecher automatically to the blacklist #1347

quorn23 opened this issue May 10, 2025 · 1 comment

Comments

@quorn23
Copy link
quorn23 commented May 10, 2025 •
edited
Loading

I noticed slskd using more resources than usually today, looking at the log i quickly find the issue, i had two user, which falling into my leecher limits hammering requests like crazy. Putting them to the blacklist manually quickly fixed the issue.

Could we get an option to put such bad actors automatically to the blacklist? Specially with clients creating 100s of requests in rapid manner?

Example of such a client/user

My leechers settings for context.

Edit: just noticed blacklist doesn't really blacklist them from keeping spamming requests, so this might actually be a bug?
Sadly still happening

    thresholds:
      files: 100
      directories: 10
    upload:
      priority: 999
      strategy: roundrobin
      slots: 1
      speedLimit: 1
    limits:
      queued:
        files: 1
        megabytes: 1
        failures: null
      daily:
        files: 1
        megabytes: 1
        failures: 1
      weekly:
        files: 1
        megabytes: 1
        failures: 1
  blacklisted:
    members:
      - thicc
      - plumaazul
    cidrs: []
  userDefined: {}```
@jpdillingham
Copy link
Member

Have you configured limits for the leecher group? This sort of situation is why those were added; if you set everything to minimums leechers will only be able to get one album a day or whatever.

Them requesting files and being rejected shouldn't be hard on resources, but I can see how spamming logs isn't helpful. It would be a quick change to log those at a debug level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@quorn23 @jpdillingham
0