Notification tokens and real-time socket infrastructure
By RepoJournal , from @bgrgndzz's public GitHub activity
Backfilled
Buğra Gündüz built out the notification and real-time messaging backbone for bloom across three commits, connecting the pieces needed to push updates to clients.
He set up the notification token register [1] to manage client subscriptions, then configured socket.io to use Redis as its adapter [2], allowing messages to fan out across multiple server instances. In the middle of this work, he added random sorting to the topics list [3], a UI feature to vary how topics are presented.
One email a day. Unsubscribe in one click.
A short briefing every day bgrgndzz ships something — in about 3 minutes.
One email a day. Unsubscribe in one click. Read a past issue →
References
- [1] setup notification token register bgrgndzz/bloom
- [2] connect socket.io to redis bgrgndzz/bloom
- [3] add random sorting for topics list bgrgndzz/bloom