Implemented volatile chat buffer for channel chats. Standard chat messages now survive channel refresh and show up for newly connected users: 366df357b8

Next is to make timed DB backups for channel messages, and a RAM-only buffer for global ones.

It's probably best that shutdown-related server announcements don't survive restart, and not really a big deal that toke messages don't either.

Implemented volatile chat buffer for channel chats. Standard chat messages now survive channel refresh and show up for newly connected users: 366df357b863d064adba1176fdb41f43e167cdeb Next is to make timed DB backups for channel messages, and a RAM-only buffer for global ones. It's probably best that shutdown-related server announcements don't survive restart, and not really a big deal that toke messages don't either.

rainbownapkin commented

2025-07-22 07:55:01 -04:00

(Migrated from gitlab.com)

Chat messages should set off a 2-5 second timer that gets reset if a new chat is received before it goes off.

At the end of the timer, if no new messages have been received since the timer was last reset, the DB should save.

A second 5-10 minute timer run happen in the background along side the shorter one, that gets cut off short the moment the first timer completes (IE: whenever a DB transactions occurs.) If this timer ends, it means the chat room has been busy for 5-10 minutes without a save, and should be saved regardless of how busy it is.

This ensures that DB transactions occur as chats happen in slow rooms, while ensuring the DB isn't constantly saving on busy rooms.

Chat messages should set off a 2-5 second timer that gets reset if a new chat is received before it goes off. At the end of the timer, if no new messages have been received since the timer was last reset, the DB should save. A second 5-10 minute timer run happen in the background along side the shorter one, that gets cut off short the moment the first timer completes (IE: whenever a DB transactions occurs.) If this timer ends, it means the chat room has been busy for 5-10 minutes without a save, and should be saved regardless of how busy it is. This ensures that DB transactions occur as chats happen in slow rooms, while ensuring the DB isn't constantly saving on busy rooms.

rainbownapkin (Migrated from gitlab.com) closed this issue

2025-07-23 01:07:21 -04:00

rainbownapkin commented

2025-07-23 01:07:22 -04:00

(Migrated from gitlab.com)

Persistent chat buffer complete: c64b315fdf

Persistent chat buffer complete: c64b315fdf9fc76f797ff6a077405bbbdedd176a