Ehi nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet I see you are working on the Rust Nostr library, I was playing around with it mostly for NIP46 and NIP65 stuff following the example codes on the repo and I was wondering: if I want to publish an event using the outbox model what do I need to do? Is there a method or option on the Client object to automatically publish the event on the outbox relays of the user or do I need to make sure to "client.add_relay(...)" for every outbox relay (taken from "Kind::RelayList" events) prior to sending the event?

Reply to this note

Please Login to reply.

Discussion

Hey, unfortunately is not available on rust-nostr yet. I was working on it but not finished yet. I hope to complete it soon!

Sorry to bother you again, but is there a way with nostr-sdk to save the state of the client and/or signer/bunker in the localstorage of the web app that is running everything? Or is this outside of the scope of the crate and therefore needs to be achieved by the framework in use? I am trying something with Dioxus Web but apparently the Client and NostrConnectURI types doesn't support serialization.

I am still a beginner with Rust, so I might say stupid and incorrect things.

No, it not support that. Only received events are persistent if you are using indexeddb.

NostrConnectURI not support de/serialization with serde but you can use the `.to_string()` method to serialize it as str and `NostrConnectURI::parse` to parse it.

Thank you, that was very helpful for me.