Respond to deadline violations in PM #3

New Issue

lupine · 2019-10-23T21:56:17+01:00

lupine commented

2019-10-23 21:56:17 +01:00

Commands that fall foul of a deadline are currently dropped on the floor with no feedback. The intent of deadlining is to prevent channel flooding, but the lack of feedback can make users issue repeated commands in an attempt to get any sort of response from the bot - lack of a response is interpreted as brokenness / slowness instead of rate-limiting.

There's a commented-out feature to extend the deadline each time it is violated, which is a Pavlovian attempt to curb this behaviour, but a little extreme.

The better option is to send the requester a PM when their command is dropped, informing them of the deadline violation. If deadline extension still needs to be implemented after that, the PM can include information about how much longer their actions mean they have to wait. This should increase effectiveness.

Commands that fall foul of a deadline are currently dropped on the floor with no feedback. The intent of deadlining is to prevent channel flooding, but the lack of feedback can make users issue repeated commands in an attempt to get any sort of response from the bot - lack of a response is interpreted as brokenness / slowness instead of rate-limiting. There's a commented-out feature to extend the deadline each time it is violated, which is a Pavlovian attempt to curb this behaviour, but a little extreme. The better option is to send the requester a PM when their command is dropped, informing them of the deadline violation. If deadline extension still needs to be implemented after that, the PM can include information about how much longer their actions mean they have to wait. This should increase effectiveness.

Sign in to join this conversation.

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: lupine/lysenko#3