@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
Well, I think my IRCd (Eris v2) is close to be complete.
unicorn, n. - The purest and rarest cob, identified by a singular majestic kernel. Sightings can be found between Ogallala and Dubuque through summertide.
not my blog but i recently discovered acko.net which i can recommend. awesome personal website
@fastidious๐profilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@jamesjan3profilefollowresearcher, developer, dancer:
That site makes me dizzy with all the animations and fly ins/outs.
When I write I just add html files to the swiley.net folder in public.swiley.net. Sometimes I syndicate elsewhere (I was doing Substack for a while before Notes took over.)
I finally bit the bullet and have started to use dictation software more often, even outside of just my prompts. I really like it. Hopefully, computer use becomes much smoother soon. I would love to be able to control my computer with just my voice.
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
#haskellnotesfollow#ainotesfollow
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox.
So we're currently stuck with using VMs. This turns out to be tricky but seems do-able.
My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit.
I also don't want the agent to be able to git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.
... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on.
For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).
(defun textlog-post (beg end)
"Publish the region between BEG and END to `textlog-url'.
Interactively, requires an active region. Returns the URL of the
new post when the server reports one."