The road to 1b users isn’t shit logins that waste people’s warps. Too many times have I been burned with warps logins. I’m now skeptical anytime I see one. That doesn’t seem right.

The dev you do here matters. I believe in you all. Who has a warps login experience to help me overcome my doubts?

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

I’ve have several bad experiences:

1) I once payed and connected in the browser, and after clearing the cache, the token was lost and I had to pay to connect again (the devs did apologize but didn’t refund).

2) Most recent, I payed warps and when I returned to the app, the login screen spinner never stopped. The app warned that I was important to return within a 5min window. Despite immediately revisiting, nothing seemed to connect. The devs stopped talking to me. Warps lost.

can you elaborate on what you're referring to here? did you pay warps to connect and the transaction failed in Warpcast (and you never got the Warps back) or something else?

Making the blockchain invisible at /thirdweb

Good questions. I’m out of the loop here.

I like to think there is a reference implementation somewhere with robust error handling and a resolution strategy for when users aren’t granted access despite paying.

Worst case scenario: apps need to get much better at apologizing.

What would you say to someone building a client to solve this? What’s the preferred approach within the protocol’s constraints?

qDAU 🎩 track bike guy in 🇲🇽
✨⛰️🚲🏔️

photography ⛓️ http://obscura.io 🔴_🔴  /openventures /proxyswap

I don’t currently understand the details, but my instinct is that whoever took my warps owes me an on-chain action.

If I attempt an on-chain action and it fails, I am responsible for the gas fee. But I also get a txt record of my failure. I see my mistake: “I already minted”, etc.

When a warps login fails, wtf?

while i don't think it's the best either - since the login is a "signer" / on-chain contract approval (usually to some sort of client), there needs to be something to pay the txn fee. What would your proposed solution be other than WC paying those fees bundled in the initial storage fee somehow

pinata

Check out Photocaster.xyz, using sponsored signers via /pinata https://www.pinata.cloud/blog/how-to-add-farcaster-auth-to-next-js

It’s possible to build logins without warps / fee 🙂

It’s possible to build logins without warps / fee 🙂

https://docs.neynar.com/docs/how-to-let-users-connect-farcaster-accounts-with-write-access-for-free-using-sign-in-with-neynar-siwn