How about to create two different ones in Minibits and try out?
#asknostr
Does anyone know how to connect nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59u4kl3vp to nostr:nprofile1qqsfy7f8d0lms08wxw2xu4jvxcq2x2zqy6dgypksrh05p3jr9w4qhjcpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcgnazkh via NWC?
Stacker News is asking for separate connection strings for sending and receiving, and I'm just not seeing that distinction when I create a connection strings in Minibits...
Discussion
Hmm. Worth a shot.
Ok, so that didn't work, but I did find a workaround.
I just took the connection string from Minibits, entered it in the "Connection for Sending" field on Stacker News, then added my Minibits LN address as a receive option.
Couldn't get the string to work in their "Receive field, but since I can use the LN address as a different option for receiving zaps, it all works out.
nostr:naddr1qqrrwvej8qursq3qvgldyxx7syc30qm9v7padnnfpdfp4zwymsyl9ztzuklaf7j5jfysxpqqqp65wxtf6ns