It's night.

How will they train AI to answer new questions if those questions are not being asked to the right people?

@nevent1qqs...

Make art.

We we cannot afford to be without protection.

💯

The more try hard idea would be taking frost and extending its Shamir Secret Sharing foundations to do signing, encryption and decryption like they do in other threshold cryptography schemes like BLS (just haven't looked into if these schemes are as secure as frost over repeated use).

https://iancoleman.io/blsttc_ui/

It's definitely not straight forward. I been thinking about doing something like musig(frost-2-of-n-coordinator-keys, frost-1-of-m-user-device-keys).

Where the 2 of N coordinator keys would generally be a mix of the user key, and selection of coordinators (the higher the number of coordinator the more likely a user can move coordinators if ever the need arises).

The user device keys can be as many devices as a user wants (they only need one online device to sign a message, assuming that device would be the one they are currently using and that the user can securely use the coordinator to manage device keys).

You can probably do Distributed Key Generation on both the coordinator and the device frost keys if the clients are compatible. I think nip17 is quite ideal for ChillDKG.

Ever considered using Frost to aggregate the device keypairs (with the added benefit of enrolling new device keys, or removing old device keys, later while keeping the same aggregate pubkey)?

The user encryption definitely needs to be decoupled.

Pass the aux!

@nevent1qqs...

Scary.

An http based nostr relay.

Everything is culture.