ANNOUNCEMENT ABOUT GOSSIP UNSTABLE BRANCH
It has come to my attention that a lot of people are using the 'unstable' branch of gossip. That's great if you want to encounter bugs and thus help me fix them. But it is not so good if you don't want your database to become corrupted. Unstable is not meant for people to be using as their daily driver.
The master branch will have the following guarantee: Any database migrations will remain, and further changes will migrate from that point. I won't roll back any commits.
Neither of those guarantees are true for unstable. I may force-push, roll back commits, and change migrations. if you run off of unstable, these actions could cause your database to corrupt. So for those brave souls doing this (and I'm glad there are a few of you), I strongly recommend you backup your database every time you fetch and compile new code (unless you don't care about event history and like starting fresh). Here is one way to do that on linux:
tar cvf - lmdb | zstd -c > lmdb.$(date +%Y%m%d).tar.zst