Eric Wong <[email protected]> wrote: > All of these will probably be in the future of public-inbox; > but I think I'm going to goof off with these in a > yet-to-be-announced AGPL project, first...
That project remains unannounced and stalled. My mind isn't working well enough to implement some of the logic necessary... But most of the low-level bits are done. * While working on that project; I've noted git SHA-256 and SHA-1 don't mix for alternates, currently. Neither -extindex, lei nor v2 inboxes can support a mix of SHA-1 and SHA-256 epochs/alternates. * Interfacing with FUSE3 is *easy* (at least for users with gcc + libfuse3-dev + URCU installed). The low-level FUSE API makes far more sense to me than the high-level FUSE API used by most language bindings. I'm using a standalone C shim (not Inline::C) using the FUSE MT-loop to interface with multiple Perl processes via SOCK_SEQPACKET. * Perl 5.12 isn't happening: https://public-inbox.org/meta/20211108183859.GA25072@dcvr/ https://public-inbox.org/meta/20220213101802.GA18993@dcvr/ -- unsubscribe: one-click, see List-Unsubscribe header archive: https://public-inbox.org/meta/
