Yuki Kishimoto

GitHub: https://github.com/yukibtc
PGP: 86F3 105A DFA8 AB58 7268 DCD7 8D3D CD04 2496 19D1

Public Key

npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet

NIP-05 Address

Profile Code

nprofile1qqsx3kq3vkgczq9hmfplc28h687py42yvms3zkyxh8nmkvn0vhkyyuspz3mhxue69uhkummnw3ezummcw3ezuer9wcqs6amnwvaz7tmwdaejumr0dsf6t4nk

Publishing to

nostr.oxtr.dev

nos.lol

relay.damus.io

Author Public Key

npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet

Show more details

Last Notes

2025-03-30 08:29:36 GMT

- reply

Because I was using SQLite only for persistence. When it was opened, all the data was loaded into RAM, in the DatabaseHelper. It was basically an in-memory database with SQLite as persistence.
Using the NostrDatabase traits, you can implement your own database, and use it in rust-nostr. But if anyone is interested to open a PR to implement a "pure" SQLite backend, I'll merge it.

2025-03-30 08:28:36 GMT

- reply

You can see the REQs using the debug log level

2025-03-18 09:42:34 GMT

## 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-13 21:28:46 GMT

- reply

```python
from nostr_sdk import EncryptedSecretKey
encrypted = EncryptedSecretKey.from_bech32("ncryptsec...")
secret_key = encrypted.to_secret_key("<password>")
```

2025-01-31 11:15:31 GMT

- reply

For now are available: Keys signer (with both NIP04 and NIP44 support), NIP59, event de/serialization, event building and the SDK Client (NIP42 auto authentication, gossip, event sending, event fetching and subscriptions).
I'll add the other stuff as I find the time. If you need something specific, let me know that I'll expose it.

2025-01-31 10:55:20 GMT

- reply

Nice! Yeah haha

2025-01-31 10:50:08 GMT

## rust-nostr v0.39 is out! 🦀
### Summary
Add NIP96 support, add NIP22 helpers, NIP01 adjustments, add `try_connect` and `wait_for_connection` methods for better connection handling, support for custom WebSocket clients (both in Rust, Python, Kotlin and Swift), new JVM bindings (Linux, macOS and Windows), huge reduction of UniFFI bindings binaries size, many cleanups, refactoring and performance improvements and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all code contributors!
* @npub1qqq…rfkq
* @npub1zwn…fhrf
* @npub1r3c…fx0c
* @npub1v0l…qj49
* ethicnology
* Gudnessuche
Thank also to @npub1use…k5ks, @npub1a3t…kq4k and spacecowboy!
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr #rustlang #programming #rust #python #javascript #kotlin #swift #flutter

2025-01-20 13:16:39 GMT

- reply

How? :)

2025-01-20 12:44:17 GMT

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 GMT

- 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-14 22:25:05 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- reply

🧡

2024-12-31 12:38:15 GMT

- reply

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

2024-12-31 11:38:32 GMT

## 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 GMT

- reply

Wow, thank you very much 🧡

2024-12-24 08:34:08 GMT

- reply

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

2024-12-24 08:30:11 GMT

- reply

Are you trying to [email protected]? What error do you receive?

2024-12-23 19:37:41 GMT

- 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 GMT

- 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 GMT

- reply

You have to enable `nip59` feature

2024-12-12 07:41:56 GMT

- reply

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

2024-12-06 17:51:39 GMT

- reply

What makes the python FFI circuitous in your opinion?

2024-12-02 11:16:47 GMT

- reply

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

2024-12-02 09:25:59 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

## 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 GMT

- 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 GMT

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 GMT

- reply

🧡

2024-11-13 22:48:27 GMT

- reply

Thanks! Should be fixed now

2024-11-13 20:36:54 GMT

- 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 GMT

- 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 GMT

- reply

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

2024-11-10 13:53:55 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

- 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 GMT

## 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 GMT

- reply

Fixed at 7587fba8ee72041689aa46c1436ecfa73d75d381

2024-11-01 09:11:09 GMT

- reply

Thanks!

2024-10-31 22:38:06 GMT

- reply

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

2024-10-31 21:05:26 GMT

- 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 GMT

- 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 GMT

- reply

Thanks, I'll investigate.

2024-10-31 19:40:42 GMT

- 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 GMT

- reply

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

2024-10-31 15:40:39 GMT

- 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 GMT

Testing rust-nostr NIP46 signer [connect]

2024-10-31 14:15:20 GMT

- 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 GMT

- reply

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

2024-10-28 16:10:01 GMT

- reply

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

2024-10-28 14:23:00 GMT

- reply

Try this commit: ede2a91ef7d3738b36a03243697fbd20efd335a1

2024-10-28 14:03:04 GMT

- 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 GMT

- 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 GMT

- reply

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

2024-10-23 10:29:08 GMT

- 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 GMT

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

2024-09-25 16:06:49 GMT

- 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 GMT

- reply

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

2024-09-24 21:08:25 GMT

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

2024-09-24 18:01:46 GMT

- 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 GMT

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

2024-09-19 21:57:16 GMT

- reply

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

2024-09-19 20:29:05 GMT

- reply

Not yet!

2024-09-19 20:21:02 GMT

- 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 GMT

- reply

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

2024-09-19 19:48:24 GMT

## 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 GMT

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 GMT

- 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 GMT

- 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 GMT

