Clone

HTTPS: git clone https://vervis.peers.community/repos/yEzqv

SSH: git clone USERNAME@vervis.peers.community:yEzqv

Branches

master

2.mdwn

[[!template id=ticket class=proposal]] [[!tag /projects/funbot/ideas]]

[[!meta title=“Message delay to avoid flooding”]]

Issue

Right now, the bot uses a single TCP connection. If it’s closed for any reason, the event loop ends and the bot turns off. After 10 minutes the cron job runs it again, but it’s better to have the bot handle restarting the connection by itself if it get closed, which will improve uptime.

Plan

Check how existing Haskell IRC bots do this, and read about the technical details of flooding to understand fully.

Perhaps we can keep a timestamp within the Session monad and use that to test for flooding. Another idea is an asynchronous. If an output queue ran in a separate thread (this deserves its own ticket), it could handle flooding prevention elegantly in its event loop.

Result

None yet.