Very simple spec for a first cut of programmable DCs. Plan is to basically expose a thin layer on top of internal Warpcast APIs. We don't know enough about the final shape of public DC APIs, so will keep it simple to start.

Very simple spec for a first cut of programmable DCs. Plan is to basically expose a thin layer on top of internal Warpcast APIs. We don't know enough about the final shape of public DC APIs, so will keep it simple to start.

https://warpcast.notion.site/Public-Draft-Programmable-DCs-v1-50d9d99e34ac4d10add55bd26a91804f

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

- how can I opt out if I'm too annoyed with the messages?

- how are messages/ webhooks secured?

- recommend adding some kind of tag + visual indicator to differentiate automated dcs vs human dcs

- would be nice to set an idempotency key in the request to avoid odd duplicates in the conversation

-

Risk @Stripe prev: wallets @bitski, search @airbnb | https://www.castsense.xyz/ 

good questions

1) there will be an opt in mechanism, still being designed but open to ideas
2) for now simple API keys
3) likely won't be there to start to KISS but am agreement that differentiation will be useful
4) good call, updated doc with idem key

Building @warpcast and @farcaster, new dad, like making food

Agree about KISS and late to this but 1000% agree with Shash about 3 (need for an indicator). Even just a little robot symbol 🤖. I can see the benefit of exposing an API for DCs but is so open to abuse (spam/scams) that need all the help we can get to tell people ‘this is automated’