second thing that i see thanks to having my relay to test it is that it doesn't respond to nip-42
so, yeah, i'll be looking at this app closely it has some good ideas in the UI design, but it's really minimal at this point
Discussion
I don't call it ugly but yes it's very minimal at this point.
The whole point of Nostr is that different platforms can have its own best client implementations for Nostr features.
Therefore, one client should just focus on one platform.
https://blowater.app is always a desktop client which happens to be able to render on mobile web, partially.
NIP-42 is intentionally not in the scope of this client because it was never the design goal of the product.
Not all NIPs are suitable for all client. The design goal is important.
lol
it took me about 2 days to fully implement nip-42
can you explain to me why you and the rest of the dev community don't think authentication matters? in english?
i heard someone say a while back that it "only mitigates some metadata leaks"
bitch do you not understand what the fuck that means exactly? how about this pesky thing called a "replay attack"
i am very sad that you all are so fricking stupid that you don't think authentication is important
it's like 1999 and nobody has SSL still, and we are using MD5sum to generate password hashes
yeah, i can't use your chat app with my nostr.wine relay that i pay for because it requires NIP-42 (just like my relay does, when i set the config that way, i just made a bypass for IPs due to the fact i use it on a VPN and it can filter for that)
well, not that i have any chat partners that use nostr.wine but if i did, i would know that our chat metadata wasn't leaking
you really need to think about that, it's really starting to grind my gears how nostr client devs are so bleeding oblivious to the privacy implications
are you TRYING to leak all our comms metadata to the spooks or what?