Description

Add a provider that supports auth and read/write capabilities using Neynar's @neynar/nodejs-sdk package and REST API.

Progress

• Currently working in Litecast(testing changes in an app before moving to the farcasterkit package)
  • Connect to Warpcast
  • Read feeds, threads, and user profile info
  • Post casts/reactions
• Up next
  • Extend hooks to provide all data necessary for Litecast(essentially feature parity with Neynar's APIs)
  • Test & move from Litecast directly to the farcasterkit package

For reference, here's the NeynarProvider file in Litecast

Description

Add components & hooks for signup and sign-in with an EOA. This will be compatible with(and come with examples for) Dynamic, Privy, and RainbowKit out of the box, with future support for embedded wallets to further improve the signup/sign-in UX.

Progress

• Signups are about ~90% done, you can see and read more about this integration's progress here
  • Need to fix an error I'm getting when calling the Bundler contract, then I can patch up styling and add the components/hooks to the farcasterkit package

Description

From my perspective, there are two main things that need to be fixed with the API:

• Standardize pathnames for routes built directly on the replicator(paths that expose tables from the replicator's DB directly)
• Upgrade API routes/schema to be more app ready, such as:
  • Including reactions in the cast object
  • Adding write functionalities

Changes to the API should not only offer routes to expose standard schema from the replicator, but also offer routes that are more app-ready, akin to the past Warpcast APIs.

Description

Migrate from the old replicator to Farcaster's new replicator

It's also worth keeping feat: Standardize and upgrade API routes in mind, since both this chore and that feature would require changes to API routes.