"!dibs @other" should call dibs for the other user

h/t Sam

!-+ should give up the DAC and immediately join the queue

Might be interesting to track

• who had the baton the most, longest, shortest
• when the baton is used
• who stole the most
• who locked the most
• etc

The lists of happy and angry emoticons are currently hard-coded. Should be comma-separated lists in configuration instead.

Video has a use case where they have 2 resources and don't care which one comes free first so it would be desirable to call dibs on whichever comes free first.

e.g. !lock for demo until 11am

Mention comment in !status response

DACbot simply ignores them, even if they change it back to the original.

If someone is in the queue for more than 5 minutes maybe the DAC should notify the current owner at 5 or 10 minute intervals, TBD.

Something like:
!reserve at 4pm for 1 hour

DACbot might give the current owner of the DAC warnings at 15, 10 and 5 minutes before automatically stealing the DAC for the user with the reservation.

Maybe should be disabled by default. Only when enabled in config should a user be able to issue commands for another user

The bot should parse the DAC log to get the IP address connected to the DAC then parse the output of "ping -a" to get a machine name.

If a user acquires the resource by being next in line and there is someone else in line, then DACbot should say:

"@{User} the {baton} is yours! But since @{Next} is also waiting in line you have 60 seconds to call dibs before I automatically rescind for you."

If the user does not call dibs within the time limit then the current owner will be moved to the back of the line and the next user will acquire (starting this process again).

While locked the DACbot would prevent others from calling dibs or stealing

Qbot ignores users with unicode characters in their name

Should keep acquire times separate