I think so. mdb_dump -s relays ./
mdb.c:5966: Assertion 'IS_LEAF(mp)' failed in mdb_cursor_next()
Aborted (core dumped)
It depends on the precise error. Lots of serde_json errors from bad objects over the network are not a problem. It just means that event is broken and you can't use it. Getting them from your database is a different story. Anyhow I see you rebuilt your db from scratch so I guess we will never know. If it happens again and you have a github account, open an issue at https://github.com/mikedilger/gossip
I did keep a copy of those dotfiles! So if you wanted to try to trouble shoot... I also tried doing gossip rebuild indexes, but it failed due to the relays table being corrupt as far as I could tell
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c I saw something mentioning this problem on GitHub. But looks like the solution was in bugfixes. This may have happened due to a hard boot in my case
just rebuilt the db from scratch oh well, lesson learned
nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c I saw something mentioning this problem on GitHub. But looks like the solution was in bugfixes. This may have happened due to a hard boot in my case
Oops I broke my #gossip client. Anyone know how to fix relay picker error error serdejson error
Maybe relays with a whitelist of nsecs could work in this case maybe
your use case is 100% what freedom tech is about
Maybe something like simplex would be a better protocol in your use case. unless the 'gift wrapped' 'better dms' thing is audited to be truely secure
this whole gossip thing i think is going to make 'private relays' not a viable reality. Ive been trying to experiement with that
wouldnt relay scraping leave that kinda info exposed🤔
What in the hell is this https://www.linuxfoundation.org/press/announcing-openpubkey-project
hairy orange bro
The v4v isn't equal. A collage degree might as well be indentured servitude at this point
#weedstr if it's bad then I wanna be bad
Your buggatis are way to thristy