X.KOJIRA.IO
Timeline

Yuki Kishimoto

[email protected]
npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet
GitHub: https://github.com/yukibtc
PGP: 86F3 105A DFA8 AB58 7268 DCD7 8D3D CD04 2496 19D1
A security update is available for anyone using `negentropy` by NostrDevKit.

Please update to v0.4.4 or v0.5.2

https://github.com/nostrdevkit/negentropy/security/adviso…

Thanks to nprofile1qqsqgc0uh… for finding and fixing the vulnerability.

#nostrdevkit #rustnostr #rust
As per NIP-59, the rumor should use the current timestamp, while the other timestamps should be tweaked: https://github.com/nostr-protocol/nips/blob/2ab507db107d0…

But yeah, I can add that option.
Some of the APIs were not designed as well as they should have been. We’re redesigning and refining them with v1.0 in mind (no ETA yet)
I just took a quick look, and I think the problem is that the relays being added with NONE capabilites. This means they can't do anything (neither read nor write).

Unless you want to use specific capabilities, you can omit that argument in addRelay, so they will be added with the default capabilities (READ + WRITE).
Have you a small example to reproduce it?
I've already adapted FFI APIs but not released anything yet. There are still a some things to rework before the next release.

I think if you fork the repo, you should be able to run the workflow for building them by yourself:

Fork the repo -> Go to "Actions" -> Select the "Publish" workflow -> Click on "Run workflow" -> Select the commit to use, deselect everything except "Build KMP" (the "Swift package version" can be empty) and DON'T select "Publish" -> Run it and you'll find the AAR in the artifacts (called nostr-sdk-ffi-kmp-aar).

Compilation can be done also locally, but unfortunately requires macos as it needs binaries also for iOS, and I didn't found a way to cross-compile them from Linux.

https://github.com/rust-nostr/nostr-sdk-ffi/commit/72c07c…
I've published a NIP-17 event with the key in the nostrsdk-debug repo, and now REQ receives that event from auth.nostr1.com

So there were probably no events published for that key on that relay
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
The URL in the AdmitPolicy is to let you know from with relay the AUTH request is coming.
You don't have to add it, it's added by the SDK.
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 nprofile1qqswgvmv6…

https://codeberg.org/dluvian/gitplaza
Does this happen with the in-memory gossip store, or with the SQLite one? Or both?
Yes, I've starter working on it a couple of days ago. The PR: https://github.com/rust-nostr/nostr/pull/1252

I'm working on making all the libraries runtime-agnostic. Hope to have a PR ready soon.
Ahh, with the AdmitPolicy::admit_auth is possible handle the approve/reject flow while using the SDK impl: https://github.com/rust-nostr/nostr/pull/1218
Out of curiosity, why are you manually handling auth requests? Are there issues with the SDK implementation?
nprofile1qqspycgrh… 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.
No, clone doesn't affect that, it's fine to use it. Have you tried the SQLite gossip storage, instead of the in-memory one?
The new SDK APIs are now available in the master branch, for those interested in trying them out!

https://github.com/rust-nostr/nostr

nevent1qqsq9ee8s8w…
This time I just merged them 😂, those are nprofile1qqsqqqqqq… 's work

I've removed it here: https://github.com/rust-nostr/nostr/commit/c2442d87da7ec5…

At the moment, I think there are other things more important to focus on. We'll see if re-add it in the future, after the beta or release stage.

Otherwise, if someone is interested in building a nostr-sdk extension library, could add it there.
Nostr SDK bindings for Kotlin Multiplatform are out for testing!

Package: "org.rust-nostr.org:nostr-sdk-kmp:0.44.0-SNAPSHOT"

Support the following targets: Android (x86, armv7, x86_64, aarch64), iOS (aarch64 and x86_64), Linux (GLIBC and MUSL; x86, x86_64, armv7, aarch64 and riscv64), FreeBSD (only x86_64), macos (x86_64 and aarch64) and windows (x86, x86_64 and aarch64).

#rust-nostr #rustnostr #rust #kotlin #kmp #ffi
Thanks, I've released it ad patch (v0.43.1)
Here you can find some docs/examples: https://rust-nostr.org/
It shouldn't be related to the SDK, error 403 means that the server is blocking you
Unfortunately in bindings I can't mark a function as deprecated.

You have to use the NostrParser and then construct the tags. In this way you can extract only the stuff you need from the text
older →