By default amethyst uses tor for unknown relays (inbox/outbox relays from other people), try changing the privacy settings to basic

Sure, I can use my wife's ipad

https://github.com/greenart7c3/Nip46Lab I started building the nip 46 tester, claude 1 shot this. Will have a better look at it tomorrow or Monday Just run the html locally and test it with any bunker

In the permissions from the connect request you are sending get_pubic_key instead of get_public_key

Aegis on iOS, don't know what apps support it There's also primal but I haven't tested how it works on ios

Relay performance on android - Pixel 6a ~200k events added to the relay before the test Strfry 1.1.0 on android terminal: Published: 1000 Duration: 1.99s Rate: 501.63 events/s Executing 100 queries... Executed: 100 Duration: 25.61s Rate: 3.90 queries/s Events returned: 7800 Topaz: Published: 1000 Duration: 2.75s Rate: 363.42 events/s Executing 100 queries... Executed: 100 Duration: 20.81s Rate: 4.80 queries/s Events returned: 7800 Citrine: Published: 1000 Duration: 4.49s Rate: 222.80 events/s Executing 100 queries... Executed: 100 Duration: 13.80s Rate: 7.25 queries/s Events returned: 10000

No, it's only relays that accept bunker requests. Paid relays will not work, all others should work if they don't block ephemeral events. When you try to add a relay you will see a message if something is wrong or the relay don't accept bunker requests The profile relays can be the relays you use in other clients.

It looks like lnvps is not following the nip 46 spec, it should ask for the user pubkey after connect but it's not doing it https://github.com/nostr-protocol/nips/blob/0a25dd524389d642ec153d9009a16fb183eb23ce/46.md?plain=1#L34

You can disable the HDR brightness in display settings if thats your issue