strfry still marching toward 1.0. the rumors of sfrfry ded, in shambles 🐳 #nostrded #whowillrunrelays?
nostr:nevent1qqsv8faxe7fsq0lsly89l94ztc55cvpll3702h7lsm6t73xx9n3fhxcehsh52
Exporting and importing events into a new strfry instance (which you need to do when the DB version changes) takes too long. Here's a feature I just added that speeds this up a lot:
https://github.com/hoytech/strfry/blob/next/docs/fried.md
Going forward, there is a release-0.9 branch. I'm going to tag one more release on that branch soon (after back-porting a couple fixes). It will have strfry export --fried but not import. I'm planning on this being the last release of the 0.9 series.
I'm working on a 1.0 release in the next branch. I just did a big refactor of the DB format that I've wanted to do for some time. I also removed prefix matching on id/pubkey (this was removed from NIP-01) and fixed a bunch of bugs. This release will also have the latest negentropy protocol version and BTree code.
Discussion
I like how nostr:nprofile1qqszrq3cgvfe89vadjrp0gaa3xfs82txpx6y5ezwjuufzqu20h5xytgppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0f0a7qk develops the relay. It seems like he's in his own world, unaffected by anything outside of it. I think that's how it should be.