He quit nostr lol 

 Really lol? 

 Yeah, but it wasn't just because of ditto.  He was having trouble with his nostrudel fork and the general decline in users and interaction here.   

 Oh geez 

 Oh geez 

 Yeah, the bridge is a bit flaky too and if you add momostr you end up double posting and theres a weird thing where posts end up getting reposted into nostr on another npub 

 There is definitely something wrong. But I'm not sure what yet. https://grafana.soapbox.pub/dashboard/snapshot/iqYQUQANVMBjuI6iRcWH3GxdLFI4Uhvs 

 Let's fix this. I'll video call to get to the bottom of it if we have to. This issue has disturbed me ever since, but I cannot reproduce it. 

 Also can you check if the same problem occurs on another Ditto instance? ditto.pub gleasonator.dev cobrafuma.com 

 Also can you check if the same problem occurs on another Ditto instance? ditto.pub gleasonator.dev cobrafuma.com 

 Thank you. I know which part of the code is failing here, but I don't know why yet. 

 I couldn't reproduce in FireFox. Maybe tomorrow you can also screenshot the JS console. Here is everything looking fine.

https://image.nostr.build/4282de46608e03707516a5ed4038de466cb68a3b9c6daa454b6f70b5ac0c4760.png 

 I couldn't reproduce in FireFox. Maybe tomorrow you can also screenshot the JS console. Here is everything looking fine.

https://image.nostr.build/4282de46608e03707516a5ed4038de466cb68a3b9c6daa454b6f70b5ac0c4760.png 

 This is really helpful, thank you for your assistance. I need just a little bit more information.

First let me explain what's supposed to happen. Ditto logs you in with the "Remote Signer"  specification. Soapbox implements a Remote Signer. For you to log in, both Soapbox and Ditto must connect to Ditto's relay and send messages to each other.

So, please open the Network tab of your inspector, and filter it by "WS". Then refresh the page.

You should see a request for "relay". Click on that, then click on "Response" in the right sidebar. At first it will be empty.

Now try to log in. Do messages appear in the right pane, like shown here? Or is there even a request to the "relay" at all?

https://image.nostr.build/eec276cc591189747f347eaaa524a9eecd17bcebc9b5ec1e502048f938b7c17b.png 

 Oh man, that is so odd. 

 In this screenshot, are your console logs the same as before? The extension is just asking for getPublicKey?  

 I'm going through the code right now and thinking it through 

 It makes no sense to me. Ditto is waiting for your client to respond, but your client already responded. If there was an error, it should have thrown an error in Ditto, but it didn't. I'm going to set up FireFox nightly to see if I can reproduce it there. 

 It makes no sense to me. Ditto is waiting for your client to respond, but your client already responded. If there was an error, it should have thrown an error in Ditto, but it didn't. I'm going to set up FireFox nightly to see if I can reproduce it there. 

 It could somehow be Soapbox or Ditto that's the problem. But it makes no sense that it works perfectly on one machine every time, and never works on the other machine. 

 I deployed a custom build of Soapbox with extra logging to gleasonator.dev. Can you please try logging in there?

https://image.nostr.build/f0e05fb63c7f411d7bae20e73c9c17e8cffcc86b954bc6b02b603e85366ebfd5.png 

 I deployed a custom build of Soapbox with extra logging to gleasonator.dev. Can you please try logging in there?

https://image.nostr.build/f0e05fb63c7f411d7bae20e73c9c17e8cffcc86b954bc6b02b603e85366ebfd5.png 

 Thank you, I can investigate this more now. Be back in 30 mins... 

 Do you still have this open? Could you send the full json of this response event?

https://image.nostr.build/97ca7e53dd37675645e4856237d8765ab40c244529067e6a0efc61bd61620e38.png 

 That's the request. I need the response.

Apparently the response didn't get sent through the relay at all. So I'm narrowing down the issue. 

 Yep, then maybe we can upgrade to Telegram or Signal from there. 

 Okay, I'll DM you on Fedi