Event JSON
{
"id": "63f5c8106d5b0f0127619c4719c845c6001b6007b878a4c201d08e651d873efb",
"pubkey": "e808f10f5fae6f883a51f4bbc49f7da721701a853f8bddc5b948071f4d7d5229",
"created_at": 1709011965,
"kind": 1,
"tags": [
[
"p",
"4ebb1885240ebc43fff7e4ff71a4f4a1b75f4e296809b61932f10de3e34c026b",
"wss://relay.mostr.pub"
],
[
"p",
"8b0be93ed69c30e9a68159fd384fd8308ce4bbf16c39e840e0803dcb6c08720e",
"wss://relay.mostr.pub"
],
[
"e",
"5ca975c00c9c8c4fc6d79232bc8b391aa4bf692c7c30f7f6be35f13f040be704",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://phpc.social/users/lewiscowles1986/statuses/112001808158997745",
"activitypub"
]
],
"content": "nostr:npub1f6a33pfyp67y8llhunlhrf855xm47n3fdqymvxfj7yx78c6vqf4scxpnql Perhaps of interest. If you track record (row) history using JSON, you should try to track a migration identifier for the database or the table as well, so that if the schema changes, you can apply a strategy to \"rectify\" records, before applying the change.",
"sig": "f2b61b8485a757bd0c40524a6fca607843d7a2f83d08ec0e0d886323797bd7cbe99f0c89162afc88b286aaeef07006f89aff5c787271edd997c0bd754a7728c6"
}
