Oddbean new post about login | logout Try to move the `client.subscribe` code and filter in the `process_reminder_notifications` func, between the `let mut notifications = client.notifications();` and `info!("listening for notifications");`
I'll give that a shot here in a bit. what are you thinking the issue might be?
so nostr:nprofile1qy28wumn8ghj7un9d3shjctzd3jjummjvuhszymhwden5te0wp6hyurvv4cxzeewv4ej7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3jamnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kz7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshsqgrgmqgktyvpqzma5slu9rmarlqj24zxdcg3tzrtneamxfhktmzzwgaa0eg5 it looks like putting the subscribe after the notification receiver creation appears to be the key i needed. i appreciate the help.
When you call the 'notifications' method, you subscribe to the notification channel from that precise moment. Anything sent before that moment is not included in the channel. In the code you were subscribing to the relays very early and then you were sending the metadata event (if one of the relays is offline it may take some seconds to continue). Therefore, when the `notifications` method was finally called, it's likely that the events had already been received (but not included in the notification channel). --- I'll update the documentation of the "notifications" method.
ahh good call. classic race condition. well that makes alot of sense. thanks for the help!