cooldowns #38

Open
opened 2025-03-12 20:46:58 -04:00 by adam · 1 comment
Owner

if vassago has had the same command with the same input triggered x times over y seconds (tune x and y, obv) in a given channel, go into cooldown.

should be a secondary defense against triggering off self, and/or having 2 instances that accidentally trigger each other (e.g., me: "chatgpt" -> shtikbot: "chatgpt is weak" -> magnificent charamote: "chatgpt is weak" -> shtikbot: "chatgpt is weak", etc)

if vassago has had the same command with the same input triggered `x` times over `y` seconds (tune `x` and `y`, obv) in a given channel, go into cooldown. should be a secondary defense against triggering off self, and/or having 2 instances that accidentally trigger each other (e.g., me: "chatgpt" -> shtikbot: "chatgpt is weak" -> magnificent charamote: "chatgpt is weak" -> shtikbot: "chatgpt is weak", etc)
adam added this to the buck passing milestone 2025-06-20 16:50:10 -04:00
Author
Owner

changing the fuck out of this.

new plan!

everything is on a cooldown. telling a joke? adds barely any heat. generating a QR code? adds a significant amount.

...ok cool, why? as a ripcord to prevent infinite loops? in case you add something heavy, like quote-unquote AI? just don't let anyone else touch them, boom done.
although I guess this would be a good proactive prevention against unforseen loops.

changing the fuck out of this. # new plan! everything is on a cooldown. telling a joke? adds barely any heat. generating a QR code? adds a significant amount. ...ok cool, why? as a ripcord to prevent infinite loops? in case you add something *heavy*, like quote-unquote AI? just don't let anyone else touch them, boom done. although I guess this would be a good proactive prevention against unforseen loops.
adam changed title from safety ripcord: per-channel cooldown to cooldowns 2025-06-21 23:33:29 -04:00
adam modified the milestone from buck passing to tomorrow, always a day away 2025-06-21 23:33:42 -04:00
Sign in to join this conversation.
No project
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.

Dependencies

No dependencies set.

Reference: greyn/vassago#38
No description provided.