We also show notices and error messages the app receives when you click on the relay. Hope that helps. Let me know if I should add more info into it.  

 Yes it's workin' great! 

 nostrology/ lfg! 

 Here is a link to your event at your relay (for testing):

nostr:nevent1qqsv2zg6aephnyr6upm60v9tgm3hjzjdmks425mcj3c0erv9re00d9spzemhxue69uhkzat5dqhxummnw3erztnrdakj7qrq2tw 

 Lemme try that again (I got bugs on my side)

no nostr prefix this time

nevent1qqsv2zg6aephnyr6upm60v9tgm3hjzjdmks425mcj3c0erv9re00d9spzemhxue69uhkzat5dqhxummnw3erztnrdakj7qrq2tw 

 So a few questions.

I presume gossip tried, but it did not load this event from auth.nostr1.com.   It did find it from hotrightnow and nostr.wine.

Also, I presume gossip would have asked me for AUTH approval if it had tried auth.nostr1.com and been AUTH challenged. But I was not asked. So I think that means the relay neither auth-challenged me nor supplied the event. But that is a lot of presumptions, there may be a bug or two on my side. 

 I have kind one turned off on auth.nostr1.com right now.  It is only for DMs, groups based on giftwrap etc.  relay.tools does support this option though if someone wants a relay that does auth with kind one (or any kinds). 

 Oh that makes sense. Dumb assumption on my part. 

 All good, I believe I tested the auth with gossip and it worked for the kind ones.  I am working to make any and all options work.  It's quite the matrix of features 😂 

 I will add gossip to my test matrix tho when I circle back around to kind one nip42'ing just to make sure. 😎 I think nip42 with kind one would be awesome, esp in a client mode where the client uses a key to auth, and then multiple other keys to sign events.. so far I don't know of any clients doing that tho.  May have to write one. 

 I can also test DMs from gossip, even tho they're kind4 this auth relay in theory is helping only serve the DMs for that key that has authed.  (Protec) 

 They are kind 17 now too, on master branch, if you and your partner both have DM relays advertised. 

 Oh awesome!!! I will try this out for sure. 

 If you got a DM from me, then it works.  If you didn't, it might still have problems.  I get the 'cc' giftwrap back to myself, but that doesn't prove that the outbound giftwrap worked. 

 Hm, it doesn't appear to have worked (didn't receive in amethyst) 🤔 I will further debug with a new gossip setup while watching the logs.

I know I have one 'bug' currently on the relay, if a client sends more subsequent auths, after a connection is authed, the messages go to strfry and strfry will respond with unknown cmd notice.  Clients like amethyst and coracle ignore this, tho I would like to keep that from happening just more difficult than I thought.. other than that I haven't found any other bugs yet in the relay proxy. 

 One cool thing is amethyst seems to know you have a private DM relay.  Because it defaulted to nip17 and appears to have sent my test to your chorus relay, and to auth.nostr1.com.  Didn't receive your initial one tho. 

 I haven't seen any DMs from you.  I have giftwrap DMs from other people going back quite a long time even.

I've fixed enough bugs for today though, this one will have to wait for tomorrow. 

 GM ser!  I did some pretty extensive gossip nip17 testing this morning over coffee.  Here's what I found

https://gist.github.com/jeremyd/6274c83dca409ee548cfc1af518274c7 

 I fixed a bunch of problems with DMs this morning. I sent you another one from gossip (I sent you one from amethyst last night).  Did you get either of those?  I've gotten yours now, and the carbon-copies of mine. 

 I checked just now from amethyst, I am still not seeing any.. 🤔 

 ps; problem solving(solved) pow/ like it!