Last time i ran into a deadlock i fixed it in like three or four hours. This is the exact kind of programming I'm best at, and it's with a project I'm familiar with and have used for 3+ years (without, i might add, any data loss or corruption so long as i ran fshalt, across at least four machines).
Fossil has very simple data structures and _already mostly works_. I'm not worried about deadlocks. If there were still data corruption or loss issues that i was aware of I'd be much more hesitant, but all that I'm intending to is related to in memory and on-CPU logic. I have no intention of changing anything about the disk format.
Venti is simple enough that neoventi seemed like a good idea. Compatibility with the disk format was the hardest part.
I think fixing fossil will be less work than trying to replace it, and fixed fossil + neoventi will do most of what i want. Venti is where the interesting stuff happens anyways.
And, importantly, if I'm wrong, i can just stop working on it and go back to e.g. wbfs. I also don't have access to the latest neoventi or pdffs sources until i get back to my pc, so I'm stuck with what i have on the reform; this seemed a reasonable short term obsession
khm (npub19av…rp6r)
pixx
npub15c…k3agq
2026-03-16 02:27:03 UTC
in reply to nevent1q…snxr
Author Public Key
npub15cwtx74f44j6snvq7yw74ncttpkzueufm47xd3e5nmtxd5hwazdqck3agqSeen on
wss://relay.momostr.pinkPublished at
2026-03-16 02:27:03 UTCEvent JSON
{
"id": "5ef80208b45a437be2be4bc74eddea702e78ad54b6e9c7737d7d3f210a152d3f",
"pubkey": "a61cb37aa9ad65a84d80f11deacf0b586c2e6789dd7c66c7349ed666d2eee89a",
"created_at": 1773628023,
"kind": 1,
"tags": [
[
"e",
"4bf6ab7eaebd2d16ca6500b97114a3987604937a7a7604d0a982ec9e20618ddd",
"",
"root",
"a61cb37aa9ad65a84d80f11deacf0b586c2e6789dd7c66c7349ed666d2eee89a"
],
[
"p",
"a61cb37aa9ad65a84d80f11deacf0b586c2e6789dd7c66c7349ed666d2eee89a"
],
[
"proxy",
"https://merveilles.town/@pixx/116236486124087207",
"web"
],
[
"p",
"2b0a6c373105dfed9dbc02932c5eeca4f3c26bf41f346370623cf061a0ac1a44"
],
[
"e",
"020f3280a0320bfd0ec83ffdeddf885791ada8bd0cdd1db5364861e8b9167d75",
"",
"reply",
"2b0a6c373105dfed9dbc02932c5eeca4f3c26bf41f346370623cf061a0ac1a44"
],
[
"p",
"2f58acc48f03ab946c4f71e16bb3d9969aae76c3093782186d9dccc311dee842"
],
[
"proxy",
"https://merveilles.town/users/pixx/statuses/116236486124087207",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://merveilles.town/users/pixx/statuses/116236486124087207",
"pink.momostr"
],
[
"-"
]
],
"content": "Last time i ran into a deadlock i fixed it in like three or four hours. This is the exact kind of programming I'm best at, and it's with a project I'm familiar with and have used for 3+ years (without, i might add, any data loss or corruption so long as i ran fshalt, across at least four machines).\n\nFossil has very simple data structures and _already mostly works_. I'm not worried about deadlocks. If there were still data corruption or loss issues that i was aware of I'd be much more hesitant, but all that I'm intending to is related to in memory and on-CPU logic. I have no intention of changing anything about the disk format.\n\nVenti is simple enough that neoventi seemed like a good idea. Compatibility with the disk format was the hardest part.\n\nI think fixing fossil will be less work than trying to replace it, and fixed fossil + neoventi will do most of what i want. Venti is where the interesting stuff happens anyways.\n\nAnd, importantly, if I'm wrong, i can just stop working on it and go back to e.g. wbfs. I also don't have access to the latest neoventi or pdffs sources until i get back to my pc, so I'm stuck with what i have on the reform; this seemed a reasonable short term obsession \n\nnostr:npub19av2e3y0qw4egmz0w8skhv7ej6d2uakrpymcyxrdnhxvxyw7appqp6rp6r",
"sig": "25a03de387f0d3e2a303794eea07db1514bcfb109ed6747f30ec38ab2256ec7b664816aeae996a7bd75dea64fa08ffd5d405bcf682277bc212179b1740596227"
}