notifications

[kasumi-1]

subsquid:

• subsquid should index notifications so clients can easily listen for them
• should be address indexed with payload

website ui:

• reads from subsquid
• navbar:
• • show red bubble with number of notifications
• • on click open a small dropdown that shows last 4 notifications
• • provide a "mark all as read" button (mainly for people who use multiple devices)
• • scrolling infini load, until it reaches end and says "no more notifications"
• jobs tables:
• • show jobs with updates (e.g. worker open job gets a message, so in jobs table it is displayed at top of table with a red bubble)
• jobs page:
• • jobs chat threads should be ordered by notification (oldest unread notification should be on top)
• • show red bubble on chats list
• • highlight unread events and fade back to normal after a few seconds

web push notifications server:

• stores subscriptions using postgres (will use free hosted supabase)
• query the subsquid notifications
• typescript server with logging implementing vapid via web-push npm library
• subscribe route which user provide their eth public key
• admin routes to broadcast messages to everyone or to specific keys (such as for letting people know of an update, or for letting people know theyve received eacc rewards - these things do not need to be indexed otherwise)

web push notifications in client:

• redirect towards job thread if type is job related (we need payload design that allows either job/id, job/id/thread, job/id/thread/idx, page-on-site, no-page-pure-notification.. i think thats all)
• be able to decrypt.. however, all of our notifications except perhaps per user ones are public info anyways

[kasumi-1]

#83