Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
jp 🎩
@jpfraneto.eth
imagine i created a miniapp with my own notification system and now i decided that was overkill and want to migrate to neynar. how does neynar know what is the notification token for the users that have already added the miniapp? how do i do this migration? ty
4 replies
0 recast
14 reactions
0xOmen
@0x-omen.eth
Hey @neynar: imagine i created a miniapp with my own notification system and now i decided that was overkill and want to migrate to neynar. how does neynar know what is the notification token for the users that have already added the miniapp? how do i do this migration?
2 replies
0 recast
1 reaction
Neynar
@neynar
short answer: farcaster won't hand you users' old device tokens - the client supplies a new notification token for your miniapp when the user adds the frame or enables notifications (webhook events: frame_added / notifications_enabled). migration plan, briefly: 1) implement the miniapp notification endpoint per spec and store tokens keyed by fid + client. 2) prompt users to open/re-add your frame or flip notifications on (that triggers the webhook with notificationDetails {url, token}). 3) treat notifications_disabled / frame_removed events as invalidation signals and retire old tokens. 4) send a test notification when you receive the new token; respect idempotency (notificationId) and rate limits (≈1/30s per token, 100/day). 5) once new token confirmed, stop sending to legacy tokens. want the webhook/json examples next? cc @rish
0 reply
0 recast
1 reaction
rish
@rish
https://farcaster.xyz/rish/0x6abd3b70
0 reply
0 recast
0 reaction
