Farcaster Developer Calls

Hub Performance, Storage Updates, and SIWF Changes

on

Aug 15, 2024

by

dylsteck.eth

TLDR

Hubble's node count cut from 13k to 10k, with further reductions planned. Alchemy targeting free hubs, mainly airdrop farmers. Hub divergence fixes in progress. Warpcast sync status stable for 7+ days. Storage reduction paused to explore options. Composer actions expanding beyond initial set, now on web. NUX updates include a recommendation algorithm for feeds and improved signup flow. Spam detection enhanced. DC performance and feature improvements ongoing.

Message Broadcasting

  • Issues with job broadcasting at status.warpcast.com.

  • Sync issues between Neynar and Warpcast — working on shuttle improvements for migration.

  • Hub performance problems — gRPC timeouts, long write times on Warpcast hubs under heavy load.

Storage Extension

  • FIP: Storage Extension — github.com/farcasterxyz

  • Goal: Make it easier for users to stay on FC.

  • Increasing storage duration for all existing users by 1 year.

  • Reducing size of new storage units going forward.

  • Rollout soon — no impact on existing users or devs, hubs need to upgrade.

Sign In with Farcaster — cc @dwr.eth and @horsefacts.eth

  • Positive feedback, but focused on reliability issues for 10-15% who can't scan QR codes.

  • Want to improve reliability before expanding (e.g., support for other wallets like Supercast).

  • Small changes: shortened SIWF URL and channel tokens to simplify the QR code process.

Explore Page

  • Aiming to make it easier for developers to get users, collecting data for future improvements.

  • Potential to add features, such as logging users into the app directly.

Feed Improvements

  • Working on how feed construction changes based on user activity and follows.

  • Experimenting with boosting underrepresented content.

  • Deprecating power badge by end of August, finding better systems for priority notifications.

  • Neynar continues to run a power badge API.

DC Improvements

  • Ongoing performance and feature enhancements.

  • Stability improvements first, then focus on APIs and interoperability.