X.KOJIRA.IO
Timeline

reya

npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445
wip: syncing local repository to nostr git. the UI is still rough because I'm working on a brand-new UI kit for GPUI, and I'll migrate to it very soon.
https://blossom.jumble.social/dcc6e079779e052f489829f6365…
GM
it is a client for grasp protocol or nip34
Deepseek is also extremely good at Rust.
Yo. Remember Nostr Connect (web extension) that was designed by npub1r0rs5q2gk0e3d… . I've released a new version with a different name (*) called Nostr Signer. It's currently available on Firefox and under review for Chrome.

Changelog:
- Added support for NIP-44
- Fixed bugs

* About the new name: the previous extension was published under my old email, but Google has locked my account, so I have to re-publish it under a new name.

https://addons.mozilla.org/en-US/firefox/addon/nostr-signer/

https://image.nostr.build/23433d65ee7528a36bae8721f761f20…
https://image.nostr.build/cb9e1527807140989ce32781f907a5e…
https://image.nostr.build/bef9b175aa53b62b417a18d2caef466…
when I clicked to the login button, i got "login error"
When I bought the domain lume.nu, they didn't require my ID card. Now they're asking me to provide one, or they will suspend it.

https://image.nostr.build/df77082ab39c6422ac16e581b741941…

https://image.nostr.build/b53aacf7b3831a96d591d9b19188b37…
Sorry, somehow all messages have been deleted on this relay, but the other relay still has them. NIP17 is driving me mad.
Yes, this is my struggle. Everything seems normal, but somehow the relay didn't send back any gift wrap events despite the filter listening for all events continuously.

I added another relay like nip17.com, and it works fine.
nostr-sdk is marked subscription as closed, but look like no feedback to the relay.
https://image.nostr.build/514e48d1c1b0bab76fbbab0e207636f…
I think the problem is nostr-sdk isn't sent `CLOSE` req after receive `AUTH` like others
https://image.nostr.build/e9299ad30756bf1b94011a1a2ffd29c…
Hi npub1drvpzev3syqt0…

I'm wondering if there's a way to debug all messages sent by the client, like `client.notifications`. I'm debugging why my app always succeeds at authentication but fails to resubscribe after auth (both manually and with auto-auth).

Specifically, I'm already calling resubscribe, but the relay isn't sending anything after authentication (specifically the relay auth.nostr1.com). I thought this might be a relay bug, but it works fine on web clients like nostrudel.com.
Also, with automatic authentication, the SDK doesn't prevent duplicate auth requests, which causes some issues.
I've tried this API. It looks like I need to add a relay to the AdmitPolicy first to make it work. However, in my app, when receiving an auth request, the user will take action before the auth response can continue to be processed.
Hi npub1drvpzev3syqt0… , I wonder if we could have an option to disable `wait_for_ok()` for the send event API. Sometimes I just want to send an event but collect the report later.

Use cases:
- A user sends a NIP-17 message. My app will update the UI immediately, then I will listen for OK notifications via `client.notifications` and update the UI accordingly.
Hi npub1drvpzev3syqt0… ,
I think I've found the problem here. It looks like the SDK is waiting for the timeout to finish before returning the result, instead of returning immediately after receiving the event from the relay.

I've created a simple flow like this:
1. Spawn a task to listen for notifications via `client.notifications()`
2. In another task, send an event to the relay and get the output: `let event = client.send_event(event).await?`
3. You will see the notification in task <1> receive the OK event from the relay immediately.
4. However, in task <2>, the output only returns after 10 seconds (the default timeout).

Sorry for put the issue here. My GH account is locked, I will create another one later.
Both. I'm just tested the sqlite backend, it still have same issue.
I've adjusted the `ok_timeout/timeout` to 1 or 2 seconds, and now everything seems fast, as if gossip is disabled. I think there are some bottlenecks when handle notification, cc npub1drvpzev3syqt0…
I've done some debugging. After I create subscriptions, the relay responds immediately, but somehow the notification channel isn't receiving events yet.
It looks like nostr-sdk automatically runs negentropy sync when relays are added. I think this causes a bottleneck in my app and creates significant delays. My app flow works like this:

1. Users launch the app
2. The app connects to bootstrap relays
3. The app gets the user's relay list and verifies its existence
4. If the relay list exists → Get profile → Get and verify messaging relays

The flow is simple and runs step by step, so I don't think the backend affects it much. If I disable gossip, it runs fine.
Hi npub1drvpzev3syqt0…
I wonder if you have any plans for using async_utility for the gossip-sqlite crate? I can work on this, it would temporarily allow me to use it in my app.
nice, i will look into it.
I want to give users full control over the flow. Users can approve/reject auth requests. You can check the code here: https://git.reya.su/reya/coop/src/branch/redesign-2/crate…
Hi npub1drvpzev3syqt0…, I wonder if you could re-add the `resubscribe` method for relays? My app is manually handling authentication requests, but all methods related to `resubscribe` aren't exposed in the new API.
I got this issue after update to this commit:
/src/client/gossip/semaphore.rs:137:9:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
I cannot use sqlite yet, because it's depend on tokio
older →