Event JSON
{
"id": "5e81b5ffad2845d952ed02bec455ff466c5483b21a054bc975373c7093559f50",
"pubkey": "b7f4998efbebfd0d675e0671c492f7610c7cef16e7619798bc7e7611cbeb10c6",
"created_at": 1733210006,
"kind": 1,
"tags": [
[
"p",
"6a912725c67a36f1ddb9c39c958841c3f7cca97401c6afed602d7d6dd93dbc93",
"wss://relay.mostr.pub"
],
[
"p",
"b537dcd0f34fbdafbe55ff5a6a5275120dee94022e852a2d6a03cee99e6e7a6d",
"wss://relay.mostr.pub"
],
[
"e",
"353a2c030d99642e7ca270c86f05368d1d66b6b4d0fd07a52dbf9b6b6bcb4358",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/jonocarroll/statuses/113587651015490353",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqd2gjwfwx0gm0rhdecwwftzzpc0mue2t5q8r2lmtq947kmkfahjfsf6u4p8 Interesting, I'll check that out! In terms of format if I was building it myself, I'm tempted to use something like Datomic https://www.datomic.com/benefits.html which stores as EAV+T (a triple plus a time); very amenable to semantic triple processing, but it's unclear that it needs to be that powerful. Certainly, management of this is additional overhead, but aims to solve a problem.",
"sig": "66fa1e8722a839f39c761965d9a9f41132d19a387500c0025d050886fbe721ca598df926fc34c6cc95c2eb844f74c37ee0249b46c42197a0a6fa255167640234"
}