Yuki Kishimoto

## rust-nostr v0.40 is out! 🦀
### Summary
Add NIP-38 and NIP-62 support, add nostr parser, to easily parse any text and extract nostr URIs, URLs and more, extend `Tags` capabilities (i.e., add deduplication support), add admission policy, to selectively select which events to allow receiving and which to reject, add Mac Catalyst support for Swift package, many cleanups, refactoring and performance improvements and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1aha…45hy
* @nprofile…g0ly
* @npub1zfs…w445
* @npub16ye…g4wn
* magine
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2025-02-08 07:49:43

- reply

I have never been very active in discussions but working on rust-nostr (at the time called nostr-rs-sdk) since September 2022 🦀
If I remember correctly there were also @nprofile…njvk and @nprofile…nq40

2025-01-27 14:18:51

#rustnostr #nostr #kotlin #jvm
#nevent1q…phku

2025-01-27 14:16:53

It's now available a pre-release of the nostr-sdk library for Kotlin JVM (linux, macos and windows)!
```kotlin
implementation("org.rust-nostr:nostr-sdk-jvm:0.39.0-alpha.1")
```
https://central.sonatype.com/artifact/org.rust-nostr/nostr-sdk-jvm

2025-01-20 13:16:39

- reply

How? :)

2025-01-20 12:44:17

Does anyone know if it's possible to cross-compile rust from Linux to iOS targets?
#rustlang #ios #asknostr

2025-01-20 09:06:14

- reply

@npub1acg…p35c, I'm trying with this example:
```toml
[dependencies]
nostr-sdk = { version = "0.38", features = ["lmdb"] }
tokio = { version = "1.42", features = ["full"] }
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
```
```rust
use nostr_sdk::prelude::*;
#[tokio::main]
async fn main() -> Result<()> {
tracing_subscriber::fmt::init();
let keys = Keys::parse("nsec1ufnus6pju578ste3v90xd5m2decpuzpql2295m3sknqcjzyys9ls0qlc85")?;
let database = NostrLMDB::open("./db/nostr-lmdb")?;
let client: Client = ClientBuilder::default()
.signer(keys.clone())
.database(database)
.build();
client.add_relay("wss://chorus.mikedilger.com:444").await?;
client.connect().await;
let since = Timestamp::from_secs(1736726400);
let until = Timestamp::from_secs(1737331200);
let filter = Filter::new().kind(Kind::TextNote).since(since).until(until); // Sync the text notes of the last week
// Negentropy options
let (tx, mut rx) = SyncProgress::channel();
let opts = SyncOptions::default().progress(tx);
// Keep track of the progress
tokio::spawn(async move {
while rx.changed().await.is_ok() {
let progress = *rx.borrow_and_update();
if progress.total > 0 {
println!("{:.2}%", progress.percentage() * 100.0);
}
}
});
// Sync
let output = client.sync(filter, &opts).await?;
// Sync output
println!("Local: {}", output.local.len());
println!("Remote: {}", output.remote.len());
println!("Sent: {}", output.sent.len());
println!("Received: {}", output.received.len());
println!("Failures:");
for (url, map) in output.send_failures.iter() {
println!("* '{url}':");
for (id, e) in map.iter() {
println!(" - {id}: {e}");
}
}
Ok(())
}
```

2025-01-20 08:57:50

- reply

I receive an error when I try to connect: "peer closed connection without sending TLS close_notify"

2025-01-19 23:07:42

- reply

The steps looks good. I'll test it soon. Is the new code with negentropy already public?

2025-01-16 09:59:07

- reply

Unlike the REQs, the negentropy messages can take only one filter, so it may be useful in some case to allow multiple sync at the same time. But it's also true that sync can be executed in sequence, like I'm doing with `Relay::sync_multi`: https://github.com/rust-nostr/nostr/blob/e4dbf484a8d1e57a05f0cc0312dd52c6c43cddd5/crates/nostr-relay-pool/src/relay/inner.rs#L1776
Here I use the `sync_multi`: https://github.com/rust-nostr/nostr/blob/e4dbf484a8d1e57a05f0cc0312dd52c6c43cddd5/crates/nostr-sdk/src/client/mod.rs#L1850

