nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet 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.

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.

Reply to this note

Please Login to reply.

Discussion

No replies yet.