Go to https://blowater.app and play with it. I will zap anybody 2100 if the issues is not duplicated from current GitHub issues.
I have 42K to zap. Valid until Sep 15th.
Discussion
Its not really a bug, but do you plan on supporting NIP-65 with the inbox/outbox relay model? I love your client but its always missing DMs because I don't use the damus relay and some of my DMs are on other relays
Good question.
1. Blowater's relay list can be modified and sync across device.
2. It uses a CRDT approach which you watched last week. It is not compatible with NIP-65 and is more stable than NIP-65, meaning other client can't mess it up. I will draft a NIP to let more client adapt it.
3. Yes, Blowater should somehow discover a npub's relays in a "smart" way, be it NIP-65 or other methods. Then the user can choose to copy these discovered relays to Bw's relay list.
NIP-65 is a little more than just relay list syncing, it includes the inbox / outbox model (I think everyone calls it the gossip model) https://github.com/nostr-protocol/nips/blob/master/65.md#motivation
To summarize, the idea would be to send the DM events to the other users "read" relays so that you can be certain they will see the event.
The CRDT approach your using probably works better for relay list syncing, but I don't think It would work for the above scenario since the events are encrypted and other users could not read them. and therefor would not know what relays to send the DM events to.
All that said, send me a DM or let me know when you have something written up about the CRDT approach. I'm really interested in learning how it works
I will put this under "relay discovery" feature set.
Voy a probarlo y que más hay que hacer
Se ve muy cómodo y amigable
On Android, Firebox and Chrome "add to home screen" supported.
On iOS, Safari "add to home screen" supported
I used it yesterday and it worked great
your zap is very fat recently
Just connected to play around.
Slick UI, simple to use.
I don’t understand one thing:
One tab for contacts and one for strangers, but in my case they are mixed.
Not sure how, but it seems the recognition/identification between strangers and contacts could be improved.
Gorgeous UI, first off.
When you go into Settings, the bottom nav disappears and I don’t see an intuitive way to get back to chats?
It just appeared after swiping around a bit, so maybe it just got sticky for a minute 🤔
Also, I would consider removing the “input your private key here” section and only allow login vi extensions or creating the account directly within.
Private key into web browser is not practicing safe nsecs, and I feel like it shouldn’t be encouraged. Not a bug, but an opinion 🫡
The question comes down to: web extensions are just another web page so that the security level is the same. It comes down to whether you trust the app or not.
The problem on mobile is that there is no extension.
I thought there was a bigger difference, where an extension only saves the data on your device and the web page has more vulnerabilities or ability to leak data.
I don’t have the technical background to claim I know - this is just the impression I’ve gotten from many previous discussions on and about nostr
Extension is really just another web page with more system privileges than normal web pages. It can communicate with servers and peek your current webpage’s data without your permission. From this perspective it’s less secure than a normal webpage.
The narrative on Nostr is if you centralize your private key risk to a single extension that you trust, then you don’t have to trust individual Nostr clients. Meaning you still need to pick one extension that you trust. Extensions are not intrinsically safer.
Thank you; that makes sense. Those extended permissions are why I’ve still never put my primary nsec anywhere besides the client I generated it within. And I only add extensions to a browser other than the one I use for day to day use.
Appreciate the thoughtful reply 🙏
You are welcome and your secuirty awareness is very good.