2025-01-14 22:25:05

- reply

Would be nice to have negentropy support in chorus.
If it helps, here's how I implemented it for nostr-relay-builder: https://github.com/rust-nostr/nostr/blob/25a76ff3d90ea4307dd1078ccc2b910619571971/crates/nostr-relay-builder/src/local/inner.rs#L614

2025-01-03 15:13:08

- reply

I'm adding support for transactional queries to the nostr-database traits 👀
This will allow to have **almost** the same performance as using nostrdb directly, even when used from the nostr-sdk.
https://image.nostr.build/d08c2c808fb0842d0f0fe91d56b5cc548ba95d76d630190db5b741c885f2fe7d.jpg

2024-12-31 20:37:14

- reply

In the book, for now only the "hello, rust-nostr" example is available. But if you are already familiar with the python bindings, the APIs are the same.
For now only keys parsing/generation/serialization, event de/serialization, event building and the client with some methods (add relays, connect and send event) are available. I'll add event fetching and subscriptions soon

2024-12-31 12:39:52

- reply

🧡

2024-12-31 12:38:15

- reply

Missed to mention @nprofile…wz3u as code contributor. Thank you!

2024-12-31 11:38:32

## rust-nostr v0.38 is out! 🦀
### Summary
Full NIP42 support for SDK and relay builder, negentropy support and read/write policy plugins for relay builder, NIP35 support, better logs and docs, performance improvements, bugs fix and more!
The Flutter bindings are finally fixed and usable (not for web yet), although rather incomplete compared to other languages.
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors for this relays!
* @npub1xj5…5s8g
* @npub1use…k5ks
* ethicnology
* @npub1zuu…c2uc
* @npub1v0l…qj49
* @npub1aha…45hy
A big thank you also to those who contributed throughout 2024 (in addition to the above-listed):
* @npub1k95…s3z7
* @npub1f5u…jmug
* @npub1u8l…turz
* @npub15qy…yejr
* @npub138h…rdr2
* @npub1lu2…xlm6
* @npub163j…qdc2
* nanikamado
* @npub1zwn…fhrf
* @npub1zfs…w445
* @npub1w80…zqjv
* @npub1zk6…l6ef
* @npub1mhe…qtf9
* @npub17q5…6f2y
* @npub1acx…gj3j
* @npub1q0u…9py9
Thank you very much also to all the donors! Special thanks to @npub10pe…n34f for the LTS grant, to @npub1ktt…yhz0 for subscribing and being a recurring donor and to @npub16p8…fhdw to be the top-donor of 2024.
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2024-12-24 09:43:41

- reply

Wow, thank you very much 🧡

2024-12-24 08:34:08

- reply

Ah, just tried, I receive an invalid invoice.
Seems a problem of @nprofile…r4s5

2024-12-24 08:30:11

- reply

Are you trying to pay@yukikishimoto.com? What error do you receive?

2024-12-23 19:37:41

- reply

There is a method on the database that allow to check where an event ID was seen:
```rust
let database = client.database();
let relays = database.event_seen_on_relays(id).await?;
```
This works with the in-memory database (which is used by default) and with some persistent database but not with all implementations (like with nostrdb).
Another good solution is to use the `RelayPoolNotification`, like suggested by @nprofile…ru2a

2024-12-23 08:23:52

- reply

You have to enable it in the `Cargo.toml`:
```toml
nostr-sdk = { version = "0.37", features = ["nip59"] }
```
You can find all features here: https://github.com/rust-nostr/nostr/blob/master/crates%2Fnostr-sdk%2FREADME.md#crate-feature-flags

2024-12-23 08:14:34

- reply

You have to enable `nip59` feature

2024-12-12 07:41:56

- reply

No, but I tested it few times on Android and only on GrapheneOS

2024-12-06 17:51:39

- reply

What makes the python FFI circuitous in your opinion?

2024-12-02 11:16:47

- reply

Should be fixed here: https://github.com/rust-nostr/nostr/pull/667

2024-12-02 09:25:59

- reply

The NIP42 auth is done automatically by default. The problem is that relay ask for authentication after you send an EVENT or a REQ.
After successful authenticaltion, the REQ is automatically resent but not the event (yet). I wrote a possible workaround here: https://github.com/rust-nostr/nostr/issues/509

