While we are sharing eye rollers.. I had this person plonk into our issues once with a “revolutionary” encryption technique. I wish I could remember the concoction he described.. Now that I’m trying to find it, it seems they deleted the github account. Seems like he saw the light, or got banned. Either way SNR increased and I’m all for that.
I’ve been traveling from Hamburg to Barcelona by bike for the last ~6 weeks. Total is about 2700km. It surely could be done faster but I’ve met people along the way and did some work.
Also you get to connect with locals and nature along the way. Another thing that’s totally lost when you do the airborne thing.
Crossing an ocean is ofc a different beast but I’m also
excited for a re-emergence of blimps!
Glad you picked up on it. It’s not on the protocol guide yet but there are two or three new formats in discussion which all just sign opaque bytes. Wider adoption pending but the meta feeds is in JS already.
I can ignore the licensing for my personal stuff (and some work might be able to, too) but from a technical perspective I find the SPL translation layer and fs caching overhead much greater pill to swallow. It’s basically bolting on Solaris as a 2nd memory system just for zfs. I really hope this hack is recognized for what it is sooner rather then later…
sorry to rain down here but multi-device support is not a feature of metafeeds at all. It only realizes partial replication. It's equally important to grow the network but strictly distinct, all metafeeds are on the same device.
Not an export on this but I heard what blocked a lot of projects based on kindles was the proprietary waveform driver stuff to draw on the displays. Meaning that basic linux had supper inefficient redraw behavior compared to what the eBooks are doing.
If the response from the compiler/type system is the feedback signal for the loop, shouldn’t this work for any language that offers such facilities?