Share the code!

A Bitchat like app _without_ the chat, to push people to talk in real life: let the user to set some topics (e.g. nostr, bitcoin, pizza, weird-interest...), notify when two users with common topics approach each other, showing a personalized description to be identifiable ("yellow tshirt and sunglasses").

I tried again and Coracle now generated the kind:10063, but it didn't push it to all my write relays, chronicle.dtonon.com in particular. I found that chronicle didn't have the read and write flags in Coracle, only the DM one (weird, I didn't update my 10002 in a long time). So I enabled them in Coracle, but inspecting the sent event, I can see that it added the "read" flag (should be empty). I deactivated/activated the write/read flags again to force an update, that was correct. Then I updated again the Blossom list, that was now pushed to all my write relays.

Yes Coracle, and I updated the field. Weird, I will try again later.

I'm testing it using the web app. Problem: the kind:10063 event is pushed only to your cache server (wss://cache.primal.net/v1), but not to my write relays. Is it a bug or a wanted behavior?

How does it work? I added a couple of Blossom servers in Settings, I see a new kind:30078 event (preferences), but I cannot find any kind:10063 on my write relay.

Easy 😅 And you completely loose the resilient benefits of seeds.

Exactly. https://en.wikipedia.org/wiki/Method_of_loci

Fair concern. Just use generic topic and then expose the unacceptable opinion by voice, if it's the case.

Splitting a 24-word seed does not create two valid 12-word seeds, the checksum fails. And even if it were the case:

#single topic is absolutely valid!

maybe it could be a "no chat" mode available in Bitchat

Even with the best UI, storing many seeds (an well know format, easy to spot) is more complex than having one seed with a customizable additional layer of security. I repeat, for advanced setups, not the casual user.

I talked about stolen *seeds*. A passphrase can be memorizable, you can always store it securely in a password manager, and offline backup are safer since the format is not easily identifiable as is the case with seeds.

Good catch 👍 I don't know the current logic based on timestamps, could make sense using a setTimeout strategy to buffer the updates and wait a little (e. g 2 secs) before firing the final event?

Any client supports Blossom BUD-03 "User Server List"? https://github.com/hzrd149/blossom/blob/master/buds/03.md noStrudel fails to fetch the NIP-65 list and to set up the relays correctly, so I cannot test the "Media Servers" settings properly.

"I convinced Grok God Is real" An interesting reflection about scientific consensus. https://www.youtube.com/watch?v=ga7m14CAymo

Sure. But casual users don't use password managers, and if they do probably they don't have sufficient opsec and backup procedures in place. A memorable (easy to transcribe and store as well) passphrase seems a good starting point.