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
Gossip Client /
npub189…r3tg8
2023-08-24 20:32:42
Author Public Key
npub189j8y280mhezlp98ecmdzydn0r8970g4hpqpx3u9tcztynywfczqqr3tg8Published at
2023-08-24 20:32:42Event JSON
{
"id": "60daa60089160f8e2cdf1442317e0354ab7d3d33d4c2a6cd4682047e7fc73a57",
"pubkey": "39647228efddf22f84a7ce36d111b378ce5f3d15b8401347855e04b24c8e4e04",
"created_at": 1692909162,
"kind": 1,
"tags": [],
"content": "ANNOUNCEMENT ABOUT GOSSIP UNSTABLE BRANCH\n\nIt 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.\n\nThe 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.\n\nNeither 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:\n\ntar cvf - lmdb | zstd -c \u003e lmdb.$(date +%Y%m%d).tar.zst\n\n",
"sig": "dafab8fa498b0d2dbcd4ea0e6470415fe5ff6c8debd803217eca5f25ddf23ea37bb63124be4cb6fdada48c4f7ff22b9461d3045e8e9ec7e4a38d79d8e5ae7e8f"
}