When we'll the first Nostr heavy client with Tauri?

nostr:nevent1qqsrmtfhcupqm9rvhjfuutq28d2mjvecwaqtd3s083a84wkwpnkl02gppemhxue69uhkummn9ekx7mp0qgsxh8dfyrztdm9l9sfqrzn6952rkn0alxrccwl2c60rnw6e0pqucmsrqsqqqqqptw24g2

Reply to this note

Please Login to reply.

Discussion

Hi, I'm working on lume, which powered by tauri and rust-nostr https://github.com/lumehq/lume

Yes I know lume it's great! But I would prefer a more classical UI like Snort UI on desktop

And someday I'll get it to compile cleanly for AUR and BSD ports.

I plan to convert Blowater from a pure Web client to a Tauri app so that I can publish to App Store

I plan to convert Blowater from a pure Web client to a Tauri app so that I can publish to App Store

Can't wait! The blowater app is able to retrieve our Nostr Relay configured in our metadata or by default it's using blowater Nostr Relays?

> The blowater app is able to retrieve our Nostr Relay configured in our metadata

Not yet, currently I hand coded some relays into the code.

> by default it's using blowater Nostr Relays

Yes, by default it only connects to wss://blowater.nostr1.com

Blowater is never designed to be a social media client and never will. It's a Discord style client for communities & organizations. Therefore, relays play very different roles comparing to mainstream nostr clients.

Yes it's exactly what I (and we) need!

the only thing is if People we sent message are not connected the blowater relay, they won't be able to see the message but I suppose you also hard coded damus, nos, etc. relays.

> the only thing is if People we sent message are not connected the blowater relay, they won't be able to see the message

This is the current behavior of Blowater but it's never my eventual goal.

Delivery is a hard problem so that I intentionally sacrificed cross-relay interop for a smoother UX as a workaround.

I am working on better cross-relay interop. It just takes time.

There are several design problems I need to solve before addressing the cross-relay problem.