Until autonomous rideshare services take over. Then regional monopolies will arise due to the infrastructure needed to support those fleets.
On english wikipedia it's a section of another article https://en.wikipedia.org/wiki/Ono_no_Takamura#Takamura_in_la...
IPFS would be a particular implementation of those more general concepts. SRI + multiple HTTP sources would be another more incremental approach.
> With LMDB on the raw block device, each write of a record results in an immediate write to the device Shouldn't they use mmap instead of syscalls for byte-addressable storage to avoid switches into kernel space?
Combine with SRI and some convention to just ask one of several hosts for it based on the hash(es) and we have concent-addressable loading.
https://xkcd.com/2030/
And paperclips.
It takes a long time to design and fab new layouts. So at best you would get firmware mitigations baked in. Or, as mentioned in other comments, the HT sidechannels might be fixed simply because HT is turned off.
Until autonomous rideshare services take over. Then regional monopolies will arise due to the infrastructure needed to support those fleets.
On english wikipedia it's a section of another article https://en.wikipedia.org/wiki/Ono_no_Takamura#Takamura_in_la...
IPFS would be a particular implementation of those more general concepts. SRI + multiple HTTP sources would be another more incremental approach.
> With LMDB on the raw block device, each write of a record results in an immediate write to the device Shouldn't they use mmap instead of syscalls for byte-addressable storage to avoid switches into kernel space?
Combine with SRI and some convention to just ask one of several hosts for it based on the hash(es) and we have concent-addressable loading.
https://xkcd.com/2030/
And paperclips.
It takes a long time to design and fab new layouts. So at best you would get firmware mitigations baked in. Or, as mentioned in other comments, the HT sidechannels might be fixed simply because HT is turned off.