pull down to refresh
easier, harder, or stayed the same
none of the above, as it has most likely become impossible for me; the [incredibly small] node I used to run lived in the cloud, in the spare capacity of an overprovisioned server that I got laughed at for even daring to wonder how much it cost...
meanwhile, my NVMe controller reached higher temperatures than the CPU die [i.e., the compilation used an amount of memory swappable for background processes although not prudently useful for single monolthic tasks] from the first efforts towards compiling Alby hub locally, after the invocation from their README for obtaining precompiled docker images failed to even download them for reasons that are, honestly, not my job to fix.
obviously, the simplest next step is to abandon Alby hub [at least, for the time being], and look into alternatives built of separate small composable components.
salooning this deleted rant because I hate soapboxing and it seemed too much upon rereading... links to the original post
honestly I'm half-wondering whether the interminable parade of hopeful forks could be viewed as the checks-and-balances of the ecosystem against itself, regardless of whether any individual fork succeeds or fails; as long as, in the long run, forks are possible and critical ones do occur, the network remains money of the people, by the people, and for the people, rather than some incomprehensible technological overlord accelerating the consumption of all available energy.