Event JSON
{
"id": "b7557109280029e8c543742ad7e7f5d76cb8105bda6213f9a88f5a622bea800e",
"pubkey": "5c931aab4bd50aef18e4fd6a257cb53bb70fee015066bea9102ac27a8e230f5c",
"created_at": 1739289122,
"kind": 1,
"tags": [
[
"p",
"02d2c68f7c236a687ff8a596099af9a535b513fad04d6ed961dcec55246bff3c",
"wss://relay.mostr.pub"
],
[
"p",
"8671184c76e0cf3c8c9a785cdde1fd132e318e4a14c2a5cdfdb93de4eb16643f",
"wss://relay.mostr.pub"
],
[
"e",
"54aabd522de45b095db143fed58a58420ee105c7adda45d007269d4c70952802",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://ruby.social/users/Schneems/statuses/113986051939039191",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqqtfvdrmuyd4xsllc5ktqnxhe556m2yl66pxkaktpmnk92frtlu7qtcp3s2 I think my regex code is probably just as robust. This definitely isn't a supported use case. Of serde_yaml, and is for sure an abuse of these trait bounds. It works...but it also might break in unexpected ways. \n\nMaybe opening up an issue and asking for a supported way to read multiple documents, possibly behind a feature flag. Or maybe there's already an issue on it.",
"sig": "39b216de23c85b921abb30f13513223c61301df29a8c532b007f1d84823a2b390bf76940df9dd7892add147e1fe5e783888f1fc4f44079c75fd14c0ac3bbc57c"
}