Nostr Web Client

nostr:nprofile1qqsdy27dk8f9qk7qvrm94pkdtus9xtk970jpcp4w48k6cw0khfm06msppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz7zvqagl instead of a GUID why not use an npub and store the encrypted chat history on nostr?

PayPerQ 4mo ago

We have thought about this idea, and we've also thought about just encrypting things client side and storing it on our own servers. The last idea we had was to use passkeys as well which seem to be the best idea of them all currently.

The problem with the nostr idea is that it, for maximum convenience, requires that the users have some sort of nostr browser extension which probably only applies to 20% of our users currently.

Also, is there even a nostr note type for this type of encrypted data?

Passkeys on the other hand are supported by most modern browsers and so should work immediately for most, if not all of our users.

But tbh we are still exploring the different options and not sure which one is indeed the best.

But happy to increase the conversation here.

Reply to this note

Please Login to reply.

Discussion

Freedom Tech Co. 4mo ago

Yes, you can use kind 30078 with "ppq + thread id" as the d-tag

passkeys suck because you lose the device, you lose the account

We agree that browser extensions are bad, however nostr wrappers such as keychat and fedi go a long way to fixing this

You can also use Amber or even a hardware signer

Given that queries are often not sensitive, there's also an argument you could generate a local keypair, or accept a raw nsec. It's a start, at least, and would allow accounts (and history) to be shared, eg among a team