Nostr Web Client

Hey nostr:nprofile1qqsq36k72r04rkj2gt6acpz7xkehrypwqmt2spfpt0kr6ukudp7vkpqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpzpmhxue69uhkummnw3ezumt0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0v2l6t9 I think I found a bug? I can log in by connecting to #amber from the npub.pro domain, but if I am on vinney.npub.pro, amber just hangs on connecting.

Maybe the npub.pro sub domains should send their amber request as the top level domain? Or amber needs more granular domain detection? I don't know enough about either system to speculate.

Reply to this note

Please Login to reply.

Discussion

vinney...axkl 1y ago

CC nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck

Npub.pro 1y ago

I have just signed in with Amber, worked fine. Do you click on Amber icon to use it, or do you use bunker url or nostrconnect string?

vinney...axkl 1y ago

Clicked amber icon.

That DID work for me on npub.pro, but not vinney.npub.pro (and amber showed the subdomain when I attempted to approve it).

Maybe my internet was being dumb. I'll try again later