reya

Public Key

npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445

Profile Code

nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds9z9f3c

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445

Show more details

Last Notes

2026-08-18 01:07:26 UTC

WIP: issue browse
https://relay.reya.su/c86b3ccdd11dc9f57e73b6d7474455562c1a468a2f271811b5a4a217fdaff105.mp4

2026-08-17 06:34:43 UTC

- reply

Hi @npub1drv…seet , can we have an option for that? it looks like nostr-sdk enforces a custom timestamp for the sealed event when building gift wrap event: https://github.com/nostrdevkit/nostr/blob/e892ea0a32b3b92909bb6409494adc5a46a19d75/nostr/src/nips/nip59.rs#L441

2026-08-10 06:49:11 UTC

- reply

I've lost access to that github account. So I'm working on this repo for now: https://git.reya.su/reya/coop and https://git.reya.su/reya/coop-mobile
Yes, GPUI is actually better than Rust + Web, it also work good enough on Linux and extremely flexible.

2026-08-10 00:23:31 UTC

- reply

Deepseek is also extremely good at Rust.

2026-08-07 06:39:50 UTC

- reply

Maybe a new model is coming soon, so the old model is getting throttled 🤣

2026-08-06 01:27:44 UTC

It seems Gitea is under attack. I also received a warning from Vultr.
https://npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445.blossom.band/584599fae1cdaa9a268534d3f94729e3bb7dae811be6696125c0b4cfa9156a5a.png

2026-08-05 02:17:05 UTC

- reply

I don't know why, but only chinese models like kimi or deepseek give me consistent results

2026-08-05 02:06:40 UTC

- reply

It seems it runs android

2026-08-04 06:19:22 UTC

my dream phone
https://youtu.be/Y9LeCTcK5PY

2026-07-29 13:39:28 UTC

- reply

the next 2 years will very painful

2026-07-27 10:24:39 UTC

- reply

I already do that, but it still require define_time_provider!
You can check the file here: https://git.reya.su/reya/coop/src/commit/fd32b8c0ce2348c046d7e458ce292270a6118260/web/src/main.rs

2026-07-27 09:38:44 UTC

- reply

I got other issue with the universal-time crate:
```
error: a time provider is required.
Use `define_time_provider!(YourProvider)` in your binary crate.
See: https://github.com/shadowylab/universal-time
```

2026-07-26 13:40:32 UTC

- reply

Did you work on it yet? I will look into it on tomorrow and create a PR

2026-07-25 03:29:40 UTC

- reply

Any updates on this? 🤣

2026-07-25 00:20:36 UTC

- reply

You can try Coop: https://zapstore.dev/apps/su.reya.coop
iOS version will coming later.

2026-07-23 08:10:53 UTC

- reply

when I see an announcement like that, I highly suspect nothing burgers 🤣

2026-07-22 01:02:20 UTC

- reply

What parts didn't you like about the UI? I'm just curious, because I'm building something similar and need more insights

2026-07-18 07:17:14 UTC

- reply

I got the dependency issues fixed. But look like async api from sdk didn't work in wasm enviroment?
```
error: future cannot be sent between threads safely
--> crates/state/src/lib.rs:307:12
|
307 | cx.background_spawn(async move {
| ^^^^^^^^^^^^^^^^ future created by async block is not `Send`
|
= help: the trait `std::marker::Send` is not implemented for `dyn futures::Future<Output = Result<nostr_sdk::prelude::Event, nostr_gossip_memory::prelude::Error>>`
note: future is not `Send` as it awaits another future which is not `Send`
--> crates/state/src/lib.rs:309:25
|
309 | let event = EventBuilder::new(Kind::Custom(5315), "")
| _________________________^
310 | | .tags(vec![
311 | | Tag::custom("param", vec!["search", &query]),
312 | | Tag::custom("param", vec!["limit", "10"]),
313 | | ])
314 | | .finalize_async(&signer)
| |________________________________________^ await occurs here on type `Pin<Box<dyn futures::Future<Output = Result<nostr_sdk::prelude::Event, nostr_gossip_memory::prelude::Error>>>>`, which is not `Send`
note: required by a bound in `background_spawn`
```

