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 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
Each user has its own servers and channels. What is there to deduplicate?