Event JSON
{
"id": "9a99f37100a32688e668815b189f939f8aacdd7319f589f4c957bc61ae6694cc",
"pubkey": "8e02cd7b480b23cf7d1e13800e3056447fc63a62a5c9336e29e689ec6b8ab4ed",
"created_at": 1688307203,
"kind": 1,
"tags": [
[
"p",
"4c239a2ce6750f1924717c5991ef50fed16bbfd75b3fdb29f9d82f45ade77512",
"wss://relay.mostr.pub"
],
[
"p",
"1dbb334410672477ad84d68e8ed95f8a84cf004fd3b09d6aafdb61efbbb1927a",
"wss://relay.mostr.pub"
],
[
"e",
"eca005a82483965c5ee736abdb0f61590a0d608973c8b647d03610a00db80cef",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://vis.social/users/wcbdata/statuses/110644900904833128"
]
],
"content": "nostr:npub1fs3e5t8xw583jfr303verm6slmgkh07htvlak20emqh5tt08w5fqhuwylg In my experience as a data modeler, geopolitical hierarchies are single-use, temporal things. They work for the one purpose they were built for and almost immediately develop a breaking exception. I've only been successful modeling them for long-term use as a quasi-graph using a thing/thing-relationship/relationship-type model where multiple types of hierarchies can exist.",
"sig": "82bea4d51642afccc91f526ec3893ec98741591976b3a2368bf1887bd448a542400864a567119e27c301d048f0a1355cfebeb6a426fc228bccd39610dfd2b743"
}