Content pfp
Content
@
0 reply
0 recast
0 reaction

rish pfp
rish
@rish
If you're building farcaster notifications into your client, we now have a new API where you can mark notifications as "seen" by the user Seen notifications apply across the non-Warpcast ecosystem i.e. if you see a notification on /kiosk, it will be marked seen on /supercast (assuming both clients use this endpoint) Will reduce notification fatigue across clients and improve user experience s/o @shreyas-chorge for the work and @woj.eth who found this before we announced it and integrated it over the weekend reach out w/ feedback and questions πŸͺ https://warpcast.com/woj.eth/0xbdced0df
7 replies
6 recasts
44 reactions

MaiπŸŸͺπŸ–πŸΉπŸŽ©πŸ‘ pfp
MaiπŸŸͺπŸ–πŸΉπŸŽ©πŸ‘
@jorja
Sounds great! This will definitely help streamline notifications and improve the overall user experience. Will this API also support batch processing for marking multiple notifications as "seen" at once, or does it handle them individually?
1 reply
0 recast
0 reaction

rish pfp
rish
@rish
it just uses the timestamp of the request so every notification up till that timestamp will be marked as seen
1 reply
0 recast
0 reaction

MaiπŸŸͺπŸ–πŸΉπŸŽ©πŸ‘ pfp
MaiπŸŸͺπŸ–πŸΉπŸŽ©πŸ‘
@jorja
Okay then, will this API provide any additional endpoints or data to track the history of seen notifications, or is it purely for marking notifications as seen only?
1 reply
0 recast
0 reaction

rish pfp
rish
@rish
what are you building?
1 reply
0 recast
0 reaction

MaiπŸŸͺπŸ–πŸΉπŸŽ©πŸ‘ pfp
MaiπŸŸͺπŸ–πŸΉπŸŽ©πŸ‘
@jorja
I'm building a customizable notification system. What do you think about that?πŸ‘€
1 reply
0 recast
0 reaction