!dnsbl format is clumsy, hard to remember and not used

[jesopo]

• having to write out a category name is cumbersome (imagine !dnsbl DNS/MX type hostname detected on IRC)
• dronebl listings can also take a freeform comment for additional info that should be distinct from category (currently hardcoded to "used by irc spam bot" in Sigyn, which is likely a good overridable default)
• having a default category encourages people to list IPs without concern for category (type 3 is often not accurate!)

I'd like to propose switching to category numbers or short names, as well as making categories mandatory:
KLINE 1440 *@1.2.3.4 :[...]|!dnsbl 19 vpngate ip
KLINE 1440 *@1.2.3.4 :[...]|!dnsbl vpn vpngate ip
KLINE 1440 *@1.2.3.4 :[...]|!dnsbl 6
where the format is !dnsbl <category> [comment ...] !dnsbl [<category> [<comment ...>]]

obviously this comes at the cost of making sure everyone is informed about categories, but i don't think it's unreasonable to ask for accurate listing details.

[jesopo]

I think there's a robust debate to be had about mandatory vs optional category - a question of convenience vs accuracy; whether the effort necessary to recall and use categories for each !dnsbl will outweigh the perceived benefit, and thus end up in less use of it.

aside from this, if there must be a default category, type 6 is correct more often than 3 is.

[ncoevoet]

maybe only use this ticket to default to type 3 and leave it as it is ?

[jesopo]

I'd still like a better way to request a given category and also a way to give a comment that isn't hardcoded

[ncoevoet]

either we limit to few categories which is more human friendly to memorize, or we use the digit code or i don't know i'm a bit out of idea :)