I was imagining something more like concept-city based around an extensive quasi-Venetian canal network, where "swimmable" (like "walkable") defined a possible mode of regular transport.
Me too. I like to think that, if humans survive to reach some kind of utopian, post-scarcity state, people will experiment with building places like this, just because they can.
I just spent some time in Basel, so I thought they'd mention about how the locals go for a dip after work with their wickelfisch and float downstream back home
The thing about Jobs is that he's become whoever you want him to be. If you believe yourself a visionary, he's the one to emulate. But, conversely, you can't visit Linkedin for a second without seeing the Jobs quote about hiring smart people and getting out of their way. (Ironically, considering the point of this essay.)
From a quick glance at what JobRunr does (especially running asynchronous/delayed background tasks), it seems that Restate would be a very good fit for it as well. Restate will also handle persistence for you w/o having to deploy & operate a separate RDBMS or NoSQL store. Note that I am not a JobRunr expert, though.
Thanks! I'm not familiar with Jobrunr, but we can definitely help with orchestrating async tasks (as well as sync rpc calls), especially if its important that they run to completion
I am personally involved in procurring HSMs for regulatory reasons. I would be more than happy to deploy an alternative solution that's demonstrably better suited for threats in todays typical cloud environments and fight it out with the regulator. The author sadly doesn't answer that question. Anyone having an idea?
How about confidential computing, e.g. AWS Nitro enclaves, Intel TDX etc?
HSMs make most sense when they’re performing high-level operations (“Is this credit card CVC valid?”); when used as signature or decryption oracles (“Hi, I’m a trusted application server, now sign this email!”) their security gain rapidly diminishes.
Sometimes they get used for key storage alone (“Hi, I’m an application server booting up, give me the RSA signing key for account x!” or even worse “Hi, I’m an application server booting up, give me the key wrapping all the user keys in our database!”), with obvious implications.
Getting an HSM vendor to implement your use case can get very expensive; confidential computing lets you do it yourself, i.e. draw a much larger “trusted” box in your architectural diagram than otherwise feasible.
I don't think they're trying to solve this issue directly. This is intended to be used as PKM (personal knowledge management) system.
You are correct in any case that this is a hard problem and I would love to get some perspective from the author on implementing such a system org-wide.
Not sure I agree with your PKM point. It feels like it fits well for company/project structure. Reading his forum and a bit into the article it seems to advocate a "librarian" that keeps the system correctly categorized. I think he mentioned somewhere that this system doesn't fully fit PKM. I remeber some example of categorizing photos according after vacations, but running out of numbers. But I must admit I don't fully remeber the arguments.