Yuki Kishimoto

## 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-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-09-02 23:32:15 GMT

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

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

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

2024-08-30 21:54:43 GMT

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

- reply

Ok, I'm going to publish the patch

2024-08-28 18:21:51 GMT

- reply

Can you try this commit?
5094b373643f1629e435a5d09709d395bb5825e6

2024-08-28 18:08:01 GMT

- reply

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

2024-08-28 17:56:41 GMT

- reply

With which `EventSource`?

2024-08-22 15:28:22 GMT

- reply

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

2024-08-18 19:58:00 GMT

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

2024-08-18 18:51:27 GMT

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

## 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 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-13 19:44:09 GMT

- reply

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-08-07 11:40:50 GMT

- reply

https://crates.io/crates/rocksdb

2024-08-04 18:26:12 GMT

- reply

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

2024-08-02 19:07:10 GMT

- reply

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

2024-08-02 12:58:13 GMT

- 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"}
```

2024-07-19 17:34:29 GMT

- reply

Ah sorry, according to bech32 could happen if the passed data is too long. So, in the case of `Coordinate`, if the identifier is huge the code will return an error. It's unlikely that happen for `Coordinate` but possible with other structs like `Nip19Profile` (ex. adding many relays).
https://github.com/rust-nostr/nostr/pull/394

2024-07-19 15:23:17 GMT

- reply

Weird, in the code it return `Result<String, Self::Err>`.
https://github.com/rust-nostr/nostr/blob/6f87fdc7a9725f7c0ccbd4766179af031132400e/crates/nostr/src/nips/nip19.rs#L797

2024-07-16 14:50:42 GMT

## rust-nostr v0.33.0 is out! 🦀
### Summary
Better outputs for send/batch/reconcile methods (ex. you can now easily know where a message/event is successfully published and where/why failed), allow to change NIP-42 option after client initialization, increase max stack size for JS bindings to prevent "memory access out of bounds" error, expose more objects/methods for JS bindings, dry run option for negentropy reconciliation, get NIP-46 relay from NIP-05 profile, bug fixes (NIP-42 auth not works correctly, NIP-46 "ACK" message not handled, ...) and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub15qy…yejr
* @npub1q0u…9py9
* @npub138h…rdr2
* @npub1zwn…fhrf
* @npub1k95…s3z7
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr

2024-07-15 16:24:45 GMT

- reply

https://github.com/rust-nostr/nostr/blob/bdd250dab7f107b78aae63214c115336248e8367/crates/nostr-sdk/examples/sqlite.rs#L44-L50

2024-07-15 16:23:19 GMT

- reply

I tried to add the send failures at commit `bdd250dab7f107b78aae63214c115336248e8367`.
What do you think of that solution? I'm not still very convinced but for now could be good.
I'll try to add receive errors in the v0.34 release, in next few days I'll release v0.33

2024-07-11 13:23:10 GMT

- reply

Thanks, I adj. some thing and cherry-picked at 931c7bbd155af2858dffc3e00e9fcfa583e4c257

2024-07-10 13:38:10 GMT

- reply

`local` means events stored in database but NOT on relay. The opposite, `remote` means events stored on relay and not in database. I'll adj. docs to make this clear
Good idea, I missed to add send failures. But, the receive failures are currently not possible to known, error regarding receive failures are only logged (this could be a thing to improve). For example, if the event received is too big, will logged a message but no error is returned. Checks for received events are done here: https://github.com/rust-nostr/nostr/blob/d244d10f53bf0ad2a1e84fffdf658c84d7bcce0c/crates/nostr-relay-pool/src/relay/internal.rs#L799-L999

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-07-08 15:59:28 GMT

- reply

Ok, understood, make sense

2024-07-08 15:40:06 GMT

- reply

What could be the use case?
Do you mean execute the reconciliation (including getting full events) and return the IDs of events that were missing? Or a way to get those IDs without get full events from relay?

2024-07-08 13:20:05 GMT

- reply

By default reconciliation direction is "down", so only get events from relays and not rebroadcast events. The reconciliation direction it's defined by `NegentropyDirection`.

2024-07-04 17:39:50 GMT

- reply

Thank you 🧡

2024-07-04 16:39:11 GMT

- reply

Thank you 🧡

2024-07-04 16:37:43 GMT

- reply

Thank you 🧡

2024-07-04 16:35:42 GMT

I'm so honored to have been selected, you've realized my dream: working full time on open source projects as an independent dev! Thank you so much OpenSats and donors 🧡
#nevent1q…sdgr

2024-07-04 12:10:17 GMT

- reply

Check examples, book is not ready yet 😅
https://github.com/rust-nostr/nostr/tree/master/bindings%2Fnostr-sdk-ffi%2Fbindings-python%2Fexamples

2024-07-03 01:03:05 GMT

👀
https://image.nostr.build/a48128774ac13dc3824c39bbb3f4e11049a33835b7db1ca81b3cefb147c68144.jpg

2024-07-03 00:06:51 GMT

- reply

I tooka quick look at the event and it seems huge. Disabling limits should solve the issue. You can find an example here:
https://github.com/rust-nostr/nostr/blob/master/crates%2Fnostr-sdk%2Fexamples%2Flimits.rs

2024-07-02 14:33:02 GMT

New version of `reverseproxy` is out. This release include full support to embedded Tor client and hidden onion services.
```bash
reverseproxy 127.0.0.1:8080 myhiddenservice.onion:80 --tor
```
https://github.com/shadowylab/reverseproxy

2024-06-20 15:10:28 GMT

- reply

If you import everything with `use nostr::prelude::*` and want to use NIP04, specify also the module instead of just the function, like this:
```
nip04::decrypt(sk, pk, content)
```

2024-06-14 16:16:31 GMT

Released a patch for Python, Kotlin and Swift `nostr-sdk` packages that not allow usage of relays with TLS v1.2 certificates.
Rust devs have to update the `async-wsocket` dep in `Cargo.lock` file to `v0.5.2`: `cargo update -p async-wsocket`.
Python, Kotlin and Swift devs, just bump the package from `v0.32.1` to `v0.32.2`.
Thanks to the @npub1m0s…40un team!

2024-06-07 16:51:38 GMT

## rust-nostr v0.32 is out! 🦀
### Versions
Rust & JS: `v0.32.0`
Python, Kotlin & Swift: `v0.32.1`
From this release all packages for all languages will have the same major and minor versions.
### Summary
Added `async`/`future` support to Python, Kotlin and Swift, added automatic authentication to relays (NIP-42, can be deactivated in client options), improvements to relay limits, many bug fixes (relays not auto reconnect, wrong query order for SQLite, tokio panic when using SQLite database in bindings) and more!
Note for kotlin devs: from this release the packages will be published at `org.rust-nostr` instead of `io.github.rust-nostr`.
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to all contributors!
* @npub1u8l…turz
* @npub1q0u…9py9
* @npub1zwn…fhrf
Thanks also to @npub1nxa…a6q8 for helping to discover some nasty bugs!
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr

2024-05-28 16:49:18 GMT

- reply

Publishing `0.13.0-alpha.2` that fixes some issues related to async changes.
Python devs that receive "no running event loop" have to add `uniffi_set_event_loop(asyncio.get_running_loop())` line to the code.

2024-05-28 13:33:02 GMT

For all devs using the Python, Kotlin or Swift rust-nostr libraries: I've published an alpha version of nostr-sdk with async/future support. Please give it a try and give me a feedback.
All rust-nostr libraries (except for protocol implementation) are async so make sense to convert bindings to async instead of keeping them blocking, but I don't know how common async programming is in those langs.
The alpha versions are:
* Python: 0.13.0a1.dev0
* Kotlin: 0.13.0-alpha.1
* Swift: 0.13.0-alpha.1
Here you can find some async python examples: https://github.com/rust-nostr/nostr/tree/async-ffi/bindings%2Fnostr-sdk-ffi%2Fbindings-python%2Fexamples
https://github.com/rust-nostr/nostr/pull/379
@npub1nxa…a6q8 @npub1mgv…pdjc @npub1use…k5ks @npub138h…rdr2
#rustnostr

2024-05-27 18:19:03 GMT

- reply

I'm compiling the wheels only for some python versions and arch, so maybe it's not available the one for your setup. Here you can check the support matrix: https://rust-nostr.org/nostr-sdk/02-installation.html#support-matrix
If miss your one, you can compile the wheel by yourself:
* Clone rust-nostr repo
* `cd bindings/nostr-sdk-ffi` (or `cd bindings/nostr-ffi`)
* Install `rust` and `just`
* Run `just python`
The wheel will be located in `bindings-python/dist`

2024-05-27 17:20:22 GMT

- reply

Hey, I not tested on Alpine yet. Have you any issue?

2024-05-17 10:24:33 GMT

## rust-nostr release is out! 🦀
### Versions
Rust: v0.31
JavaScript: v0.14
Python, Kotlin and Swift: v0.12
### Summary
Reworked `Tag`, added `TagStandard` enum, simplified the way to subscribe and/or reconcile to subset of relays (respectively, `client.subscribe_to` and `client.reconcile_with`), added blacklist support to mute public keys or event IDs, removed zap split from `client.zap` method, many improvements and more!
Full changelog: https://rust-nostr.org/changelog
### Contributors
Thanks to @npub15qy…yejr for contributing!
### Links
https://rust-nostr.org
https://rust-nostr.org/donate
#rustnostr #nostr

2024-05-10 18:30:51 GMT

- reply

And here: https://github.com/hoytech/strfry/blob/master/docs%2Fnegentropy.md

2024-05-10 18:29:29 GMT

- reply

There isn't a NIP yet, but you can learn more here: https://github.com/hoytech/negentropy

2024-05-10 18:25:24 GMT

- reply

The v0 since strfry not merged v1 yet (IIRC v1 is not compatible with v0). But the rust-negentropy implementation is ready for v1.

2024-05-10 17:23:20 GMT

- reply

Negentropy reconciliation. It's available in rust-nostr, just call `client.reconcile(..)`.

2024-05-08 13:50:22 GMT

- reply

Thanks! I'll check it

2024-05-08 12:31:22 GMT

- reply

For now I created a Matrix space: https://matrix.to/#/#rustnostr:matrix.org
I prefer to avoid Telegram, Discord and so on.
If there is a good alternative to Matrix spaces here on nostr, with a desktop/web client, we can move there.

2024-05-08 06:48:02 GMT

- reply

`client.get_events_of` it's basically an auto-closing subscription: subscribe, listen until EOSE or when timeout is reached, close subscription and return events.
To subscribe "forever", just use the `client. subscribe` method. All the events will be sent to a notification channel. You can find an example here:
https://github.com/rust-nostr/nostr/blob/master/bindings%2Fnostr-sdk-ffi%2Fbindings-python%2Fexamples%2Fbot.py

2024-05-07 06:34:59 GMT

- reply

It's intentional. Using in-memory indexes remove some work to me. But in the long term it will probably be replaced with DB-native indexes.
I not done tests/benches with native indexes yet, but indexeddb (the db for the browser), in general, it's slow... so in-memory indexes help a bit.

2024-04-17 07:45:44 GMT

- reply

When you call the 'notifications' method, you subscribe to the notification channel from that precise moment. Anything sent before that moment is not included in the channel.
In the code you were subscribing to the relays very early and then you were sending the metadata event (if one of the relays is offline it may take some seconds to continue). Therefore, when the `notifications` method was finally called, it's likely that the events had already been received (but not included in the notification channel).
---
I'll update the documentation of the "notifications" method.

2024-04-16 20:50:59 GMT

- reply

Try to move the `client.subscribe` code and filter in the `process_reminder_notifications` func, between the `let mut notifications = client.notifications();` and `info!("listening for notifications");`

2024-04-16 19:07:32 GMT

- reply

Mh, that's weird. Is it in this project that you're having issues?
https://github.com/w3irdrobot/remindme

2024-04-16 15:58:36 GMT

- reply

No, if persistent database is not enabled the "seen" set is stored in RAM. So, if you stop and re-start the client you'll receive the Event notification again.

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.

2024-04-15 21:08:15 GMT

- reply

You have to use the `to_bech32` method.
The book is not ready, but you can find some example related to keys here: https://rust-nostr.org/nostr/03-keys.html

2024-04-14 19:37:32 GMT

https://github.com/dluvian/voyage

2024-04-12 15:43:25 GMT

New rust-nostr release is out! 🦀
Rust: v0.30
JavaScript: v0.13
Python, Kotlin and Swift: v0.11
Adapted NIP46 to last changes, added `NostrConnectRemoteSigner` to easily build remote signers (just construct it and call `serve` method), improved proxy options (allow to specify the proxy target: all relays or only `.onion` ones),
improvements to NWC client, fixed equality operator for some foreign language (python still need to use `a.__eq__(b)`), added `nostrdb` storage backend (noto available for windows yet), added NIP32 and completed NIP51 support and more!
Changelog: https://github.com/rust-nostr/nostr/blob/v0.30.0/CHANGELOG.md
Thanks to @npub1mhe…qtf9 @npub138h…rdr2 @npub1u8l…turz @npub1q0u…9py9 @npub15qy…yejr for contributing!
https://github.com/rust-nostr/nostr/releases/tag/v0.30.0
https://rust-nostr.org/donate
#rustnostr

2024-04-11 08:33:53 GMT

- reply

Thanks! Not at the moment but probably it will be

2024-04-11 07:12:55 GMT

- reply

Thanks 🧡💜

2024-04-08 08:02:42 GMT

- reply

Custom field allow you to set non-standard or not yet implemented fields.

2024-04-08 07:54:22 GMT

- reply

set_name update the "name" field that is basically the username, for example "yuki".
set_display_name update the "display_name" field that is an alternative bigger name with richer characters, like "Yuki Kishimoto".

2024-03-29 10:41:51 GMT

- reply

Local database + negentropy should reduce it

2024-03-28 15:47:58 GMT

- reply

Yes!
@npub1nxa…a6q8
https://github.com/believethehype/nostrdvm

2024-03-24 17:27:48 GMT

- reply

Try to take a look at https://pypi.org/project/nostr-sdk/

2024-03-22 09:39:53 GMT

What IDE/editor do you use for Rust?
#rustlang

2024-03-22 08:42:54 GMT

- reply

What IDE/editor do you use for Rust?
#rustlang

2024-03-17 13:48:41 GMT

- reply

https://doc.rust-lang.org/stable/book

2024-03-16 17:10:12 GMT

- reply

For sure until July, thanks to @npub10pe…n34f
And I hope to continue to work on it full-time for the next years (I'll try to apply again for a grant in the next weeks/month, this time for the OpenSats LTS).
Otherwise, I'll try to work on it anyway, but in the free time 😅

2024-03-15 12:47:52 GMT

New Rust Nostr release is out! 🦀
Rust: v0.29
JavaScript: v0.12
Python, Kotlin and Swift: v0.10
New automatic shutdown on drop system for `Relay`, `RelayPool` and everything build on them (no longer required to call shutdown method), improvements to NWC client (now available also from Python, Kotlin and Swift!), NIP44 functions for NIP07 signer, improvements to subscription system, allow to edit relay limits, allow to use a custom database in Python, Kotlin and Swift (in rust was already possible), re-added support to `Filter::match_event` and more!
Thanks to @npub1lu2…xlm6 @npub1u8l…turz @npub1mhe…qtf9 @npub1aha…45hy for contributing!
https://github.com/rust-nostr/nostr/releases/tag/v0.29.0
https://rust-nostr.org/donate
#rustnostr

2024-03-12 07:41:13 GMT

- reply

Have you tried iced?
https://github.com/iced-rs/iced

2024-03-09 08:07:36 GMT

https://nakamotoinstitute.org/library/cypherpunk-manifesto

2024-03-07 22:47:12 GMT

- reply

Ah, my bad. For Zeus is not needed that client 😅
Anyway, I'm planning to build an implementation also for nodes (hope to include it in next release)

2024-03-07 22:27:16 GMT

- reply

Last release of bindings not include the NWC client yet (in rust is already available).
Approx. in a week I'll release the new version that will include it:
nwc = NWC(uri)
nwc.pay_invoice(..)
nwc.get_balance()
...

2024-02-23 18:16:41 GMT

- reply

@npub1yxp…qud4

2024-02-19 20:21:42 GMT

- reply

Thank you! 💜⚡

2024-02-19 19:58:11 GMT

It's now possible to support rust-nostr with recurring donations! (experimental)
In addition to one-time donations and split zaps, are now available the recurring donations, entirely based on nostr and lightning (NWC).
https://subscribe.rust-nostr.org/
https://rust-nostr.org/donate.html
#rustnostr #NWC