Thread - Nostr Hypermedia

Thank u for your insights from a user's perspective. However, from my perspective, I need to create a solution that is as universal as possible, since I cannot assume that the users of my PWA have a specific app like Keychat installed. My question is therefore aimed at finding out how I can best support the different standards (NIP-07/55/46) directly in the web app to ensure broad compatibility.

↑ Parent

Replies (2)

Dikaios1517 dikaios1517@nostrplebs.com 1 month ago

Keychat is just one of many options for NIP-07 signing. Alby, nos2x, and a couple others are out there, as well. NIP-07 is the most universally adopted signing standard for all Nostr web apps. If you are building a PWA, then order of priority would probably be NIP-07, then NIP-46, and finally NIP-55 since it is Android specific.

2 replies ↓

Dikaios1517 dikaios1517@nostrplebs.com 1 month ago

That order of priority changes drastically if you are building a native Android app, though. Then you'd better have NIP-55 working out the gate or go home. Add NIP-46 when you can get around to it, and no need to bother with NIP-07 since the app isn't operating in a browser.