Database support and deduplication #754

Closed
opened 2026-10-05 04:42:49 +02:00 by adam · 1 comment
Owner

Rather than storing each user's backlog separately, it'd be cool if it all went into a database with deduplication. This would reduce storage requirements, allowing a larger number of users (or a longer backlog) on the same server/bouncer.

Rather than storing each user's backlog separately, it'd be cool if it all went into a database with deduplication. This would reduce storage requirements, allowing a larger number of users (or a longer backlog) on the same server/bouncer. <!-- github-sync-id:203824329 -->
adam closed this issue 2026-10-05 04:42:49 +02:00
Author
Owner

Each user has its own servers and channels. What is there to deduplicate?

Each user has its own servers and channels. What is there to deduplicate? <!-- github-comment-id:275879077 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#754