HackerTrans
TopNewTrendsCommentsPastAskShowJobs

cowbertvonmoo

no profile record

comments

cowbertvonmoo
·3 mesi fa·discuss
Yeah, once you give anyone a capability — bots included — there’s no stopping the capability from getting widely distributed. You have to bake in protections like revocability up front to be prepared for the case that they get disseminated beyond your intended reach. And, with agents, provided the agents behave in a way that is consistent with being unworried about their reputation, they could and might disseminate a capability widely, in their own network. So, a key to safely designing a bot network is to assume all the bots are in a clique and sharing all granted capabilities amongst themselves, as they can converge on that if they choose. At some point, it’s a game of managing their introductions. Hey, that’s a whole lot like parenting.
cowbertvonmoo
·3 mesi fa·discuss
I’m Kris Kowal and I’m the tech lead on the Familiar project and happy to answer questions about building this new kind of user agent for safely managing and extending the capabilities of bots and apps.
cowbertvonmoo
·10 mesi fa·discuss
I maintain ses, the compartment primitive LavaMoat relies on. The ses shim for hardenedjs.org creates compartments that deny guest code the ability to inspect the true global object or lexically reference any of its properties. By default, each compartment only sees the transitively frozen intrinsics like Array and Object, and no way to reach the genuine evaluators. The compartment traps the module loader as well, so you can only import modules that are explicitly injected. That leaves a lot of room for the platform to make mistakes and endow the compartment with gadgets, but also gives us a place to stand to mount a defense that is not otherwise prohibitively expensive.