Event JSON
{
"id": "0074fe7ce88d352b3e2390be99a5c91ef326b5d90f550e164de71b8be4387b83",
"pubkey": "6acd3b439a624b8e095aa280bc9175731e16da08eeb7cfde730b8fcad4675783",
"created_at": 1698311400,
"kind": 1,
"tags": [
[
"p",
"d977399f08f0f05dd0877d84c4e0338781c4a01c83c7a1d9992264e37324a093",
"wss://relay.mostr.pub"
],
[
"p",
"ad79524db05f31433426ac484d9261c3199e2e408fa1c28aa6b730808699dc7a",
"wss://relay.mostr.pub"
],
[
"e",
"adf230b01429f20b8fe2e7f12de66666a5a506f39d6223ce3743778fe3289523",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://chaos.social/users/cy/statuses/111300535923848902",
"activitypub"
]
],
"content": "nostr:npub1m9mnn8cg7rc9m5y80kzvfcpns7qufgqus0r6rkveyfjwxuey5zfs76rl3e how do you tackle the attestation requirement? do you map the keypass container to the hardware? could there be some passkey services you will not be able to use keepassxc for? (and will keepassxc be FIDO certified?)",
"sig": "a1381ca66d57e2612a80b7b43c0c070724084bfbdec5f84f71daecdc3c6173a1422646c6336d64d066d917ee223f6501843635e360cc1dfe222e5cf02ba22cfc"
}
