It could be a tactic, but it's a little depressing that people can be scared by Nostr.

what about retouching the White Noise website payoff to highlight Nostr? "A truly secure and private messenger built on Nostr, that’s lightning fast, infinitely scalable, and identity-free." PS: Cool graphics!

I was just checking this thing, but WN has no relay settings, probably for now it only uses an hardcoded relay. can you confirm and share the relay, please?

I get this error for a Whitenoise user: I created a circle using relay.0xchat.com, cannot I just message a npub without first adding a circle?

If I try to contact a Whitenoise user from 0xChat, he receives a NIP-17 message. Should 0xChat detect the compatible formats and let me choose?

Wait, is 0xChat already compatible with Whitenoise?

Sure, but you are still using more resources (from client and relay) than using a single event. What I don't grasp is this urgency to fracture the profile data, given its small size.

I used GBoard whitout network access (grapheneos setting) for months without any problem, you just lose the dictation. Now I forced myself to switch to FUTO Keyboard, it improved a lot lately and the offline dictation is really good.

I'm on Android.

> We might add an index list to send just the kind0 and kind 10002 there. Please not another event, we are scattering the basic profile config in too many places. Maybe adding a "meta" flag to kind: 10002 is enough.

I'm facing the same problem.

This is a great news, bravo !

For me it's not simplistic at all, actually it's the hard part that requires ad hoc optimization for each theme. From the preview I don't like very much the overall feeling, it remembers me a too darkened or really old/bad quality screen; but as usual, let's see the finished experience, best of luck with your work! :)

I never talked about following lists, these should stay separated, and maybe re-thinked to avoid the problems caused by the atomic structure. About memory usage, we should reason keeping in consideration the real sizes: an average profile with 10 relays takes less than 1000 bytes, and the client can easily discard the useless data from memory as soon as it has been received.