Mike Dilger on Nostr: GOSSIP USERS on unstable: I do not recommend using the unstable branch, but some ...
GOSSIP USERS on unstable:
I do not recommend using the unstable branch, but some people are. I have had to roll back database changes again, so if you ran gossip on unstable you should recover your database from backups. Since I know you are lazy and not actually making backups, you can instead do the following to fix your database:
1. pull the branch "rewind" from github
2. Compile and run with "./target/release/gossip oneshot" to clear the broken data.
3. Then switch to the new unstable branch and recompile.
If you don't do this, or recover from backups, a bunch of NIP-89 helpers will be missing for you but otherwise gossip will seem to work.
Published at
2024-10-15 23:25:31Event JSON
{
"id": "0000b747ebb8ed32904adf728a498fd044c6dc58cf26186b4e22b36dc4d4ed0a",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1729034731,
"kind": 1,
"tags": [
[
"nonce",
"9223372036854775934",
"16"
]
],
"content": "GOSSIP USERS on unstable:\n\nI do not recommend using the unstable branch, but some people are. I have had to roll back database changes again, so if you ran gossip on unstable you should recover your database from backups. Since I know you are lazy and not actually making backups, you can instead do the following to fix your database:\n\n1. pull the branch \"rewind\" from github\n2. Compile and run with \"./target/release/gossip oneshot\" to clear the broken data.\n3. Then switch to the new unstable branch and recompile.\n\nIf you don't do this, or recover from backups, a bunch of NIP-89 helpers will be missing for you but otherwise gossip will seem to work.",
"sig": "14726ad4b3057f15df38ef5a32bc8fbe6f3c0edd3d180a37bb30ee0688cefa6b69cc059216fc0cf45937cfea75a59d2ed142c77e810e3d9aaabd659be831e604"
}