most trivial line-based formats line csv are actually decently self-syncronizing, so if the file corrupts, you'll only usually lose a few rows. most binary formats make heavy use of lengths and offsets, making them much more brittle.
usually this doesn't come up much.. unless it's something you only go looking for once things have gone wrong, like logfiles.
Lily /
npub162…e49jl
2024-06-27 21:16:51
Author Public Key
npub162yftstcc5pfsdukxp0whnamzk3s6dm85e3pzyw0tx25jaywjmnsje49jlPublished at
2024-06-27 21:16:51Event JSON
{
"id": "7f2b12eee09e030fe87fb6f716fa954e964973c1cc8fc42b06d70d0a8ab2fb8e",
"pubkey": "d28895c178c502983796305eebcfbb15a30d3767a6621111cf599549748e96e7",
"created_at": 1719523011,
"kind": 1,
"tags": [
[
"proxy",
"https://glaceon.social/users/lily/statuses/112690660104773909",
"activitypub"
]
],
"content": "most trivial line-based formats line csv are actually decently self-syncronizing, so if the file corrupts, you'll only usually lose a few rows. most binary formats make heavy use of lengths and offsets, making them much more brittle.\n\nusually this doesn't come up much.. unless it's something you only go looking for once things have gone wrong, like logfiles.",
"sig": "83b2954f47963d8f23107465ec045b927024b839eb98f764ff7a194fd4f62d0ee06269e96db2f264a59aba274f5637e624d7b5f09f8b2f1fa3abd4e4c8d461fc"
}