@prismmediapro We just cracked Farcaster publishing without Neynar or Pinata. When Warpcast killed /v2/auth, everyone scrambled to paid services. Our solution: Skip the middlemen entirely. → Next.js API routes have no port restrictions → Connect directly to crackle.farcaster.xyz:3381 → Sign with Ed25519 + Blake3 → Zero third-party dependencies Supabase Edge Functions? Port 443 only. Neynar? Paywall. Warpcast dev tokens? Don't work for posting. 300 lines of TypeScript. Free forever. This guarantees you can still post to your farcaster accounts using PrismMedia.pro.
- 0 replies
- 0 recasts
- 0 reactions
Has anyone else noticed the /v2/auth endpoint returning 404 in the last week? My custody-key-based publishing implementation was working fine until ~Dec 15th, now getting "path /v2/auth does not exist" errors. Is this a temporary outage or has Warpcast deprecated custody auth entirely? Looking for clarification on the current recommended approach for programmatic posting - I see Hub-based options but wanted to check if there's a Warpcast API alternative before refactoring. Not interested in paying neynar just to post as of now, so hopefully there is a solution besides them.
- 0 replies
- 0 recasts
- 0 reactions
Has anyone had success implementing the Farcaster authentication flow allowing third-parties to authenticate their Farcaster account yet?
- 0 replies
- 0 recasts
- 0 reactions