Okay, but that’s an easily resolvable trademark issue. That’s not what they are challenging.

Whatever it is that’s in their app, I REALLY don’t want it if these are the methods they use to push it.

I like browsing Reddit sometimes. I’d use it more if there was a non-Reddit browsing app, but those are gone now. So I sometimes use the mobile website.

I guess they‘re not particularly interested in my eyeballs.

It‘s nice to see that Docs is actually being used outside of the french government. I hadn’t seen anything about it outside of that context yet.

I’m also interested in it. Wondering how hard it would be to patch up the UI quirks and slowness. Considering that it has apparently already been in production for a while, I‘ll guess that the UI bugs don’t indicate that the software is too badly maintained overall.

We've found it to be quite flexible to set up. Are you doing anything in that space or would consider using it?

> Microsoft said they wanted not just to license the image for use as Windows XP's default wallpaper, but to buy all the rights to it. They offered O'Rear what he says is the second-largest payment ever made to a photographer for a single image

> "I don't think the engineers or anybody at Microsoft had any idea it would have the success it had

They also flew him out to deliver it. I feel like they had an idea of what they had.

Something like this just seems so obvious. Of course, an agent should be able to act on a remote machine. In theory, this is simple: just give it another set of tools that acts somewhere else.

In theory, it should be possible (trivial, even) to simultaneously connect multiple folders to a single session (as to mirror a more complex workspace). However, I haven't really seen any coding agent that can connect to multiple environments yet.

As far as I'm informed the complexity doing this is a little bit higher than just giving it read and write tools, if I understand correctly, modern harnesses are a little bit more optimized per model (diff formats, see "apply patch").

Thanks! You're right, the idea is obvious in hindsight. The hard part was finding something that works generically across environments. The devcontainer spec turned out to be that standard. It's already adopted by VS Code, GitHub Codespaces, DevPod, and a growing list of tools, so you get a portable definition for free.

On the multi-environment point, devcontainer-mcp already supports this. An agent can spin up multiple workspaces simultaneously (local Docker, DevPod, Codespaces) and work across them in the same session. Each workspace is just another set of tool calls with a different handle. Nothing stops you from having a frontend container and a backend container running at the same time.

On the diff format / apply-patch point, that's a real concern. I went with surgical string replacement (old_str → new_str) for file edits inside containers because it's model-agnostic. No diff format to get wrong, no patch that fails to apply. It's less clever but it works reliably across models.

A few years back there was an outcry in Germany about developmental aid funding bike paths in Peru.

Could this have been one of the most effective forms of aid?

I’m glad that some people in the FOSS community are embracing AI assistance.

It’s here and we need to write software. Let’s celebrate that it lets us do it better!

Isn’t it funny how the measure is how much AI is used instead of how productivity has evolved?

Of course the first image if of lightly dressed women. They know their audience.