Never heard of Exim, I'm just realizing what it is:

> Exim is an open-source Mail Transfer Agent (MTA) designed for Unix-like systems to receive, route, and deliver email.

what's the significance of this? do people use this in production systems?

Exim is apparently the largest email server these days... it used to be postfix, but with most people using Gmail or 365, running your own email seems to be an afterthought. /shrug

I had the exact same reaction - never heard of this.

Then perhaps you haven't been around for very long. Have a look here before you put your feet in your mouth any further:

https://en.wikipedia.org/wiki/Comparison_of_mail_servers

this is a good explainer video that talks about why Polymarket maintains a Panama HQ instead of a US one and why it has two different sites (.us vs .com). https://www.youtube.com/watch?v=seNwZhK4UdA

it already is. re-read?

Yes, it is, my bad. I was on my way to delete my comment actually! Oh well, too late now… (:

This largely appears to be a HTML generator at its core, not necessarily what Figma does with layers/canvases etc. There's no collaborative nature to it either.

It feels like a lightly designed product that moves claude CLI to their backend, generates the HTMLs and renders them in browser on claude.ai website for you. Sure, it accepts your design system as an input from you or imports from your repo, but you could feed the same into claude CLI as well?

I'm curious what exactly it gives besides having claude CLI + prompting it well with your design system + skills.

The IBM/Microsoft analogy is a classic. It’s always fascinating to watch these 'frenemy' dynamics play out. In these cases, the one who owns the direct interface with the end-user usually wins the long game, while the 'infrastructure' partner risks becoming just another utility. Will be interesting to see if Canva can maintain its identity or just become a shell for Claude's output.

Yep agree it looks like it’s taking the existing generated artefact, parameterising it within an inch of its life, exposing a pseudo WYSIWYG for the parameters and calling it a day with a few export options. Not a huge leap from what they’ve got already but it’s a clever adjacent step for sure. Same product new chrome.

It's rolling out progressively throughout the day.

I see on a daily basis that I prevent Claude Code from running a particular command using PreToolUse hooks, and it proceeds to work around it by writing a bash script with the forbidden command and chmod+x and running it. /facepalm

Maybe that means you need to change the text that comes out of the pre hook?

As I understand it, the problem nowadays doesn't seem to be so much that the agent is going to rm -rf / my host, it's more like it's going to connect to a production system that I'm authorized to on my machine or a database tool, and then it's going to run a potentially destructive command. There is a ton of value of running agents against production systems to troubleshoot things, but there are not enough guardrails to prevent destructive actions from the get-go. The solution seems to be specific to each system, and filesystem is just one aspect out of many.

As I understand it, the problem is these apps/agents can do all of these and lot more (if not absolutely everything, while I am sure it can go quite close to doing that).

Solution could be two parts:

OS bringing better and easier to use OS limitations (more granular permissions; install time options and defaults which will be visible to user right there and user can reject that with choices like:

- “ask later”

- “no”

- “fuck no”

with eli5 level GUIs (and well documented). Hell, a lot of these are already solved for mobile OS. While not taking away tools away from hands of the user who wants to go inside and open things up (with clear intention and effort; without having to notarise some shit or pay someone).

2. Then apps[1] having to, forced to, adhere to use those or never getting installed.

[1] So no treating of agents as some “other” kinds of apps. Just limit it for every app (unless user explicitly decides to open things up).

It will also be a great time to nuke the despicable mess like Electron Helpers and shit and app devs considering it completely fine to install a trillion other “things” when user installed just one app without explaining it in the beginning (and hence forced to keep their apps’ tentacles simple and limited)

How about the assets?

I assume you, the player, have to provide the assets yourself, and the game won't run without them. Since the code does not contain the assets, there is no copyright infringement.

As long as the assets dont contain code, they're kind of fair game. The rule of thumb is you cannot redistribute them, but if the person owns a legal copy you can point to them on their local system. It is not up to you to figure out if they're pointing to a pirated copy or a legitimate copy mind you.

I'm sorry dude but your last post was also hyping up R1 which was a total disaster. Do you mind actually sharing your experience with OpenClaw, such as how are you orchestrating a project? How much does it cost? How do you prompt it? What tasks do you get done? How much does it actually take to execute on those tasks? What is your interaction with the agent?

Nobody's saying you should deploy code with this, but symlinks are a very common filesystem locking method.