Doughnuts are delicious, then belly vicious.
Oh multitudes! Why have you forsaken me?
Any conversation
Having a little difficulty seeing how long this service will exist. People are terrible. Sooner or later it will be found and ruined.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:Yup. I have long change my philosophy on things like these: just live the day. :-)
Been working on an old mastodon hosting project I tried to start a few years ago, with a focus on privacy. This is the first big project I've tried to come back to with the help of coding agents and find it invigorating, and gives me the confidence to actually finish the project. Who knows if it will ever make a dollar, but it sure is fun to watch my ideas come to life.
Putting a slide deck together (outside of work), despite agreeing with Tufte on this matter. Iโll also create a handout that tells the story better than the slides and deliver that, too, but was asked to produce a slide deck, and I think thatโs part of the โeffort theater.โ
Using Beamer for the slides, but not a theme that looks like Beamer because humans have eyes.
Hi ha dies que em demano si no hauria d'escriure en catalร aquรญ, per tal que hi hagi mรฉs diversitat lingรผรญstica visible. Al cap i a la fi, avui en dia les traduccions sรณn econรฒmiques. La traducciรณ automร tica pot ajudar a preservar la diversitat lingรผรญstica del mรณn.
There are days when I wonder if I shouldn't write in Catalan here, so that there is more visible linguistic diversity. After all, translations are cheap these days. Machine translation can help preserve the world's linguistic diversity.
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.
... 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.
Curious, why does using Haskell make a difference here?
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).