I didn't have experienced with any kotlin or java projects yet. Maybe I will learn it in the future.
Building GTK4 app on macOS is wild π€£. 
Yo, I've pushed a new version which also added native notification as well as fixed some bugs. https://github.com/lumehq/coop/releases/tag/v0.1.6 . Thank fiatjaf for reporting a lot of issues.

Yes, I have notice this issue too, sometime new event isn't emit to the frontend despite send or received successfully in the backend.
I've pushed a new version for further improvement https://github.com/lumehq/coop/releases/tag/v0.1.5
Hi, can you help me try the latest version? you can download new version here: https://github.com/lumehq/coop/releases/tag/v0.1.5
Ah, I've found the problem. I will patch it in the today update.
Oh, what is distro you're using? I will install it and dig more on tomorrow.
Ah, I forgot to add the README π€£
I will add it when resolve some feedback from users on tomorrow.
Oh, can you help me add the flag WEBKIT_DISABLE_COMPOSITING_MODE=1 when run app? I've found this bug on tauri not sure it related to your issue https://github.com/tauri-apps/tauri/issues/5143
Oh, I will add some reload mechanisms, instead of stuck like which is bad. Currently, inbox relays only fetch once and save in cache without any reload method, user need to restart app to reset.
Thank for your suggestion. I'm working on it, my network is super low at night time maybe I will push new release on tomorrow.
Oh, coop only have 2 relays to get user's kind 10050, which are relay.damus.io and relay.nostr.net. Maybe your relay list isn't published to there. I will push a update to let user config the default relays as well as change the default relay set to more popular relays or just use some bostr relays too.
NIP-17 deploy in progress.
nostr:nprofile1qqspycgrhlwu3he9ddhq407h7duheqxucn4g3a7zlp7agyzzyz6dvhcpzemhxue69uhhyetvv9ujumn0wd68ytnwv46z7u5fdt3 any plans to add NIP-29?
Yes, but in long-term. I want to focus on NIP-17 first and make it stable before add more features.
I am happy to announce that my little chat app called "Coop" based on NIP-17 is ready to use. It still lacks features and isn't anything fancy, but you can have a simple and stable direct messaging experience (at least on my computer π ).
So, please help test it, and then I can make more improvements.
> Download: https://github.com/lumehq/coop/releases/tag/v0.1.4
> Some informations about Coop:
Coop does not support login with Nostr Connect (NIP-46) yet, but it still treats your secret key securely by only saving an encrypted version of it (NIP-49) on the OS's Secure Keyring.
When you send a message to other users, Coop only send those messages to user's inbox relays and backup version of it to your inbox relays.
> Roadmap:
My initial plan for Coop is fully native based on Rust, but I have to back to Tauri because skill issue. But I'm not abadon it, I will release other version which fully native on the next major release.
Many thanks nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet for rust-nostr and help me debug tons of issues.

hmm, I not use egui much yet to review it, but egui is more mature than gpui, and well supported too. My only problem with egui is it hard to create native looking app (it not egui goal anyway π )
I wonder is there a way to make remote signer (NIP-46) more efficient when unwrap a gift wrapped event?
Imagine, I've 1000 gift wrapped events, to unwrap it I need to decrypted it with NIP-44, but it require permission from remote signer, so it will ask remote signer 1000 times to allow it, it will very slow.
#asknostr
nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 One problem Blowater has is that it heavily uses IndexedDB which is slow and has horrible APIs. As much as I can optimize it, itβs a bad foundation to be built on.
I believe your investment in native desktop technology is very worth it in the long run.
Web is very good at presenting / displaying things but very bad at everything else. Tauri is a good approach. We can use Rust to implement a performant storage layer.
I look forward to see what you make with Coop
I'm working to few improments, and release a stable version for Coop in this weekend.
My initial plan is use Native GUI instead of Tauri (webview), but I came back to tauri because my rust skill isn't enough to do it π .
My only problem with tauri is it heavily depend on gtk3 on linux which quite old, and I found some native features like context menu, tray,... isn't work well on wayland. It also doesn't provide much API for custom window like macos or windows.
In the long term, I want to do everything in Rust, so I can have more control in the quality without depend on 3rd libs.
my target stack:
- backend: rust-nostr
- db: nostrdb or sqlite
- gui: gpui or xilem, florem
I'm testing with English, maybe all chat app I used is set self message on the right so I already familiar and feel comfortable with it π€.
I've tested this issue when building my chat app, I see my message on the right is more comfortable than the left π€£. idk, but it feel more natural.
nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 how's your progress going for Lume 4.0 for Windows and Linux?
Hi, I've generated a version for linux and windows but it still have a lot of bugs, since I didn't have linux or windows machine, I cannot work to fix it yet. But I think it will be hard because I use a lot of experiment code and it only work well on macOS.
My current plan is release a stable version for my little chat app (NIP-17) in the weekend (you can try unstable version here: https://github.com/lumehq/coop/releases). Then next week, I will buy a linux laptop to working on a Mini version of Lume for linux (maybe windows too) only. It will extremly lightweight and simple to focus on social network only, something like https://tuba.geopjr.dev/ but for nostr.
Can't launch on Windows 11 23H2(22631.3880)π€·ββοΈBut it works in my Windows sandbox(22H2, 22631.3880), I suspect it's a problem with the WebView2 Runtime (it's not pre-installed in the sandbox). https://media.naeu.net/7cb057642351ffeb25f7857ccc932a1bfd07e058e81d2e79ecc7f5c90b69b220.webp
oh, let me check the tauri config, I think it should have by default π€
I just found a best nostr client https://jiftechnify.github.io/motherfucking-nostr-client π€£
Yo, I've pushed few changes to make Lume run on Linux and Windows again. If you have those device, please help me test it π. My PC is broken, I cannot test all functions yet, but it should work fine, maybe have some UI glitches.
My chap app is too bad so I end up rewriting it again. π€£. I cannot make it fast, something serious wrong with my code.
If you want to test, you can test current app build with Tauri here: https://github.com/lumehq/coop/releases. In other branch, I'm using Freya GUI which is faster but it not ready yet.
I've spend almost 3 weeks but my simple chat app isn't work well π
Oh, I've received bitkey in my country. I think they already ship outside US π€
Update: I ended up rewriting my chat app π₯². Fully GUI with Rust is harder than I imagine, but I'm not given up yet. I still want to release it this month.
Ah, I'm using freya which use skia for rendering. it lack of features than tauri but smoother
Finally, I can make my chat app only using around 90MB memory. Seem doing GUI with Rust is good choice. π

NIP-17 describe: "Clients SHOULD publish kind 14 events to the 10050-listed relays. If that is not found that indicates the user is not ready to receive messages under this NIP and clients shouldn't try.". So I've added small panel in the message form to inform user.

