Event JSON
{
"id": "16615c89017ed4867ee4b5e13104dd5548c48c58f201b1e8633ac50fd34b814e",
"pubkey": "c8d5a41d8a4341c35896ac790dfede47417fe5e70c7c7fb63f6a5ba0d08359f9",
"created_at": 1740471581,
"kind": 1,
"tags": [
[
"p",
"ff479c63a264a52994dec047cff0c7fdff88ccba2ffb152705d7dba3e31266bc",
"wss://relay.mostr.pub"
],
[
"p",
"e9c3448952ee9b09ac0c9a13e32b32f20358814e3e4f4fa666064d00361f0eda",
"wss://relay.mostr.pub"
],
[
"e",
"9619299e5bfe1702d4b136715cc1e26d578caba764ed914d061efe9d547ea2b1",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fluffytail.org/objects/04a48d4a-b80e-4f8c-8bbe-93ea8d81641a",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqlareccazvjjjn9x7cprulux8lhlc3n969la32fc96ld68ccjv67q5a3hg5 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqa8p5fz2ja6dsntqvngf7x2ej7gp43q2w8e85lfnxqexsqdslpmdqtcmsu3 Postgres and the kernel will figure that out, it's better not to fight them and just leave them do their own thing with a proper config in Postgres (shared_buffers, effective_cache_size and a few other settings). Postgres always caches data that it's currently processing and the kernel puts frequently requested disk data into the page cache.",
"sig": "4b925d34274215fc395ce278c915cc74e0801bf1d182b7c3b95f4115ee53b6b2260afb6312cf75954eb8d9cbb832aef23e6fa8e79858cf790525f428798d1e1b"
}