Event JSON
{
"id": "587b0ff150ede8df399e43f473231c5b20017f277a980bb27efc8202bbf26035",
"pubkey": "a321d92ec4dda29f257cddf8132129838ba706bab3aa6b29d382b41d058f06ad",
"created_at": 1738901036,
"kind": 1,
"tags": [
[
"p",
"8f910207a53f763abc174e9aa3881555c6304e4fa6cdbb1c36d97afb96aea63c",
"wss://relay.mostr.pub"
],
[
"p",
"e2946e52d0c37ca43b2bf823a5bca504559ff43beea7113ac0568033e698b069",
"wss://relay.mostr.pub"
],
[
"e",
"80abc79615fb95d86aad5a9a34a0e8615108061f38471d56d089a2c0320e3446",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/sushee/statuses/113960618332080956",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq37gsypa98amr40qhf6d28zq42hrrqnj05mxmk8pkm9a0h94w5c7qgja46r next issue with vici/prom is that my observability data/telemetry moves in a different direction/usage/shape. it needs more statistics features, but also more generic database features, I need to align with other signals and so on. I'm leaning towards generic events atm, shoved into any real good database so in this discussion sqlite. but then \"meh timeseries\". postgres/timescale is \"mid size\" already.",
"sig": "f340821c84e571d0e4f963e088f54d1987890c0d7802cbc61a44b2d672d28ef67c82cc745b398f6a4011207f66e4c1a03faabe80b2788c39988bba5203d428a8"
}
