@reya
I build nostr stuffs
Relays (4)
- wss://relay.reya.su/inbox – read
- wss://nos.lol/ – read
- wss://relay.reya.su/ – write
- wss://relay.gulugulu.moe/ – read & write
Recent Notes
Yes, in no_std or WASM you have to define a time provider. You can find an example here: https://github.com/shadowylab/universal-time#with-no_std-or-wasm-unknown
The example just set a fake time, in ...
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
You can check the file here: https://git.reya.su/reya/coop/src/commit/fd32b8c0ce2348c046d7e458ce292270a6118260/web/src/main.rs
It should be fixed here: https://github.com/nostrdevkit/nostr/pull/1400
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
```
```
error: a time provider is required.
Use `define_time_provider!(YourProvider)` in your binary crate.
See: https://github.com/shadowylab/universal-time
```
Thanks, I'll fix this in the next few days
Did you work on it yet? I will look into it on tomorrow and create a PR
1
My DMs are totally broken on Nostr.
You can try Coop: https://zapstore.dev/apps/su.reya.coop
iOS version will coming later.
iOS version will coming later.
1
👀
https://npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac.blossom.band/0553ca223769272ee055085b7c52cce934d893e63bf402b2dde86b165da79f11.jpg
when I see an announcement like that, I highly suspect nothing burgers 🤣
1❤️1
Buzz is the AI collab I always wanted to see, but in the UI I hate the most (Slack).
What parts didn't you like about the UI? I'm just curious, because I'm building something similar and need more insights
2
It supports WASM, are you compiling it from macOS?
https://github.com/nostrdevkit/nostr/tree/master/crates/nostr#wasm32-unknown-unknown
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`
```
```
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`
```
We've removed it (getrandom + wasm_js feature) because in some context was causing issues (wasm32-unknown-unknown used outside JS).
You can solve the issue by adding the getrandom dep in your Cargo.t...
Look like rust-secp256k1 isn't support wasm either. Do you know other solution?
Hi @Yuki Kishimoto
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?
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?
7
I see Japanese users are very consistent in using Nostr everyday.
❤️2❤️1🤙1
