klevdb VS hypothesize

The performance of https://github.com/klev-dev/klevdb is 10x https://github.com/maragudk/goqite so it makes me assume the durability is somewhat lacking. Can you speak to the tradeoffs here around message loss?

I would think that having a small chance of message loss due to writing to an append only log in batches might be a reasonable trade off for many things (if that is how it works).

https://klev.dev

I'm fascinated by the idea of Kafka and wanted to use it like a saas in my own apps, so I made my own take on it. It also doubles as a key/value store, so its useful for a bunch of things. The store itself is OSS and you can find it at https://github.com/klev-dev/klevdb.

I haven't touched it in years, but during grad school I created a fully operational browser-based app for integrated note-taking and reference management for academic projects, based on locally stored markdown files, and designed to minimize attentional breaks: https://github.com/rkp8000/hypothesize .

I ended up using it for the remainder of my PhD; however, it was unfortunately a bit too easy to accidentally delete an entire note document, and I never got around to fixing it (although at least one other person ended up using it as the primary tool for their grad studies also :) ).

It definitely earned me no more than $0/month.

https://github.com/rkp8000/hypothesize

In grad school I made a browser-based app in django to try to integrate note-taking and reference management as seamlessly as possible, having been fairly disappointed with existing software. Basically, it's kind of wiki-like, except links open in place by default so you don't lose your place jumping between pages.

I got it working well enough to use for the entirety of my PhD but don't really use it anymore just because it's still fairly clunky in certain ways.

I have zero time to continue working on it, but I do still kind of like the idea and would be thrilled if someone else picked it up!