If on a Winter’s Night a Traveller gives the reader the impression that there must be a system at play and gives up some of its secrets easily. However, there remains a persistent feeling, after reading each section, that there are other connections - threads of deliberate meaning - between them all that slip through your fingers as you desperately try to clutch more and more fragments passing by.
It's one of my favorite books precisely because it generates this feeling and led me to Perec's Life: A User's Manual among other fantastic works.
At the same time considering the people participating, there wasn't a way out of the problems that didn't involve violence. Different outcomes would require different choices that require different people.
I also believe that there will be more casualties in the AI Wars. We should be prepared for that. Capitalism, AI, and human life are mutually incompatible and I'm still not sure which two will survive the conflict.
You are absolutely right! It takes incredible bravery to admit that if we cannot solve the problem in totality then incremental improvements are useless.
The connection between ECS and DBs wasn't lost on developers in the early days of ECS. I'm reminded of Scott Bilias's 2002 ECS presentation: A Data-Driven
Game Object System[1] which clearly says, "This is a database."
In my mind, there's a pedagogical gap in OOP where ontologies are formed using classes and this almost never works in real life applications (no in real life for that matter). We almost always construct ontological relations using predicates not rigid hierarchies. For this, ECS tends to be flexible, and expressive enough to be a pragmatic choice.
The OP is describing the status quo on mobile phones and tablets. On mobile Secure Boot, and systems like it, are used to lock out the user. If the boot path integrity is altered, some apps won't work or will provide degraded experiences.
What's happening the article is what has already happened on mobile: it requires vendor signing to run anything on mobile OS and the vendor locks out 3rd party drivers from their OS entirely.
It's yet another step towards desktop computing converging with mobile when it comes to software/firmware/boot/etc integrity attestation, app distribution and signing, and the ability to use your own bootloader and system drivers. When Secure Boot was first rolled out on laptops, it was used by Microsoft to lock the user out of the boot process before it was adapted to let users register their own keys, it can always be used for its original purpose, and how it's currently used on mobile, again.
You don't have the ability to revoke my keys on this machine, that's the point. Not even MS could do that, because these are _my_ keys. The alternative proposed here is no keys at all.
What's the improved security argument for terminating VeraCrypt's account though? SB does have clear benefits but what is unclear is the motivation for the account termination.
What's the likelihood that this account ban provides zero security benefit to users and was instead a requirement from the gov because Veracrypt was too hard to crack/bypass.
Are the demands that users become experts in provider their own security against more advanced actors not significantly worse? The control part is unfortunate but the defaults should make it so users can focus on sharing pictures of cats without fear or need for advanced cyber security knowledge.
In Canada, demands are not actually demands. That way if the demand is avoided, there never was a demand to begin with; however, if it was fulfilled, then of course there was always a demand all along.
reply