pjv on Nostr: I don't have any C++ fu, so I have not spent any real time spelunking the core source ...
I don't have any C++ fu, so I have not spent any real time spelunking the core source code, but I know that its db is LMDB. My only hands-on experience with strfry is from the devops side; getting it running in a container, and writing the python write policy plugin in my repo.
That strfry exposes a stdin / stdout interface to any other process that can effectively pipe input and output is brilliant. It opens up so many possibilities. Alex Gleason (npub108p…yev6) has written a bunch of different write policy plugins including iirc some that are storing and referencing state. Maybe I can think of a way to write some spam filtration for overzealous taggers. Or maybe if I keep tagging Doug Hoyte (npub1yxp…qud4) in this thread he'll come in with something interesting, though I am guessing by the number of commits in the strfry repo lately that he must be pretty busy with other stuff.
That strfry exposes a stdin / stdout interface to any other process that can effectively pipe input and output is brilliant. It opens up so many possibilities. Alex Gleason (npub108p…yev6) has written a bunch of different write policy plugins including iirc some that are storing and referencing state. Maybe I can think of a way to write some spam filtration for overzealous taggers. Or maybe if I keep tagging Doug Hoyte (npub1yxp…qud4) in this thread he'll come in with something interesting, though I am guessing by the number of commits in the strfry repo lately that he must be pretty busy with other stuff.