Event JSON
{
"id": "788503d4a180e5c9ba76d4b02d1552ae0e498ab814b33333865fca92d8012392",
"pubkey": "04bde9bc1796555bc64e118086e3a6ef812bb32a0fac0abc58623b9ef0ca22de",
"created_at": 1691686327,
"kind": 1,
"tags": [
[
"p",
"d14fc624d008b2b16eb2fb68a50c21b917874a2c5410f988ba14d87b6b3e7ee0",
"wss://relay.mostr.pub"
],
[
"p",
"3c8238d85e7563b9e9152b46823591af66320c0513a9da3d487e2df6b972aeb3",
"wss://relay.mostr.pub"
],
[
"e",
"a6894d89fd540fd296786d94b1cf098550fdc685b5f60b2b3f42b85b4e377819",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"nostr"
],
[
"proxy",
"https://openbiblio.social/users/steffenr42/statuses/110866355130586301",
"activitypub"
]
],
"content": "nostr:npub1698uvfxspzetzm4jld522rpphytcwj3v2sg0nz96znv8k6e70msq7jhmgt Why linked data in #nostr events? As more clients for same use cases evolve (which is kind of emphasized through the protocol) we will have a problem understanding the metadata all the clients send. I want to use linked data to make that data understandable for different machines and clients",
"sig": "f03ae3ec215ad1b7900e92490134d11b631f7356d956cba969b62423a63f3d601f2779355fc03a0894006d2cad7957afa428d55658c85aed35a2f5db12ff683a"
}
