Yuki Kishimoto

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-08-28 22:36:22

- reply

Ok, I'm going to publish the patch

2024-08-28 20:21:51

- reply

Can you try this commit?
5094b373643f1629e435a5d09709d395bb5825e6

2024-08-28 20:08:01

- reply

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

2024-08-28 19:56:41

- reply

With which `EventSource`?

2024-08-22 17:28:22

- reply

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

2024-08-18 21:58:00

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

2024-08-18 20: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 16: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 22: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 21:44:09

- reply

2024-08-11 23: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 13:40:50

- reply

https://crates.io/crates/rocksdb

2024-08-04 20:26:12

- reply

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

2024-08-02 21:07:10

- reply

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

2024-08-02 14: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"}
```

2024-07-19 19:34:29

- 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 17:23:17

- 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 16:50:42

## 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 18:24:45

- reply

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

2024-07-15 18:23:19

- 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 15:23:10

- reply

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

2024-07-10 15:38:10

- 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 20:53:56

- 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 17:59:28

- reply

Ok, understood, make sense

2024-07-08 17:40:06

- 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 15:20:05

- 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 19:39:50

- reply

Thank you 🧡

2024-07-04 18:39:11

- reply

Thank you 🧡

2024-07-04 18:37:43

- reply

Thank you 🧡

2024-07-04 18:35:42

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 14:10:17

- 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 03:03:05

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

2024-07-03 02:06:51

- 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 16:33:02

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 17:10:28

- 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 18:16:31

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 18:51:38

## 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 18:49:18

- 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 15:33:02

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 20:19:03

- 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 19:20:22

- reply

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

2024-05-17 12:24:33

## 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 20:30:51

- reply

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

2024-05-10 20:29:29

- reply

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

2024-05-10 20:25:24

- 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 19:23:20

- reply

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

2024-05-08 15:50:22

- reply

Thanks! I'll check it

2024-05-08 14:31:22

- 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 08:48:02

- 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 08:34:59

- 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 09:45:44

- 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 22:50:59

- 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 21:07:32

- reply

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

2024-04-16 17:58:36

- 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 16:32:14

- 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 23:08:15

- 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 21:37:32

https://github.com/dluvian/voyage

2024-04-12 17:43:25

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 10:33:53

- reply

Thanks! Not at the moment but probably it will be

2024-04-11 09:12:55

- reply

Thanks 🧡💜

2024-04-08 10:02:42

- reply

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

2024-04-08 09:54:22

- 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 11:41:51

- reply

Local database + negentropy should reduce it

2024-03-28 16:47:58

- reply

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

2024-03-24 18:27:48

- reply

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

2024-03-22 10:39:53

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

2024-03-22 09:42:54

- reply

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

2024-03-17 14:48:41

- reply

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

2024-03-16 18:10:12

- 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 13:47:52

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 08:41:13

- reply

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

2024-03-09 09:07:36

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

2024-03-07 23:47:12

- 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 23:27:16

- 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 19:16:41

- reply

@npub1yxp…qud4

2024-02-19 21:21:42

- reply

Thank you! 💜⚡

2024-02-19 20:58:11

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

2024-02-17 18:29:37

I just published a fix for the get_events_of method (release v0.28)
In Rust, make sure to update the nostr-database and nostr-relay-pool deps in Cargo.lock:
> cargo update -p nostr-database
> cargo update -p nostr-relay-pool
I'll publish soon also the fix for bindings packages.
#nevent1q…pnml

2024-02-16 18:03:57

New Rust Nostr release is out! 🦀
Rust: v0.28
JavaScript: v0.11
Python, Kotlin and Swift: v0.9
This release introduce the `NostrZapper` and a zap method to easily send zaps (NWC or WebLN) with the nostr-sdk!
Added NWC client (nwc crate), added `NostrZapper` trait, renamed `ClientSigner` to `NostrSigner`, huge improvements to negentropy reconciliation, support to NIP49 (ncryptsec) and NIP59 (GiftWrap), new methods to send/get events to/from specific relays, improvements to database performance and more (including some more breaking changes respect the prev versions 😅)!
The new `client.zap` method will help to support rust-nostr development, by splitting a small % of the zap⚡. Thank you to everyone will use it! 💜
Thanks to @npub17q5…6f2y and @npub1u8l…turz for contributing!
https://github.com/rust-nostr/nostr/releases/tag/v0.28.0

2024-02-06 15:33:08

- reply

The v0.27 have support to negentropy but have some issues. I fixed all the issues in master branch (you can specify a git repo and commit in the Cargo.toml or wait for v0.28)
To use negentropy you need a persistent DB. Configured that with the ClientBuilder, just call "client.reconcile". All the reconciled event will be saved in the db: use client.database().query(filters) to query what you need.

2024-02-03 15:52:06

- reply

The Nostr SDK bindings aren't aligned with the rust library yet (some methods/structs aren't exposed), but are ready for use and maintained. Unfortunately aren't available docs/examples for Kotlin (hope soon to include them in the book).
https://central.sonatype.com/artifact/io.github.rust-nostr/nostr-sdk

2024-01-29 09:27:05

- reply

Thanks! Those metadata values are used in some rust-nostr examples.
https://github.com/rust-nostr/nostr/blob/master/bindings%2Fnostr-sdk-js%2Fexamples%2Fclient.js#L27-L34

2024-01-26 17:48:22

@rust-nostr/nostr and @rust-nostr/nostr-sdk v0.10 are out!
This JavaScript "mini" release include support to uppercase single-letter tags, creation of events with custom timestamp and huge improvements to negentropy reconciliation!
https://www.npmjs.com/package/@rust-nostr/nostr-sdk

2024-01-22 12:19:39

@rust-nostr/nostr and @rust-nostr/nostr-sdk v0.9 are out!
This JavaScript release include support to ClientZapper, a way to easily send zaps (WebLN or NWC): just call `await client.zap(entity, amount, custom-details)`!
This method will also help to support rust-nostr, by splitting a small % of the zap 💜⚡
https://www.npmjs.com/package/@rust-nostr/nostr-sdk

2024-01-19 20:54:14

https://github.com/rust-nostr/nostr/pull/257
The ClientZapper will allow to easily send zaps with WebLN or NWC! 👀⚡

2024-01-19 16:04:34

https://github.com/shadowylab/webln
https://www.npmjs.com/package/@shadowylab/webln

2024-01-18 18:33:37

- reply

#nevent1q…00lt

2024-01-18 18:31:50

Rust Nostr v0.27 is out! 🦀
Released also JavaScript, Python, Kotlin and Swift v0.8.0
This release introduce the `ClientSigner` (way to use the SDK client with different types of signers: Keys, NIP07 or NIP46), NIP07 support for WASM/JS, database performance improvements and more!
Thanks to @npub1f5u…jmug @npub17q5…6f2y @npub1u8l…turz @npub1zk6…l6ef @npub1mhe…qtf9 for contributing.
https://github.com/rust-nostr/nostr/releases/tag/v0.27.0

2024-01-09 12:28:46

- reply

Released a fix for a bug related to Filter in v0.7.1 for Python, Kotlin and Swift and v0.6.1 for JavaScript

2024-01-05 14:24:08

Released new version of nostr and nostr-sdk for Python, JavaScript, Kotlin and Swift!
https://github.com/rust-nostr/nostr?tab=readme-ov-file#available-packages

2024-01-03 01:04:57

- reply

Python, JavaScript, Kotlin and Swift libraries are all bindings of the rust crates (so no transpiled)

2024-01-03 01:00:02

- reply

https://github.com/rust-nostr/nostr?tab=readme-ov-file#available-packages

2023-12-31 12:28:18

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-21 18:14:46

- reply

Yes, I adjusted it yesterday

2023-12-21 13:46:17

New Rust Nostr release! 🦀
* Rust crates v0.26.0
* Python, Kotlin and Swift packages v0.6.0
* JavaScript libraries v0.4.2
This release include support to NIP44 v2, NIP90, NostrDatabase (both for native and web envs) and more...
https://github.com/rust-nostr/nostr/releases/tag/v0.26.0
https://github.com/rust-nostr/nostr#available-packages
Thanks to @npub1u8l…turz @npub1xts…kk5s @npub1mhe…qtf9 @npub1q7q…wt9c and proudmuslim-dev for contributing.

2023-12-18 00:40:54

- 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-12-14 22:30:34

- reply

Yes, I'll take a look into it!
In the past months I built `nostr-database`, with support to multiple backends: in-memory, SQLite, RocksDB and indexeddb (for web). It's based on in-memory indexes, to perform fast queries using an vector of `Filter`, like when querying relays.
It's fast but probably not reach the same performance of nostrdb.
NostrDatabase is a generic trait so should be possible to implement also the @npub1xts…kk5s's database, making it available in nostr-sdk.
https://github.com/rust-nostr/nostr/blob/master/crates%2Fnostr-database%2FREADME.md
#nevent1q…5mah

2023-11-13 18:44:07

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-07 14:16:21

- reply

https://github.com/yukibtc/keechain