Event JSON
{
"id": "e273962d70e227f5b42b545db2122ebe9d8ff8a1fdad2d54e891dd6af45cd78a",
"pubkey": "fa8cd3ad8a0cf7b2bb853315a62b7dc9bfdd2a9bfe0906587166f174619b2b64",
"created_at": 1710847670,
"kind": 1,
"tags": [
[
"p",
"c0ee9edf77071dbc5337663bb44cd54ff4c9a9c1b64ecd8e3f75dca28906bb15",
"wss://relay.mostr.pub"
],
[
"p",
"75fa5eda0658be8c55dedc6227d53c02ff8fbadcd99981127dbedd55c0fd8704",
"wss://relay.mostr.pub"
],
[
"e",
"8ffbcccb8830afb8f7c872d50c1f2b79fa7f5d3ff81a6a6b98bd3ca2a0046c92",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://indieweb.social/users/janboddez/statuses/112122112932223093",
"activitypub"
]
],
"content": "nostr:npub1crhfahmhquwmc5ehvcamgnx4fl6vn2wpke8vmr3lwhw29zgxhv2sdhqpvp Yeah, I could've also applied `e-content` to the whole \"post content,\" but then some mf2 \"consumers\" would show, e.g., \"reply context\" twice. (If no `e-content` is present inside the post, like for \"regular\" articles, however, the entire post _does_ get an `e-content` class.\n\nOn-topic: some people use likes for quotes/bookmarks, but there, too, some mf2 consumers do not process \"like bodies\" (and instead treat them more like \"Twitter likes\").",
"sig": "33006789bd90fdbd2f5025c0b3bbb28987a37ea541e0fedb79c559999a4a17b7c422535e41da3d5c54298d8a84fd99bad5e4c21712bde9deb48375d5ec94ee92"
}