Persistent chat history #1

Merged

riki merged 1 commit from push-sxmuwrnkqzkk into main

2026-04-02 16:48:39 +02:00

riki commented

2026-04-02 16:32:19 +02:00

Owner

Implement persistent chat history by saving messages into an SQLite database.

Since it has to be possible to correlate history with specific rooms, this also implements a table storing existing rooms and their metadata (currently only who created the room.)

Messages use bespoke snowflake IDs as their primary key, that is Unix timestamps coupled with a sequence counter. Our snowflake is tailored towards running on a single machine, and has 56 bits for a Unix timestamp (millis) with an 8 bit sequence counter for handling concurrent writes in the same millisecond. You would have to send 256 messages in a millisecond to cause a collision which is not realistic in our case.

Implement persistent chat history by saving messages into an SQLite database. Since it has to be possible to correlate history with specific rooms, this also implements a table storing existing rooms and their metadata (currently only who created the room.) Messages use bespoke snowflake IDs as their primary key, that is Unix timestamps coupled with a sequence counter. Our snowflake is tailored towards running on a single machine, and has 56 bits for a Unix timestamp (millis) with an 8 bit sequence counter for handling concurrent writes in the same millisecond. You would have to send 256 messages in a millisecond to cause a collision which is not realistic in our case.

riki added 1 commit

2026-04-02 16:32:19 +02:00