Music

Tunecaster Update:

I’ve decided to roll back the notifications feature we launched three months ago. Though well-intentioned and functional, it saw little use and didn’t meet the quality standards we want for Tunecaster.

Instead, we’ll focus on mini-app notifications via the Farcaster app.

Thanks for understanding!

Tunecaster Update:

I’ve decided to roll back the notifications feature we launched three months ago. Though well-intentioned and functional, it saw little use and didn’t meet the quality standards we want for Tunecaster.

Instead, we’ll focus on mini-app notifications via the Farcaster app.

Thanks for understanding!

https://www.tunecaster.xyz

building farcaster infra @ /neynar 🪐 | casting @ /rish

The main issue was the polling-based architecture that used localStorage to store notification read status. We were making API calls every minute for each signed-in user to check for new notifications.

Other problems:

- Constant API calls even when there were no new notifications

- Too many spammy notifications made it through even with the x-neynar-experimental headers

- Client-side state management meant notification status was lost when users switched devices or browsers - no cross-device sync

I launched the mini-app 9 days ago and noticed a big spike in CU usage for /v2/farcaster/notifications/channel/ - hit 70% of my Neynar plan. Strange because mobile mini-app users can't sign in with Neynar, so the notification feature was completely hidden from non-authenticated users, and polling only started once someone signed in with their Farcaster account. Not sure what caused the spike, but regardless, this turned out not to be a very useful notification system.

Your cast has been curated by @ghostlinkz.eth

It was added to "Tunecaster Changelog" collection - https://deescuss.com/profile/ghostlinkz.eth/collections/6fe0c699-e2bb-408b-8eab-9f411a01be8b