Oddbean new post about | logout
 @PABLOF7z @Don't ₿elieve the Hype 🦊 @Yuki Kishimoto if I have questions about nostr_sdk bindings for python, is there a chat / telegram / etc where people hang out? 

I'm trying to figure out what client.get_events_of() does, specifically what the timeout does. 

I'd also be willing to contribute to documentation for the python bindings. 
 Did you read the source yet? 
 my rust is rusty 😇  
 I did pass part of the source code through an LLM and it guessed that the timeout is being used for how long to listen for events, rather than the window of time in which events were published. 
 I believe it's to wait a small period to time to batch filters together in one REQ if you're making a lot of subscriptions. 
 Would relays be kicking me off or just decide to stop responding if I'm subscribed for too long? Is there any way I could detect that if it happens?

I should say that what I'm trying to do is run a python program that forever listens for DVM related events. I've been using a version of nostr_client() from here: https://github.com/believethehype/nostrdvm/blob/main/tests/test_dvm_client.py 

It does look like this has been updated since I last started using it, maybe I should adapt this most recent code.  
 `client.get_events_of` it's basically an auto-closing subscription: subscribe, listen until EOSE or when timeout is reached, close subscription and return events.

To subscribe "forever", just use the `client. subscribe` method. All the events will be sent to a notification channel. You can find an example here: 

https://github.com/rust-nostr/nostr/blob/master/bindings%2Fnostr-sdk-ffi%2Fbindings-python%2Fexamples%2Fbot.py 
 Thank you I’ll check that out 
 For now I created a Matrix space: https://matrix.to/#/#rustnostr:matrix.org

I prefer to avoid Telegram, Discord and so on.

If there is a good alternative to Matrix spaces here on nostr, with a desktop/web client, we can move there. 
 https://blowater.app/ seem good choice 
 Thanks! I'll check it