The test relay in question is just allowing all kind 24133 after succesful auth. No whitelist checking. I ask because Amber v6.2.0-free is posting the following error when attempting the Add a option and manually adding the test relay: auth-required: you must authenticate before publishing events.

how does Amber handle setting up NIP-46 connections with a relay that requires NIP-42? For example, the relay has global auth policy but whitelists all kind 24133 events after auth.

When normies report stuff, they don't know the root cause. All they now is that Amber isn't working with some apps. In my case, I only raised the issue with you when I couldn't get Amber to NIP-46 connect to 3 different clients. Yes, could be a relay issue, but when each connection request comes with 3 different relays, normies start thinking about the common denominator.

This note is crashing

This is all that comes through on Amber

Can also add to the list. Just an eternal "Waiting for signer..." on connect attempt

Depends on what you want to do, but +1 for Prusa reliability

Yes, 6.1.0-free

nostr connect on Amber seems mostly broken. Just tried jumble.social and nostrudel.ninja. Both fail to connect even with multiple attempts.