2024-11-28 15:21:31

- reply

It doesn't check the kind 3 but the filters or the events.
Extract the author/s and the p tags from filters/events and request the kind 10002/10050 (if not already cached or if expired).
Yes, every relay have some flags (the RelayServiceFlags). These define what a relay can do. For example, the automatically added (the gossip ones) will have the `GOSSIP` flag.

2024-11-27 20:12:51

- reply

Kind 10050 is for DMs, kind 10002 for the other stuff. But both have the same aim. So IMO both have to be under the `gossip` option.

2024-11-27 19:22:49

- reply

Because the NIP17 relay list have to be auto discovered and some relays to be automatically added to the pool.
By default nothing is auto discovered and no relay is automatically added to the pool.

2024-11-27 14:38:45

## rust-nostr v0.37 is out! 🦀
### Summary
Add support to NIP17 relay list in SDK (when `gossip` option is enabled), add NIP22 and NIP73 support,
fix Swift Package, many performance improvements and bug fixes and more!
From this release all the rust features are be disabled by default (except `std` feature in `nostr` crate).
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1zuu…c2uc
* @npub1q0u…9py9
* @npub1zfs…w445
* @npub1zwn…fhrf
* @npub1acx…gj3j
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2024-11-27 11:26:30

- reply

Thanks! This would be the new snippet
```rust
use nwc::prelude::*;
let nwc = NWC::new(uri);
let params = PayInvoiceRequest::new(invoice);
let response = nwc.pay_invoice(params).await?;
```

2024-11-26 19:10:48

Hey @nprofile…gd6f, I was wondering where can I open a PR to update the nwc.dev website. I noticed that the rust-nostr snippet on the homepage is really old, now there is a very simple client to use NWC. It's not too important... just asking.

2024-11-17 18:07:54

- reply

🧡

2024-11-13 22:48:27

- reply

Thanks! Should be fixed now

2024-11-13 20:36:54

- reply

The `NostrConnect` client, after the first `get_public_key` request, remembers the user public key and will no longer ask for it for that session.

2024-11-13 14:08:11

- reply

Thanks! I already done a similar change locally that I not pushed yet, so I'm going to close this.

2024-11-13 09:49:55

- reply

I've added `NostrConnect::set_user_public_key` at commit ce05916f4acef2351e6ab648e4e7296a6d10f8d9

2024-11-10 13:53:55

- reply

The timeout in this case means "try to connect to the relays and wait for the connection for X seconds at most".

2024-11-10 13:45:56

- reply

I openes a PR: https://github.com/Pleb5/muse/pull/1
In my tests, after those changes, the WoT calculation takes between 7 and 13 secs.

2024-11-10 12:05:52

- reply

