The new invitation info/reminder needs to calm down.

I just got this after reconnecting (all times CEST)

[13:51:57] <mockturtle> Looking for an invitation wink? https://lobste.rs/about#invitations has an intro, and https://lobste.rs/chat explains some expectations for this channel. (I am the channel bot.)
[13:51:57] <mockturtle> Looking for an invitation wink? https://lobste.rs/about#invitations has an intro, and https://lobste.rs/chat explains some expectations for this channel. (I am the channel bot.)
[13:51:57] <mockturtle> Looking for an invitation wink? https://lobste.rs/about#invitations has an intro, and https://lobste.rs/chat explains some expectations for this channel. (I am the channel bot.)
[13:51:57] <mockturtle> Looking for an invitation wink? https://lobste.rs/about#invitations has an intro, and https://lobste.rs/chat explains some expectations for this channel. (I am the channel bot.)

We assume these were triggered by one of my lines hours earlier:

[11:21:38] <wink> .. invited ..
[11:23:38] <wink> .. invitee .. invited ..
[11:23:55] <wink> .. inviting ..
[11:24:38] <wink> .. invitees ..

• too eager
• not ignoring users who talk about invites, inviting, etc. which can also happen by this imagined dialog:

<a> Hi, can I get an invite?
...
<b> a: I have sent you an invite

Not sure how to fix it, the idea was good. But it needs at least a debounce and maybe even ignore users with > 100 lines. (not sure if worth keeping a hashmap of (md5(nick), count), maybe until restart is fine)

The issue does not name the files or tests containing the invitation reminder; start by locating the logic that emits the “Looking for an invitation” message and reviewing how chat lines are matched. Reproduce the repeated messages from the examples, then verify that reminders are debounced and ordinary invitation-related conversation does not trigger repeated notices.