[PT]Devilishly wrote:I’m using a message kind like that since I’m using it always in away mode. It could also be added some commands so users could use in private with our nick(those commands could be defined by us).
Yeah! Built in triggers would be real cool! Maybe some sort of main chat trigger could be added too. We have a hub without any scripts at all to minimize the strain on the hub. Would be cool to be able to have standalone triggerbot built in
You could argue that such a feature might be abused by someone, to maybe advertise whenever anyone says anything... I'm sure such a user would be kicked/banned instantly... but just to be sure.. maybe should add an OP-Check to all of these abusable features.
[PT]Devilishly wrote:To resolve problems like in some ptokax hubs, which some ops are check as normal users even thou we have the option “Do not check ops” activated, it could be added a “Secure nick list” where we could enter a nickname and DNS or IP from hub, and those users won’t be checked.
Yeah! Great idea too! Our hub has alot of regulars that are "trusted". Nice to exclude them from the checks.
[PT]Devilishly wrote:And when it works fine, it could be added in the ADL Search, on the “Source Type” also a parameter “extension”. Because, I’m not sure but, for example, if I defined “.dll” as forbidden file, may also files like “abcde.dllabcd.avi” be considered as forbidden file?!
Yes! It would be considered fake.. Source type exactly like the real search is a great suggestion!
[PT]Devilishly wrote:Just another suggestion, since DC++k is a OP client, why not take the normal tag description of, and add to it only something like “[++k x.xx]”?
Well, it's not only used by OPs, and simply removing the tag would give users a cheating possibility. Maybe with an OP-Check?
When we are on the subject, I don't like that the UL limiter is hidden, should show as U:XX or something!
More feature suggestions:
1. Regular search for forbidden files!
DC++k could use the normal search strings to search for forbidden files, and trigger on the returned results. It could go trough the added files, one every X minutes or something (to keep the traffic down).
2. Duplicate folder detection!
A common cheat is to share the same drive multiple times, DC++k have no way to detect this (today). Could have a feature that compares the folders in the root of the filelist, by looking one step inside them, and comparing their size... if match = cheater!