Expirement with splitting chatHandler.js #240

Open
opened 2026-10-11 22:28:37 -04:00 by rainbownapkin · 1 comment

Expirement with splitting chatHandler into individual per-channel objects with a separate globalChatHandler object for tokebot and other server-wide announcements.

We should probably make commandProcessor.js per-channel too.

This would make the channel back-end more uniform, and better suited for a potential future in-which channels run inside of dedicated web-workers.

Expirement with splitting chatHandler into individual per-channel objects with a separate globalChatHandler object for tokebot and other server-wide announcements. We should probably make commandProcessor.js per-channel too. This would make the channel back-end more uniform, and better suited for a potential future in-which channels run inside of dedicated web-workers.
rainbownapkin added this to the 0.3-Alpha (Acapulco Gold) milestone 2026-10-11 22:28:37 -04:00
rainbownapkin added the
Cleanup/Refactor
Performance Improvement
labels 2026-10-11 22:28:37 -04:00
rainbownapkin self-assigned this 2026-10-11 22:28:37 -04:00
Author
Owner

We should do this last so that if it turns out in production to be a terrible idea we can roll back to a version that has everything but this.

We should do this last so that if it turns out in production to be a terrible idea we can roll back to a version that has everything but this.
rainbownapkin added a new dependency 2026-10-28 19:54:47 -04:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
Reference: rainbownapkin/canopy#240
No description provided.