Well, as long as the app is satisfied with blanket reject for all nip44 encrypt/decrypt, I can settle for that. Wisp seems to function ok in this mode (eg. DMs turned off). Unsure about amethyst. Curious what @Vitor Pamplona thinks. Are we too cypherpunk?

:claudemax: :thisisfine:

I have negentropy enabled on all relays including the NIP42-Auth DM ones. I am curious if it works well with AUTH mixed in, but I have to implement it in my DM testing client to find out, since no one else I know of has..

i worry that @greenart7c3 needs some help with manual amber.. from you guys. I see utxo has given up already, supporting it (maybe jokingly, but users told to accept all). And amethyst still is broken as well. Mostly when using DMs is what I see. I really think this is important and I love seeing what I'm signing and approve for time window etc.. Is this an unsolvable problem because of android architecture or is it just that more integration testing and fixing is required?

this one from wisp, landed on nostr21 it looks like

It's also possible that if you are on a slow connection, amethyst will starve your devices connection pool (not related to the relay). I noticed this when testing amethyst on a slow connection it could not send a message to save it's life, due to how much connection cycling it was doing in the background. Then I used a faster connection and this problem went away.

So, maybe try other clients.. See if the relay still has problems responding (like jumble or..?)

it does look like the relay is under heavy connection storm.. for a while now. I'll keep looking to see if I can tame it down. It does still respond ok, in my testing but.. Yeah it is hard to say.

cool, post some stuff about lifting the nostr ban

true if big ♥️

corny uses thebarn.nostr1.com relay if that halps 🐳🐳🏝️

can't believe that was a haiku 😂😂😂