Event JSON
{
"id": "d29c7fe52a873d7e4d5b64d90bff084409d55875f9dbe4a807ae22710ebd9eb3",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1725556231,
"kind": 1,
"tags": [
[
"p",
"1fc6332450be3dbb03765ae3b232aefde598299bd6616f33225a422f5c681bd2",
"wss://relay.mostr.pub"
],
[
"p",
"ac73b96084985a6879169944a3ffedf6ab09597968729bd0a54ceb5eb15a6483",
"wss://relay.mostr.pub"
],
[
"e",
"d3135207d828dbab4a012c0e3dee8780fb2e1d5400fca025adfb826b2deda7d0",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/113086053162992584",
"activitypub"
]
],
"content": "nostr:npub1rlrrxfzshc7mkqmktt3myv4wlhjes2vm6esk7veztfpz7hrgr0fqrnqrnk regarding the negative time_t stuff. There's a bigger PR pending upstream, that addresses this systematically. That should ensure the issue goes away.",
"sig": "95edf28d603ae9da324b6e0e74244be92e17af82ffd27d207f474870cf37066a0b2fbaee2bbff78c403491a513a7b2ac8f7c3ba7f0d657fb98f1ff32dd6112aa"
}