2026-07-17 10:27:18 UTC

- reply

Look like rust-secp256k1 isn't support wasm either. Do you know other solution?

2026-07-16 07:01:08 UTC

Hi @npub1drv…seet
I want to port coop (desktop) to web via wasm, but look like getrandom isn't enable wasm support (via wasm_js feature). Can you enable it in the main repo?

2026-07-15 01:26:25 UTC

I see Japanese users are very consistent in using Nostr everyday.

2026-07-13 11:18:16 UTC

- reply

I want to learn zig someday, it seem fun

2026-07-12 07:02:46 UTC

- reply

I think mostly github stars are made by bots 🤣

2026-07-09 03:32:19 UTC

- reply

yes, this is a red flag

2026-07-09 01:30:31 UTC

My instinct tell me that Proton (mail/drive/vpn/etc...) isn't good guy.

2026-07-08 04:40:33 UTC

- reply

this remind me about the terra/luna shitcoin 🤣

2026-07-08 01:23:23 UTC

Why is the EU so obsessed with Chat Control? I hear about it every month. #asknostr

2026-07-07 07:25:07 UTC

- reply

I've fixed the issue with nostr connect, tested with nak and auth.njump.me relay. You can update via zapstore or install new build here: https://git.reya.su/reya/coop-mobile/releases/tag/v0.2.4
cc: @npub1msd…meds

2026-07-03 11:00:13 UTC

- reply

hmm, somehow I still got the warning. maybe it don't work on KMP but only Android?

2026-07-03 08:05:32 UTC

Hi @npub1drv…seet
Do you know how to enable the 16KB support for nostr-sdk? Look like modern android require it.
https://nostr.download/35211622782ff7846b4198713f342b47a752a565078e4bcab5a4909c94edd3d5.png

2026-07-01 10:13:37 UTC

learning korean, pretty interesting language.

2026-06-30 08:03:45 UTC

- reply

wired-chan

2026-06-30 00:35:54 UTC

- reply

Welcome

2026-06-28 00:23:02 UTC

- reply

I think this is a bug from haven, instead of sent auth-request, it sent:
```
2026-06-27T14:19:18.099984Z DEBUG nostr_sdk::relay::inner: Received '["CLOSED","gift-wraps","blocked: you must be in the web of trust to chat with the relay owner"]' from 'wss://relay.reya.su/chat'
```

2026-06-27 14:22:58 UTC

- reply

Also
```
2026-06-27T14:19:18.157682Z DEBUG nostr_sdk::relay::inner: Skip re-subscription of 'gift-wraps'
```

2026-06-27 14:22:27 UTC

- reply

the issue still persist, here are my logs:
```
2026-06-27T14:19:18.058769Z DEBUG nostr_sdk::relay::inner: Received '["AUTH","050e843f5f3ee2d0"]' from 'wss://relay.reya.su/chat'
2026-06-27T14:19:18.069279Z DEBUG nostr_sdk::relay::inner: Sending '["AUTH",{"content":""
2026-06-27T14:19:18.099984Z DEBUG nostr_sdk::relay::inner: Received '["CLOSED","gift-wraps","
2026-06-27T14:19:18.100058Z DEBUG nostr_sdk::relay::inner: Removing subscription. url=wss://relay.reya.su/chat id=gift-wraps
2026-06-27T14:19:18.120491Z DEBUG nostr_sdk::relay::inner: Received '["OK","3dfb
2026-06-27T14:19:18.120723Z INFO nostr_sdk::relay::inner: Authenticated to relay. url=wss://relay.reya.su/chat
```

2026-06-27 09:12:41 UTC

Hi @npub1drv…seet
I've noticed a strange issue when nostr-sdk close subscription early without wait for AUTH completed, this is why sometime Coop cannot load full messages because it cannot read from relay. The flow look like this:
User send REQ -> Relay send AUTH and CLOSED -> SDK is sending AUTH and also remove the subscription because of CLOSED -> Relay return OK -> SDK cannot resubscribe because the subscription was removed.
Relay software: https://github.com/barrydeen/haven/

