Event JSON
{
"id": "a9e8e15209c981046c76da2ba33f1d536a922a7ccbe3d8753390c81fabcd85a3",
"pubkey": "a9b788528b0fc4650dab10e486c86c151dde0cdf5fa87ce5be30c6472cc10fc5",
"created_at": 1693087700,
"kind": 1,
"tags": [
[
"p",
"e2bc32de32285830ffa94c3619e8a7c9cd7df0176a306fb59af777b07ca1e6e6",
"wss://relay.mostr.pub"
],
[
"p",
"ec55841e6b607007a0167bd7e8d844705669336aef56485b48f4d38f51e5f68d",
"wss://relay.mostr.pub"
],
[
"e",
"c544b3a2458977ec431a930a5dc25b7bd984852f98de8c6be70fc0f90dacc674",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://hachyderm.io/users/hrefna/statuses/110958195552372853",
"activitypub"
]
],
"content": "nostr:npub1u27r9h3j9pvrplaffsmpn698e8xhmuqhdgcxldv67ammql9pumnqha3qfq Honestly? \n\nI'm going to keep repeating dret's point: https://dret.typepad.com/dretblog/2015/02/json-or-rdf-just-decide.html\n\nWe need a metamodel. \n\nWe need a way of:\n\n1. Describing extensions (and in the case of AP… core features, like \"what the heck is a user\")\n2. Handshaking on what extensions are supported.\n3. Saying what to do if an extension is not supported. \n\nIt's too easy right now to write something that is incompatible with the universe but that strictly follows the spec. Compare with, say, the situation with HTTP.",
"sig": "40bbe65531c3d0d529bfc24aee70e8f646aaa3f371dee3c18729e3bf207d4d8afda90b432b98de1637237ee4a9252920d40333f3dba67d99db5b48c38cb9078d"
}