You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2021. It is now read-only.
Often we quiet someone, then the quiet expires, we need to re-quiet (soon, or not soon), and we start thinking what duration to set. Was the user a problem before? If so, how many times? eir should be able to show all bans (active, and inactive ones too) matching a query.
Questions
Do we need such command?
Yes?
What should it be named?
Is btsearch ok?
What should it search by? Possible answers for 'btsearch lamer':
Matches by nick - returns all bans whose mask matches lamer's currently connected mask.
Matches by mask - returns all bans whose mask contains the phrase 'lamer'.
Matches by ban comment - returns all bans whose comment contains word 'lamer'.
I think we should be searching them all and merge the results into one list?
The text was updated successfully, but these errors were encountered:
A couple of concerns that spring to mind are ensuring that it isn't possible to perform queries that would be taxing on the database (capping the number of rows returned at some sensible limit may be suffient for that) and avoiding information leaks - when reporting on active bans btinfo will only allow a user to see entries they are permitted to, and this should be the same for historical records.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context
Often we quiet someone, then the quiet expires, we need to re-quiet (soon, or not soon), and we start thinking what duration to set. Was the user a problem before? If so, how many times? eir should be able to show all bans (active, and inactive ones too) matching a query.
Questions
btsearch
ok?The text was updated successfully, but these errors were encountered: