Great! Let me know if you hit any issues. Note that AUTH will currently only be triggered if you try to send a protected event to the relay. We're trying to decide on the best way to extend this functionality (any comments/suggestions welcome).

Thanks! For now none at all, but I take the opportunity to ask a maybe silly question. For auth I saw the new options 'enabled' and 'serviceUrl'. I saw a bit about nip42 and I understand there I gotta use my ws://address.onion (last slash? /)

Correct, yes, it should be the relay URL that external users use. I believe no trailing slash. We should probably normalise the URL so it accepts both, I added a ticket for this:

GitHub

Normalise serviceUrl in AUTH flow · Issue #182 · hoytech/strfry

In the AUTH flow, right now it verifies that the relay URL exactly matches. NIP-42 says just checking domain is sufficient. At least we should remo...