I am curious how you think we should manage Warpcast authentication within Pipedream. Given we won't be rotating access tokens, it seems treating the App Bearer Token like a standard API key is the best path. Thoughts / feedback?

https://pipedream.com/apps/warpcast

Entrepreneur. Founder/CEO @Pipedream. Also #girldad, investor & lifelong learner.

this has been discussed in farcaster dev calls and in my opinion resolved - treat like normal api keys

I'd agree. If an OAuth model isn't going to be supported, it would be great if Warpcast would allow creating dev-only accounts to separate keys from profiles. (unless this is already a thing, I haven't dug into it yet!)