Event JSON
{
"id": "6d1135491ef13e69a1ef5204943a0d139a95df2f611f3f80d0a9dfe21afdb7cd",
"pubkey": "6d994b5e4875fa6b675b50e708f431be1020aaf197b01d92068834d5bbc40673",
"created_at": 1692541660,
"kind": 1,
"tags": [
[
"p",
"7d199f2800dc8c279e16e6d5fb360505a5af68e56c9ce1abaf058665c237011a",
"wss://relay.mostr.pub"
],
[
"p",
"678fbdf04a787406ea6ccc5fd35c1cf57ac74ea9d0aa81df88f7a941f57e75e3",
"wss://relay.mostr.pub"
],
[
"e",
"334e5d9bc54a011c9e67a4ef4fe64aacf5da112855721a4e3de825733ab4f925",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.vivaldi.net/users/firebreathingduck/statuses/110922410265033111",
"activitypub"
]
],
"content": "nostr:npub105ve72qqmjxz08skum2lkds9qkj67689djwwr2a0qkrxts3hqydqm9hk8p \n\nthanks, that makes sense. \n\nBut you still run into schema inflexibility risks with natural keys, right? What if a URL moves, or a customer changes their name after a divorce, or a product gets renamed, or a key that was implemented as one field now needs two?",
"sig": "e696f9bcc9e6970898ce506e566af3e2bfe842d0ee2b4db6996e55ec476b28cccce5a3e9724548c718a64ebe4f6691979bfc03c951f744609c11263d23bfae77"
}