Event JSON
{
"id": "f824307136d441d6f075f345d2813b6b8f6c2210e131b3aef2b8df6b098282a7",
"pubkey": "34b41bee5569850f721c6d03563fdfa823ba89e95e7f3549e457d9b0edad6c98",
"created_at": 1709731091,
"kind": 1,
"tags": [
[
"p",
"db4d7eb854d5411342c8076e9d5e673e734bd8622dd76c57d4774fa8a2b27901",
"wss://relay.mostr.pub"
],
[
"p",
"dc1ed93111a65a07f1ad785022347f63ca274e6dedb05c2f520b840bce3e699d",
"wss://relay.mostr.pub"
],
[
"e",
"09d60c10e090f17304d72a1122cf8872bc2047798377d6d756e0c5ed80c254e1",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.lol/users/adam/statuses/112048936780914222",
"activitypub"
]
],
"content": "nostr:npub1mdxhawz564q3xskgqahf6hn88ee5hkrz9htkc475wa863g4j0yqs4745y4 I honestly think that it could have been a hardware issue with the VPS host itself — it’s the only thing that makes any sense. I think the upgrade (which was an in-place expansion of the allocated CPU cores and RAM) was enough to move the box off of the problematic stuff and onto something different. I could be totally wrong, though, but I’m glad that things are running buttery smooth now. 👍",
"sig": "7246202e7d06e017a71cedea4b152f28b312fa69e1c2499896d826ac75878ae0226d4e87a5bd0a0db961c547621b78c2f1b0989c3ddf595737e7c1e3088bff33"
}