2026-06-27 01:12:16 UTC

- reply

Keychat using Signal/MLS protocol but Coop is just pure NIP-17 implementation

2026-06-26 13:57:56 UTC

Hi @npub1wf4…dgh9
I wonder how can I add my app (https://zapstore.dev/apps/su.reya.coop) to the Private Chats curated list. Or it is manually maintaining?

2026-06-26 13:17:25 UTC

I think GTA6 will be the biggest slop this year

2026-06-26 07:30:47 UTC

- reply

Thank for helping me testing Coop.

2026-06-25 03:20:56 UTC

- reply

I've fixed my issue by create a custom zapstore.yaml file

2026-06-23 02:56:47 UTC

- reply

I just run:
```
zsp publish --wizard
```
then enter my repo url

2026-06-23 01:19:47 UTC

Hi @npub1wf4…dgh9
I want to publish my app to Zapstore, but when I enter the URL, I always got the error: "The wizard supports GitHub, GitLab, Gitea, F-Droid, or local paths...".
My repo: https://git.reya.su/reya/coop-mobile

2026-06-22 02:55:20 UTC

- reply

it's over

2026-06-21 00:27:33 UTC

- reply

I'm not even play GTA 5 yet

2026-06-17 09:16:06 UTC

- reply

I'm 😁. Do you use android phone? I need someone help me test some stuffs and the UI, still in alpha

2026-06-13 10:37:36 UTC

- reply

Is it still using the character swap combat?

2026-06-11 13:48:14 UTC

- reply

first time I hear about odin, seem cool language

2026-06-09 22:51:47 UTC

- reply

* thighs sir

2026-06-07 10:26:20 UTC

- reply

but I think deleting X is a mistake, no way you can promote nostr ...on nostr

2026-06-07 07:49:32 UTC

hi @npub1drv…seet , check my nip17 dm

2026-06-06 07:25:47 UTC

- reply

the only LLM that works consistently for me, others are just overpriced and sometimes work, sometimes dont

2026-06-06 01:18:34 UTC

Summer Game Fest this year is awesome

2026-06-04 07:44:20 UTC

- reply

I still keep my instagram account just for this

2026-06-04 02:25:35 UTC

- reply

Hi @npub1msd…meds
I've pushed a new build, it is fixed all your issues on yesterday. you can it here: https://git.reya.su/reya/coop-mobile/releases/tag/v0.1.6
let me know if you catch any issues

2026-06-03 07:51:25 UTC

- reply

I've fixed this issue on the master branch, I will push a new build today too after fix the empty room problem

2026-06-03 07:40:21 UTC

- reply

Yup, I'm working to fix it.

2026-06-03 07:27:48 UTC

- reply

Look like internal state issue, I will look into that. If no major crash issues, I will release a stable version next week

2026-06-03 02:15:39 UTC

- reply

Hi @npub1msd…meds
Can you help me test this build? https://git.reya.su/reya/coop-mobile/releases/tag/v0.1.5
I've added a proper screen for crash report, so you will know what's happened

2026-06-02 05:56:52 UTC

- reply

the chip is ok, but windows is hot garbage

2026-06-01 03:02:52 UTC

- reply

I'm also sent a message to you (nip-4e)

2026-05-29 09:36:12 UTC

- reply

Okay, I think I've found the problem

2026-05-29 07:52:06 UTC

- reply

Hi @npub1msd…meds
I've pushed a new build, let me know if the app still crashing on startup. The next build will take a bit longer but will be the stable one, I'm also publish it to zapstore and playstore
https://git.reya.su/reya/coop-mobile/releases/tag/v0.1.3

2026-05-24 23:17:00 UTC

- reply

Yes, I've received your messages

2026-05-24 10:10:18 UTC

- reply

Yes, I'll published it to zapstore later

2026-05-24 07:54:02 UTC

Yo, if you're bored on the weekend, please help me run and test Coop (NIP-17) client for Android:
Download here: https://git.reya.su/reya/coop-mobile/releases

2026-05-20 08:57:24 UTC

- reply

it's fucking hot at my place (SEA) 🥲, so I want to travel somewhere

2026-05-20 08:43:46 UTC

- reply

how’s the weather at your place?

2026-05-20 05:32:06 UTC

Sorry, I'm kinda wrong here, the stream events API is fine, but the problem is the negentropy part in gossip. After removed the negentropy sync and force to use typical stream events API, gossip is became very fast.
Other temporary fix is set timeout for gossip sync very low like this:
```
GossipConfig::default()
.sync_initial_timeout(Duration::from_millis(100))
.sync_idle_timeout(Duration::from_millis(100)),
```
So I think we should have an option to disable negentropy, also I think it will better if we have an API for client dev manual run gossip fetch for a Public Key
cc @npub1drv…seet , @npub1qqq…ln03
#nevent1q…45wk

2026-05-20 01:34:16 UTC

Hi @npub1drv…seet , cc @npub1qqq…ln03
I wonder, can you add an option (new feature) to enable this kind of behavior for the Pool stream_events API?
Detail:
- With the current behavior, stream_events API connects to all relays, then waits for the result of each relay, then collects and processes (de-dups, forwards, etc.)
- This behavior leads to very poor Gossip performance, users usually wait too long for the results because of the multi step stream_events calls
- When a user calls stream_events with a Filter X, the SDK breaks down the filter, then fetches the NIP-65 relay list (with stream_events), then connects to those relays, then fetches events by Filter X again. The problem is the SDK waits for all relays to complete, as described here: https://github.com/rust-nostr/nostr/blob/17470cb551e9e359d0a7cde7ef5e1564627c8f91/sdk/src/pool/mod.rs#L864
Proposal:
- stream_events will have an option to return early when the first result is received, without waiting for all relays
- When gossip is enabled, stream_events will always return early
- When returning early, other relays will automatically unsubscribe

2026-05-17 11:44:55 UTC

- reply

thank in advance

2026-05-17 04:17:13 UTC

- reply

i love the onchain zap. i have never seen anything this magnificent in my life, we just send bitcoin to each other

2026-05-17 03:49:28 UTC

@npub1drv…seet all latest changes in rust-nostr are insane, i'm going to fully rewrite my app 🤣

2026-05-17 03:27:25 UTC

kotlin is more enjoyable than rust

2026-05-11 00:15:58 UTC

Progress:
Coop (NIP-17 client) for Android. Fully adapts Material 3 (Expressive), built with Kotlin Multiplatform. Still WIP, but I've made good progress, maybe a release later this month.
About the features, I want to keep Coop simple, a dumb app just for messaging, so it will only support NIP-17 and NIP-4e later, nothing more.
Thanks @npub1gcx…nj5z and @npub1drv…seet for helping me.
https://video.nostr.build/4efafcb39db983487d5689ce982006c80fe78688a510d49af923b9fe344568a8.webm
#nevent1q…vfmy

2026-05-08 09:51:56 UTC

- reply

You can try run my project: https://git.reya.su/reya/coop-mobile/src/branch/develop/
it is very basic app, didn't have much code for now, and it run on a my fork of nostr-sdk-ffi, but it almost same as upstream (I only add more functions)

2026-05-08 08:54:41 UTC

Hi @npub1drv…seet
I've found a weird issue with Nostr SDK FFI for KMP. I've added relay(s) to the pool then connect. But when I subscribe or send event, the pool always empty, I also have tried get all relays from the pool by `client?.relays()` but it still empty. Nothing weird in the logs either (relay connection then relay connected).

2026-05-08 03:21:37 UTC

the new website is cool
#nevent1q…wnyu

2026-05-05 02:39:43 UTC

I spend 1 hour just to import a fucking icon to android studio

2026-05-04 11:24:28 UTC

After two weeks of learning kotlin, I can now read the amethyst codebase

2026-05-03 07:17:04 UTC

- reply

i still here

2026-04-30 08:54:50 UTC

- reply

Do you plan to support git grasp?

2026-04-30 08:35:23 UTC

Yo. Remember Nostr Connect (web extension) that was designed by @npub1r0r…q9ac . 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/23433d65ee7528a36bae8721f761f200274d98f4ff4d8fd76375ea6090866e68.jpg
https://image.nostr.build/cb9e1527807140989ce32781f907a5e97c3ed04f4b3cff9b2d5575daf49f8cbd.jpg
https://image.nostr.build/bef9b175aa53b62b417a18d2caef466d78486203d3cb350cc250846989502f01.jpg

2026-04-30 07:34:25 UTC

- reply

Yes, I've forked and added two functions: `send_event_no_wait (ack policy none)` and `send_event_to_nip17`, these are only stuffs I need

2026-04-30 01:30:14 UTC

- reply

And look like the APIs are a bit inconsistent, sometimes I see EventTemplate<...>, sometimes I see a brand new event class like AdvertisedRelayListEvent , naming isn't consistent too, likes createNew/create ,...

2026-04-30 01:20:06 UTC

- reply

I think a option to chose specific relay list when publish/subscribe will be nice. Like:
```
client?.publish(event, Target.NIP65) // publish to nip65 relay list
client?.publish(event, Target.NIP17) // publish to nip17 relay list
client?.subscribe(event, Target.Custom(setOf...)) // publish to custom relay list
client?.subscribe(filter, Target.NIP65)
...
```

2026-04-29 05:27:39 UTC

https://keepandroidopen.org/en/

2026-04-29 03:50:35 UTC

- reply

Found it: https://github.com/vitorpamplona/amethyst/tree/6c8c5eb7a5a0cf76c1c07d1aeaa4836fe10487f9/quartz/src/commonMain/kotlin/com/vitorpamplona/quartz/nip01Core/store/sqlite
I think its have all I need

2026-04-29 03:33:32 UTC

- reply

Oh, I will check it, the section in README a bit outdated. But look like Quartz isn't have cache layer yet, so I need to handle it by myself?
My current design is (taken from desktop app): Open app -> Set signer (login) -> Get user's nip17 relays -> Get all gift wrap events from those relays -> cache all events in database -> send a signal to update the UI

2026-04-29 03:14:00 UTC

- reply

Hi @npub1gcx…nj5z , do you have any docs for quartz, I tried use it but a bit feel lost 😅

2026-04-28 08:16:26 UTC

I think I should use quartz (from amethyst), it's more mature for KMP

2026-04-27 05:29:48 UTC

Hi @npub1drv…seet
I'm using Nostr SDK FFI for my KMP project. I wonder do you plan to adapt the new API changes on the master branch for ffi anytime soon?

2026-04-24 22:48:55 UTC

- reply

I think the sidebar has too many menus. We should show only 3-4 menus, and place the rest under "More"
Also, in the message list, it would be nice to have an option to hide the last message displayed below the user's name. I don't want others to see my last message.

2026-04-17 02:25:29 UTC

- reply

pfp should below 500kb

2026-04-14 12:45:29 UTC

- reply

second retard company (microslop the first anyway)

2026-04-14 00:48:22 UTC

- reply

most retarded company

2026-04-10 09:47:06 UTC

- reply

Yes, you can try Coop, and beta.jumble.social also supports NIP-4e. Before you try, I've changed the direction of Coop (desktop) to target advanced users, while Coop (mobile) is for onboarding new users. Coop (web) is planned, but I'm not sure how it will fit.
Regarding Nostr Design, I think it's hard to follow the recommendations because everyone has different tastes and different approaches. However, the recommendations still contribute greatly to helping devs make decisions. Also, it's nice to have someone check every corner of the app, as devs might realize what they've missed.

2026-04-10 06:57:20 UTC

just found out that https://github.com/dmotz/trystero is using nostr

2026-04-10 02:27:03 UTC

- reply

i love yuri