Have you revisited the nostr:nprofile1qqszm52qe2qdkc4u7dma0klx3532jka2g8geck6fwxncyp90wktq2xspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmhv4kxxmmdv5hxummnw3ezuamfdejsw8afg2 connection between nostr:npub1s4m06xdlu6fuhfhs4m3nhpp8xdpsdprwccdktckkzusfu8qzzprqnfpz6a and your favorite nostr client, nostr:nprofile1qqsp9msr6ytgfgf9mkrmapuu9qvsg9d78ua3ajntfmt580t5llvgpespz9mhxue69uhkummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctc2helt0?
I doubt the error is caused by nostr:npub1s4m06xdlu6fuhfhs4m3nhpp8xdpsdprwccdktckkzusfu8qzzprqnfpz6a, or what do you say, nostr:nprofile1qqsdmup6e2z6mcpeue6z6kl08he49hcen5xnrc3tnpvw0mdgtjemh0spz3mhxue69uhhyetvv9ujumn0wd68ytnzvuqjyamnwvaz7tmwdaehgu3dwejhy6txd9jkgtnhv4kxcmmjv3jhytnwv46qmammld?


