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

solid.

could be nice to also think about

1. how a user pre-consents to have an API message land in their primary inbox vs. request inbox (e.g. opt-in to messages)

2. how a user elegantly moves an appreciated message from the "request inbox" into primary inbox