All authentications will be handle by extension across all web apps without exposing your keys anywhere and you will still have all the traditional login methods offered by specific app.

This seems like a right approach for now. 🤔

nostr:nevent1qqsxw8ejuyzuwu0vrcpugfwsp4umf3tqtnr8vr24xpa4sg0npy5ac5spz9mhxue69uhkummnw3ezuamfdejj7sr4dus

Reply to this note

Please Login to reply.

Discussion

Tell us more!

Currently, I am in the process of figuring out the login method for web apps on my upcoming dashboard. The extensions work flawlessly on all other platforms, but for iOS, it seems that an inbuilt extension may need to be created.

However, I am not entirely certain about this.

Would be cool if there was a way where you could scan a getalby qr (which is fantasy rn) from the PWA to give access for a limited amount of time

Not sure if that would even work, Just thinking out loud

I am not really sure about building inbuilt authentication because it defeats the purpose.

I think we need a overall better authentication mechanism on nostr. You should be able to create secondary keys with limited permissions.

Would this be doable with something like nostr wallet connect?

What do you mean all authentication handled by extensions? How does that work? Currently we have to paste in the private key. How is this different specifically?

I wonder if I have input my keys around too many clients, etc? Anyone plan to burn their account and start fresh with better security practices?

nostr:nevent1qqs9xaegcc9zakq6h6r9vgh45tlusr8tzdl6x8c4jvy4tzmvfyrz8wgpr9mhxue69uhhyetvv9ujumn0wd68ycmgv43kktndv5pzp3hhqal3dxw4pnuj49jjhl4lltq9l35y9w0w8yggnk2ehzk46j8aqvzqqqqqqyjvegcx