A place for developers to talk about building on Farcaster.

/dev

if you were just starting out building on farcaster, what sorts of developer resources would you want to see? some things that are on my mind:
- what is farcaster/why should i start building on it?
- mini apps and the power of their distribution
- vibe coding a farcaster app
- apis and infrastructure providers you can use

would really appreciate any comments in this thread whether you're already a dev and these resources would've helped past you, or if you'd benefit from these resources rn!

engineer @base | /farhack /tap /cortex | dylansteck.com

Why api.warpcast.com is not CORS enabled when in docs it says is public and it has so much data that is not on protocol like:

- mute
- blocks
- channels metadata( admins, info description registration etc)
- mini app metada
- DMs
- warpcast specific notifications
- mini app analytics
- warpcast rewards
- proprietary feeds

And probably much more that I didn't specified here.

Software developer, open source enthusiast, privacy advocate.

Clear Wallet Open-source privacy focused wallet: https://clear-wallet.flashsoft.eu/


Building @warpcast and @farcaster / dad / like to read, cook, ski, code

I find it pretty useful. 

There are scenarios, even like checking a specific channel feed, I mean, all that data is already accessible, but you would need an additional proxy, in cases where CORS would eliminate that need, especially like in docs, you have authentication over API with a signer key, but there are scenarios when you can do that authentification safely on browser level (example the signer key is owned by that user that is authentificated so is safe to share it with him)

I didn't find any dev that would not find this useful, like I said, not all data is on the protocol getting a channel picture, name, or description from the browser is useful.

Getting the apps I added to favorites on warpcast, also useful.

BTW, I see now that warpcast.com does correct code splitting, from the beginning to a few weeks ago, at least it just compiled everything into a huge main JavaScript asset.

mini app metadata is served by mini apps not warpcast so that anyone can scrape that data

not sure what mini app analytics you’re referring to

the others APIs are primarily built for efficiently syncing rather than serving views which are generally fast evolving and opinionated based on specific applications needs

that being said if there are devs asking for CORS headers it seems like something we could accommodate