danfinlay

This highlights a problem with the Anthropic-Mythos-restriction style "we regulate the best models so attackers don't have them": It also ensures that only the big-guy partners of the program (Glasswing in their case) have the capability to secure themselves at the frontier model level.

Hi there, TC-39 delegate and MetaMask co-founder here.

SES does address this, and strives to achieve "object capability security", wherein access to a function is equivalent to permission to use it.

One difference between an object capability approach and the capability-token approach described in the OP article is that in an ocap approach, you would have no need for passing around a capability token just to pass it to the restricted methods: Instead, you simply disallow importing modules by default, and now pass in any restricted methods to modules that you want to have access to them. I find this approach greatly more ergonomic, and if you ever want to further restrict a function, you don't need a new token, you just write a closure with your own policy defined in it!

By the way, we've developed a tool called LavaMoat that allows applying SES security to existing npm modules, no token-passing needed, by restricting the environment of each module per a policy file. https://github.com/LavaMoat/LavaMoat

While we're at it, I'll plug an audit we did of the SES shim code: https://agoric.com/blog/technology/metamask-agoric-hardened-...

There's LavaMoat, which enables using SES confinement around normal npm packages by creating a policy file for what can be imported/required by that module (and can auto-generate a suggested policy file from what appears used, which fails to greater restriction/security, and can easily be expanded): https://github.com/LavaMoat/LavaMoat

MetaMask is actually working hard on these problems, and building faster than ever, but they're big problems that aren't trivially fixed in a point release. You can expect some big announcements this summer.

Maybe these two are one. It will be ready for the layman when these concepts are easily comprehended, with improved UX.

I'd like a genetic analysis.

There are actually eight different implementations at this time, although the go client has a slight majority of users according to ethstats.net

http://ethdocs.org/en/latest/ethereum-clients/index.html

A lot of that iMac's cost is its retina display, and you didn't bother buying a retina display for the PC. Running a speed test is silly, there are already major differences in the build.

To make this remotely more scientific, you'd either need to buy a 4k monitor for the PC, or use a Mac Pro and just take the monitor out of the equation.

Hasn't this judge seen the Matrix?

I really like throwing in a balance board for variation!

I made a 3d-printable balance board dome, you can use it to build something much like a FluidStance!

http://www.thingiverse.com/thing:1197183

I used to use Repetier Host to run Slic3r and send the serial signals to my printer, but over time I've grown to prefer Slic3r's interface, and now that it has OctoPrint integration (send to your Raspberry pi print server wirelessly), it's the only application I need on a computer to print on my Reprap.

No, these are compatible statements. They both try to poach, and Tesla can be having more luck at it.

If it balances to be perfectly level, does that mean on hills it scrapes?

If so, any plans to put proximity sensors under the sides to help it determine what "level" is?