Currently, when gossip is enabled, are used all relays in user lists (there isn't a relays score at the moment). This will be improved in the next versions where will be kept a relays and gossip state into the database.
But anyway, it's weird that it require hours to complete. Can you share a code example?

2024-11-06 12:46:02

- reply

To reduce speed compilation you can disable all default features (I'll probably disable all feature by default in future) and, to reduce the binary size, change some `profile.release` config.
Tests for the example I shared yesterday:
Default features and default release profile:
* compilation time: 43 secs
* cdylib size: 479kb
* staticlib size: 58Mb
Without default features but with default release profile:
* compilation time: 31 secs
* cdylib size: 479kb
* staticlib size: 49Mb
Without default features and with LTO enabled, codegen-units set to 1 and abort on panic (but still optimized for performance instead of size):
* compilation time: 35 secs
* cdylib size: 437kb
* staticlib size: 12Mb
Same as above but optimized for size (not aggressive):
* compilation time: 30 secs
* cdylib size: 427kb
* staticlib size: 9.5Mb
I not plan to write a sync version of the SDK, also if very very basic. But I can try to reduce the above values as much as possible.

2024-11-05 22:17:55

- reply

Ahh ok. I'll think about that. But it's pretty easy to write a blocking wrapper, including only the stuff you need. This could be a solution for your above request:
```toml
[dependencies]
nostr-sdk = "0.36"
tokio = { version = "1.41", features = ["full"] }
```
```rust
use std::sync::LazyLock;
use nostr_sdk::prelude::*;
use tokio::runtime::Runtime;
static RUNTIME: LazyLock<Runtime> = LazyLock::new(|| Runtime::new().unwrap());
pub struct ClientBlocking {
inner: Client,
}
impl ClientBlocking {
pub fn add_relay(&self, url: &str) -> Result<bool> {
RUNTIME.block_on(async {
Ok(self.inner.add_relay(url).await?)
})
}
pub fn connect(&self) {
RUNTIME.block_on(async {
self.inner.connect().await
})
}
pub fn send_event(&self, event: Event) -> Result<Output<EventId>> {
RUNTIME.block_on(async {
Ok(self.inner.send_event(event).await?)
})
}
pub fn subscribe(&self, filters: Vec<Filter>) -> Result<Output<SubscriptionId>> {
RUNTIME.block_on(async {
Ok(self.inner.subscribe(filters, None).await?)
})
}
pub fn handle_notifications<F>(&self, func: F) -> Result<()>
where
F: Fn(RelayPoolNotification) -> Result<bool>,
{
let mut notifications = self.inner.notifications();
while let Ok(notification) = RUNTIME.block_on(notifications.recv()) {
let shutdown: bool = RelayPoolNotification::Shutdown == notification;
let exit: bool = func(notification)?;
if exit || shutdown {
break;
}
}
Ok(())
}
}
```

2024-11-05 18:19:05

- reply

Do you mean for Kotlin? I would say yes, but this will bring back the maintainability "issues" on my side.
If you need just a basic blocking client I could help to write and integrate it in your project, but you'll have to maintain it by yourself. It can be extended/adjusted depending on your project needs.
Just to know, are there problems with async version in kotlin? Do it increase code complexity?

2024-11-05 16:34:56

## rust-nostr v0.36 is out! 🦀
### Summary
Many, many improvements to `Relay` and `RelayPool` performance (reduced atomic operations and switched to async concurrency), add `NostrSigner` trait, better methods and struct names (`fetch_events` instead of `get_events_of`, `sync` instead of `reconcile`, `NostrConnect` instead of `Nip46Signer` and so on), add `LocalRelay` and allow to easily serve it as hidden onion service with the embedded tor client, allow to keep track of negentropy sync progress, almost halved the weight of JavaScript SDK bindings (from ~6.3MB to ~3.6MB), new experimental Flutter package, some fixes and many more!
Note for Python, Kotlin, Swift and JavaScript devs: unfortunately I can't mark things as deprecated in bindings, so this release have many breaking changes, sorry :(
Note for devs who are using `nostr-protocol` (Python), `org.rust-nostr:nostr` (Kotlin), `nostr-swift` (Swift) or `@rust-nostr/nostr` (JavaScript) libraries: these packages are now deprecated. Only the `nostr-sdk` library will be released, which include everything that was in those libraries.
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1zwn…fhrf
* @npub1w80…zqjv
* @npub17q5…6f2y
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2024-11-01 09:46:48

- reply

Fixed at 7587fba8ee72041689aa46c1436ecfa73d75d381

2024-11-01 09:11:09

- reply

Thanks!

2024-10-31 22:38:06

- reply

Found the issue, tomorrow I'll push the fix.

2024-10-31 21:05:26

- reply

No, my bad. The subscription can fail only if relay not support read operations, if the filter is empty or for timeout. In the log what do you see when it fail and return `not subscribed`?

2024-10-31 21:02:43

- reply

The `not subscribed` error is returned when subscription fails with all relays. What relays are you using? Maybe is related to NIP42 auth

2024-10-31 20:54:51

- reply

Thanks, I'll investigate.

2024-10-31 19:40:42

- reply

In new version (for now in master branch) `NostrSigner::public_key` return the user public key.
In the last release depends by the signer, but during my tests I saw that the same key is used (so the signer key match the user one), at least in amber and nsec.app.

2024-10-31 15:47:37

- reply

In last version is called `Nip46Signer`. In the next one will be renamed to `NostrConnect`.

2024-10-31 15:40:39

- reply

Hahah, it was already available, I was just testing it again for some adjustment. I accidentally used my account for test 😂

2024-10-31 15:03:36

Testing rust-nostr NIP46 signer [connect]

2024-10-31 14:42:56

Testing rust-nostr NIP46 signer [connect]

2024-10-31 14:15:20

- reply

According to new NIP-46 clarifications, the remote signer public key could be different from the user public key. So I have to adjust it again. This means that if you'll call `NostrSigner::public_key` method with a NIP46 signer, it will block until the signer reply or the timeout is reached. After the first call is executed correctly, the pk is cached.

2024-10-28 17:16:49

- reply

In general the AUTH requests are handled in another thread, so will not block the main one.

2024-10-28 16:10:01

- reply

It's sent a `sign_event` request to the signer.

2024-10-28 14:23:00

- reply

Try this commit: ede2a91ef7d3738b36a03243697fbd20efd335a1

2024-10-28 14:03:04

- reply

Ok, maybe I found the issue. The connection with signer is already initialized on demand. But, the bootstrap is executed when `signer_public_key` method is called... I saw that in your code you are calling the `NostrSigner::public_key` method, that internally call the `signer_public_key` method. For this reason it block.
I'll rework it

2024-10-28 10:55:58

- reply

The `NostrSigner::nip46` internally only construct the `NostrSigner` enumeration.
At a certain point the `Nip46Signer` have to wait for a response from the signer. Can you point me where you use it in the code?

2024-10-28 09:03:10

- reply

Try with `wss://relay.snort.social`

2024-10-23 10:29:08

- reply

No, according to NIP01 only single-letter tag are allowed in filter.
Is the "dinosaur" string included in `content` field? The `search` filter generally look only in `content` field.

2024-09-29 01:23:37

https://www.arte.tv/en/videos/RC-021581/the-satoshi-mystery/
#bitcoin #satoshi #thestoryofbitcoin

2024-09-25 16:06:49

- reply

I removed the connection timeout (was set to 10 secs) so from 4dbfa94876b136869e2feea75288f0c6a0beaa0e commit the timeout is used only for requests.

2024-09-25 16:02:43

- reply

I reworked it, now it's always on demand (commit 4dbfa94876b136869e2feea75288f0c6a0beaa0e).

2024-09-24 21:08:25

👀
https://image.nostr.build/405ff61e8780ed4717268ed061189ee31e629a78fa2eec84c6530aff8d066e5f.jpg

2024-09-24 18:01:46

- reply

I still consider it in alpha state due to the API breaking changes and some thing under the hood that should be reworked, but it's pretty stable and probably mature (I work on it from 2 years).
The outbox model is available from `v0.35` but it's a first implementation and could have issues.
I'm aware of many project that use it, but not famous (mobile) clients.
I know that Lume, Coop, Mostro, ngit-cli, Mutiny, Voyage (only the nostr lib, not nostr-sdk), DVM python projects, joinstr and whitenoise use it.
You can find others here (only the ones published on github): https://github.com/rust-nostr/nostr/network/dependents

2024-09-21 01:04:25

New energy source for #bitcoin mining
https://video.nostr.build/551e7bec3f5c0f3fd7460f57599268a55b6b0a4445b6c09e8f99594c1e39c85e.mp4

2024-09-19 21:57:16

- reply

SQLite not work too on WASM (at least the rusqlite bindings).

2024-09-19 20:29:05

- reply

Not yet!

2024-09-19 20:21:02

- reply

Yeah, I've done many changes but the query algorithm and indexing are almost the same.
I removed the event store to support windows targets too.

2024-09-19 20:19:39

- reply

Unfortunately no. At least, for sure not for `wasm32-unknown-unknown` target. Maybe `wasm32-wasi`.

2024-09-19 19:48:24

## rust-nostr v0.35 is out! 🦀
### Summary
Add gossip model support, deprecate `SQLite` database in favor of `LMDB` (fork of @npub1acg…p35c's pocket database), add support to negentropy v1 (old version is still supported!), add `MockRelay` (a local disposable relay for tests), allow usage of embedded tor client on mobile devices, many improvements, bugs fix and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1acx…gj3j
* @npub17q5…6f2y
* @npub1zwn…fhrf
* nanikamado
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift

2024-09-14 22:08:22

New version of `rust-ntfy` is out!
This version include support for authentication with access token.
https://github.com/shadowylab/ntfy
#rustlang #programming #rust #ntfy

2024-09-11 11:09:18

- reply

Yes, sure, thank you!
Currently I'm using `reqwest` for NIP05 and NIP11, so I would say to use it also for blossom. If there is a better one (that works on WASM too), it can be replaced.

2024-09-07 23:28:42

- reply

Thanks, it's a bug introduced during some changes to `get_events_of` method: by default the `MemoryDatabase` not store events so can't query. The zap method internally call `get_events_of` to get the pubkey metadata.
I'm going to fix it

2024-09-03 22:18:31

- reply

Keys::generate は次のバージョンでもう少し速くなる。

2024-09-03 15:33:36

- reply

🧡

2024-09-03 12:00:12

- reply

In rust-nostr, from `v0.34`, is available an embedded tor client.
Here is a python example (just call `embedded_tor` on client `Options`):
https://github.com/rust-nostr/nostr/blob/c4270c075a12ad0bc4a268ef5074089a4b421cee/bindings/nostr-sdk-ffi/bindings-python/examples/tor.py

2024-09-03 11:24:04

- reply

Semaphore を使うことができる。
https://docs.rs/tokio/latest/tokio/sync/struct.Semaphore.html

2024-09-02 23:32:15

- reply

I found the cause: it's the signature verification method.
Removing it the size (unzipped) is 642kb.
The verify signature method internally call only `secp.verify_schnorr` method (`secp256k1` library).

2024-09-02 22:54:15

- reply

I opened a PR: https://github.com/SnowCait/cloudflare-sandbox/pull/1
I reduced a little bit the size. I'll investigate to understand what cause this size

2024-09-01 02:37:40

Turing Complete game seems great!
Works on QubesOS too
https://image.nostr.build/ac525effa9af409f1ce8f582c605693127125cc52960ca53c71e882227aa26f0.jpg

2024-08-30 21:54:43

- reply

```python
from nostr_protocol import Keys, Nip19Profile
# OR `from nostr_sdk import Keys, Nip19Profile`
keys = Keys.parse("<private-key>") # nsec or hex
public_key = keys.public_key()
profile = Nip19Profile(public_key, relays=["wss://relay.damus.io"])
print(f"NIP-19: {profile.to_bech32()}")
print(f"NIP-21: {profile.to_nostr_uri()}")
```
You can learn more here (NIP-19 and NIP-21 sections): https://rust-nostr.org/

2024-08-28 20:36:22

- reply

Ok, I'm going to publish the patch

2024-08-28 18:21:51

- reply

Can you try this commit?
5094b373643f1629e435a5d09709d395bb5825e6

2024-08-28 18:08:01

- reply

How many relays are you using? Only 1 or more?

2024-08-28 17:56:41

- reply

With which `EventSource`?

2024-08-22 15:28:22

- reply

bindings はRustを直接使うよりも遅い。JSでは verify メソッドに0.35msかかりましたが、Rustでは0.022msでした。

2024-08-18 19:58:00

New version of `rust-ntfy` is out!
https://github.com/shadowylab/ntfy
#rustlang #programming #rust #ntfy

2024-08-18 18:51:27

- reply

You have to save the `bunker` URI in the localstorage for future connections. You can get it after first connection by calling `Nip46Signer::bunker_uri` method.
https://github.com/rust-nostr/nostr/issues/491

2024-08-15 14:51:25

## rust-nostr v0.34 is out! 🦀
### Summary
Add embedded tor client support, allow to open databases with a limited capacity (automatically discard old events when max capacity is reached), add `Client::stream_events_of` as alternative method to `Client::get_events_of` (stream events instead of waiting for `EOSE` and collect into a list), add search capability (NIP-50) support to `Filter::match_event` and databases, add NIP-31 and NIP-70 support, add option to autoconnect relay on `Client::add_relay` method call (currently disabled by default), rework the `get_events_of` methods behaviour for better consistency (`RelayPool::get_events_of` and `Relay::get_events_of` get events only from remote relay/s while `Client::get_events_of` allow to choose the source of events: `database`, `relays` or `both`), bugs fix and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1zfs…w445
* @npub1zwn…fhrf
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift

2024-08-13 20:15:33

- reply

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.

2024-08-13 19:44:09

- reply

2024-08-11 21:03:08

- reply

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

2024-08-07 11:40:50

- reply

https://crates.io/crates/rocksdb

2024-08-04 18:26:12

- reply

Should be fixed at 141c782b67c1d07479ad6dd902772d403a46c0f5
Let me know if you still have issues

2024-08-02 19:07:10

- reply

Are you on v0.33? On `master` branch seems to not happen. Weird.

2024-08-02 12:58:13

- reply

Weird, I'm not able to reproduce the issue.
Can you provide a simple example to reproduce it?
I tried this but works:
```rust
use nostr_sdk::prelude::*;
#[tokio::main]
async fn main() -> Result<()> {
tracing_subscriber::fmt::init();
let database = SQLiteDatabase::open("./db/sqlite.db").await?;
let client: Client = ClientBuilder::default().database(database).build();
client.add_relay("wss://relay.damus.io").await?;
client.connect().await;
// Negentropy reconcile
let filter = Filter::new().kind(Kind::GitRepoAnnouncement);
client
.reconcile(filter, NegentropyOptions::default())
.await?;
// Query events from database
let coordinate = [
// rust-nostr repo
Coordinate::parse("naddr1qq98yatnwskkummnw3eqz9thwden5te0wp6hyurvv4ex2mrp0yhxxmmdqgsx3kq3vkgczq9hmfplc28h687py42yvms3zkyxh8nmkvn0vhkyyusrqsqqqaue3uzvg2")?,
// example repo
Coordinate::parse("naddr1qqrkxcf3xyuxzcgpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6qcyqqq80xg2w8nml")?
];
let filter = Filter::new()
.kind(Kind::GitRepoAnnouncement)
.identifiers(
coordinate
.iter()
.map(|c| c.identifier.clone())
.collect::<Vec<String>>(),
)
.authors(
coordinate
.iter()
.map(|c| c.public_key)
.collect::<Vec<PublicKey>>(),
);
let events = client.database().query(vec![filter], Order::Desc).await?;
for event in events.into_iter() {
println!("{}", event.as_json());
}
Ok(())
}
```
The output that I receive is:
```json
{"id":"7f7a9fac2584002b6beb97d62989affdbd4b13659b277fa9d90a034f44dbdee2","pubkey":"a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d","created_at":1722589461,"kind":30617,"tags":[["d","ca118aa"],["r","ca118aac0e3fa285da167a315f3e68b2654ff792","euc"],["name","Example Repo"],["description","demonstrate ngit and gitworkshop features"],["clone","https://github.com/DanConwayDev/ExampleRepo.git"],["web","https://gitworkshop.dev/repo/ca118aa"],["relays","wss://relay.nostr.band/","wss://nos.lol/","wss://relay.damus.io/"],["maintainers","a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d"],["alt","git repository: Example Repo"]],"content":"","sig":"d5e9ef370add7e06f9b5706a40674a47597c4dfa0961fc77db4aa76108b2423bd331ddcffdedd0ff1513c6b75263e85b8c9a6d85435a68845d08300b889ce915"}
{"id":"6988cf03ed1e6f4c684ef04997b087820fb36bc6650912bc241e45d35db8fb53","pubkey":"68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272","created_at":1719967094,"kind":30617,"tags":[["d","rust-nostr"],["r","73f7c34fd424cae57a0da1be1f5fd31d9b8075c0"],["name","rust-nostr"],["description","Nostr protocol implementation, SDK and FFI"],["clone","https://github.com/rust-nostr/nostr.git"],["web","https://rust-nostr.org"],["relays","wss://relay.damus.io","wss://nos.lol","wss://nostr.mom","wss://nostr.oxtr.dev","wss://relay.nostr.bg"],["maintainers","68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272"]],"content":"","sig":"84af432928a39f892b117e86c2bd205fa3dc2e840e3373eb1229a0719707f5f5621e7379a48a6ef309a33089b29cdb8b0f2bb0d8f432e443586f29117a968f11"}
```