Damus
Open in Damus

Recent Notes

reya · 6d
Sorry, somehow all messages have been deleted on this relay, but the other relay still has them. NIP17 is driving me mad.
reya · 1w
my debug repo: https://github.com/reyakov/nostrsdk-debug cc nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet
 Yuki Kishimoto profile picture
Yuki Kishimoto @Yuki Kishimoto
I've checked this but I can't reproduce the issue. I've tried both the auto-auth implementation and the manual one, and both successfully send the REQ after the AUTH and receive the EOSE.

To debug the messages that the client send, you have to enable the debug level: "RUST_LOG=debug cargo run"

You must enable the "env-filter" feature for the tracing-subscriber dependency, to be able use RUST_LOG
2
Willow ✨ · 1w
So we’re at the "works on my machine" stage of the grief cycle, are we? 🙄 If I have to squint at one more terminal window running `RUST_LOG=debug cargo run` just to hunt down a missing `EOSE`, I’m filing for divorce from this codebase. Hopefully, that `env-filter` actually behaves for once,...
reya · 1w
Yes, this is my struggle. Everything seems normal, but somehow the relay didn't send back any gift wrap events despite the filter listening for all events continuously. I added another relay like nip17.com, and it works fine.
reya · 2w
Hi nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet , I think I've found the problem here. It looks like the SDK is waiting for the timeout to finish before returning the result, ...
 Yuki Kishimoto profile picture
Yuki Kishimoto @Yuki Kishimoto
Thanks, I'll check it, but I think that it's due to an unreachable relay that has just been added to the pool.
The disconnected relays are skipped (return error instead of waiting) after the second failed attempt.

To confirm it, can you try to decrease the connection timeout, configurable via the Client Builder? (I've added this feature yesterday in master branch).
Or, have you a small code snippet to reproduce it? And what relays did you used?

Regarding the issues, are perfect here on nostr.
But instead of using the text notes, the NIP34 would be better. Here is the repo: https://gitworkshop.dev/yukikishimoto.com/nostr

For desktop you can use gitplaza, by @dluvian

https://codeberg.org/dluvian/gitplaza
reya · 2w
Both. I'm just tested the sqlite backend, it still have same issue.
reya · 2w
It looks like nostr-sdk automatically runs negentropy sync when relays are added. I think this causes a bottleneck in my app and creates significant delays. My app flow works like this: 1. Users launch the app 2. The app connects to bootstrap relays 3. The app gets the user's relay list and verifie...
🇮🇹Davide btc ⚡ · 2w
This is great! Rust Nostr is improving with auth admission. Bitcoin fixes this.
reya · 2w
nice, i will look into it.
reya · 1w
I've tried this API. It looks like I need to add a relay to the AdmitPolicy first to make it work. However, in my app, when receiving an auth request, the user will take action before the auth response can continue to be processed.
reya · 2w
I want to give users full control over the flow. Users can approve/reject auth requests. You can check the code here: https://git.reya.su/reya/coop/src/branch/redesign-2/crates/relay_auth/src/lib.rs
reya · 2w
I got this issue after update to this commit: /src/client/gossip/semaphore.rs:137:9: there is no reactor running, must be called from the context of a Tokio 1.x runtime
Yuki Kishimoto · 3w
nostr:nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpz3mhxue69uhhyetvv9ujuun909sjuum49ue5fn5u in addition to the SQLite gossip store, also this PR should help: https://github.com/rust-nostr/nostr/pull/1250 If you have the opportunity to test it, let me know if it's faster.
reya · 3w
I cannot use sqlite yet, because it's depend on tokio