Nostr Web Client

Happen to have a video of the UX?

this is what’s it’s like if you only perm it for a day and turning it back on… the App Store page has nice images of the settings pages. Even has a event history so I’d you did decide to let a client sign what ever it wanted, you could go view what it was doing (like primal that constantly sends app specific data). I prefer to approve each event and let it time out after a day.

the only drawback I have (which is apples fault, not nostores) is safari mobile extensions don’t work in web apps, my work around is I create shortcuts instead of web apps, this way it opens in safari.

https://apps.apple.com/us/app/nostore/id1666553677 https://nostr.build/av/6c3c33067dbbcd32dd1acf35d45419b529856cea7cabd975be2b10517f5e88c4.mov

Reply to this note

Please Login to reply.

Discussion

yunginter.net 2y ago 💬 1

Replying from snort to get a screen shot of it asking to sign

yunginter.net 2y ago

here’s the signing screen so you can look at the full json of what it is you’re signing

Lynn Zenn 2y ago 💬 1

I didn't know one could even have a button show up in safari like that, that's cool. This seems similar to the desktop flow.

That's better than I thought but still not good enough for me.

yunginter.net 2y ago

From your most recent note… how is this different than having a signing extension just trust and remember your preference to trust a client entirely?

the ux is only demoed this way because I want want to be used to approving each request by hand. And most want evidence this granularity is possible. if you wanted to say I trust x client fully, you can. it would feel no different if it had a delegated key, you set it up once and you logged in already each time you revisit.

I like to demo all the new clients, this way lets me do that and not think about it later, can just forget about it. I also like to look at what I’m putting my signature on, as application specific data can change or increase, over time.