- reply

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

2024-09-03 15:33:36 GMT

- reply

🧡

2024-09-03 12:00:12 GMT

- 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 GMT

- reply

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

2024-08-13 20:15:33 GMT

- 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-11 21:03:08 GMT

- 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-07-09 18:53:56 GMT

- reply

What do you think of this solution?
https://github.com/rust-nostr/nostr/pull/495
```rust
let opts = NegentropyOptions::default(); // Add `.dry_run()` to only check local and remote events without get them
let output = client.reconcile(filter, opts).await?;
println!("Local: {}", output.local.len());
println!("Remote: {}", output.remote.len());
println!("Sent: {}", output.sent.len());
println!("Received: {}", output.received.len());
```

2024-04-16 14:32:14 GMT

- reply

The `Event` variant is sent only if the event ID was never seen. The `Message` variant is sent always, except for the `EVENT` msg if you have a persistent database enabled and the event was already stored.

2023-12-31 11:28:18 GMT

nostr-js and nostr-sdk-js v0.5.0 are out!
This release include NIP07 support.
NIP07 is available also for rust WASM in `master` branch (will be included in release v0.27).
https://www.npmjs.com/package/@rust-nostr/nostr-sdk
https://github.com/rust-nostr/nostr/blob/master/bindings%2Fnostr-js%2Fexamples%2Fnip07.js
https://github.com/rust-nostr/nostr/blob/master/bindings%2Fnostr-sdk-js%2Fexamples%2Fnip07.js

2023-12-17 23:40:54 GMT

- reply

It's possible to integrate any database, also ones that not support arbitrary queries, by using the `DatabaseIndexes`.
All the current backends available for nostr-sdk (SQLite, indexeddb, RocksDB, ...) rely on it, also SQLite that has the ability to perform complex queries.
The flow under the hood is: build in-memory indexes (700_000 events are indexed in ~1.5 sec, not faster due to param/replaceable and deletion events checks), query indexes by filters and use the output (event IDs) to get full events from persistent DB.

2023-11-13 17:44:07 GMT

Nostr SDK now support in-memory and persistent storages.
Currently are available the MemoryDatabase (RAM, by default store only the seen event ids but it's configurable to store the full events), RocksDB, SQLite and IndexedDB (for web apps).
It's possible to use custom database just implementing the NostrDatabase trait.
NostrDatabase trait provide some very generic methods, useful to improve the efficiency and performance of nostr apps, like: query events by filters, get user profile and get items for negentropy reconciliation.
If anyone is interested in testing new changes can find 2 examples in nostr-sdk crate (rocksdb.rs and sqlite.rs, more docs coming soon) and 1 example in nostr-indexeddb crate. Let me know if there are issues.
https://github.com/rust-nostr/nostr/blob/f20c77660691f895879ec523c234ee9cb3f68ea6/crates/nostr-database/src/lib.rs#L88
https://github.com/rust-nostr/nostr/tree/f20c77660691f895879ec523c234ee9cb3f68ea6/crates/nostr-indexeddb/examples/webapp
https://github.com/rust-nostr/nostr/blob/f20c77660691f895879ec523c234ee9cb3f68ea6/crates/nostr-sdk/examples/sqlite.rs

2023-11-01 16:23:55 GMT

nostr and nostr-sdk v0.25 are out! 🦀
Released also v0.0.5 of Python, Kotlin and Swift bindings packages.
https://github.com/rust-nostr/nostr#available-packages
Thanks to @npub17q5…6f2y @npub1u8l…turz @npub1qqp…l2ng @npub1rf0…7gj6 for contributing.

2023-10-25 13:17:42 GMT

- reply

Not too much time ago the WEF said that they have to focus on the water emergency... because the climate change it's too abstract to understand for someone... 🤡🤡

2023-09-11 22:04:13 GMT

- reply

Thank you. I'm still improving and studying better the negentropy protocol.
I converted the code from C++ to Rust in basically a day and half (I'm not a C++ dev so some thing could be converted badly) and are there some things to fix/improve.
Like, I noticed an unstable performance with reconcilie_with_ids method with a set of 50000 items: it usually took 600 ms the final reconciliation but often it took 2 or 4 secs (executing exactly the same code).
Thanks, I'll replace the String with a vector.
BTW, I'm planning to release also bindings for some languages (Kotlin, Swift and Python) using UniFFI, like I have done for rust-nostr libraries.

2023-08-17 09:32:00 GMT

- reply

A big thanks also to @npub10pe…n34f for the financial support 🧡

2023-03-25 16:10:30 GMT

https://github.com/rust-nostr/nostr/releases/tag/v0.20.0

2023-01-03 18:17:23 GMT

- reply

😅
I hope soon but I usually work on backend and SDKs so I’m a little bit slow on GUI development 😅
Maybe I can release a first alpha in two weeks (I hope).
Before I need to make some improvements to my nostr-sdk library.

2022-12-16 18:50:39 GMT

Hey nostr, I just released the first alpha version of KeeChain.
It's a Bitcoin keychain that support also nostr (NIP-06 and NIP-26).
To see all details and features, go to https://github.com/yukibtc/keechain
See in the release page to download the binary for your platform, or build by yourself.
Give me some feedback 😄

2022-12-01 18:18:57 GMT

- reply

Oh, I missed NIP-26.
I’ll try to integrate sign delegations in keechain.