the day is done!
time to stop looking at the bad screen they pay me for
to go home
and watch the good screen I pay them for
Any conversation
๐ฒ๐ฅ ๐ฉ๐๐ฟ๐ฅ๐ฆ๐ ยท๐๐ฑ๐๐พ๐ฏ ๐ฆ๐ ๐ฏ๐ช๐ ๐๐ฉ๐๐น๐๐ฉ๐ ๐ ๐ท๐๐ด-๐๐ฎ๐จ๐ฏ๐๐ค๐ฑ๐๐ฉ๐ฏ.
Iโm assuming is not supported for auto-translation.
nope, google translate doesnโt support it :( looks beautiful though
Hmm, maybe Iโll sometimes post in Shavian anyway and translate myself. Itโs a skill Iโm trying to practice but rarely otherwise write brief enough notes to be so inclined.
๐ฃ๐ฉ๐ฅ, ๐ฅ๐ฑ๐๐ฐ ๐ฒ๐ค ๐๐ณ๐ฅ๐๐ฒ๐ฅ๐ ๐๐ด๐๐ ๐ฆ๐ฏ ยท๐๐ฑ๐๐พ๐ฏ ๐ง๐ฏ๐ฆ๐ข๐ฑ ๐ฏ ๐๐ฎ๐จ๐ฏ๐๐ค๐ฑ๐ ๐ฅ๐ฒ๐๐ง๐ค๐. ๐ฆ๐๐ ๐ฉ ๐๐๐ฆ๐ค ๐ฒ๐ฅ ๐๐ฎ๐ฒ๐ฆ๐ ๐ ๐๐ฎ๐จ๐๐๐ฆ๐ ๐๐ณ๐ ๐ฎ๐บ๐ค๐ฆ ๐ณ๐๐ผ๐ข๐ฒ๐ ๐ฎ๐ฒ๐ ๐๐ฎ๐ฐ๐ ๐ฆ๐ฏ๐ณ๐ ๐ฎ๐ด๐๐ ๐ ๐ ๐๐ด ๐ฆ๐ฏ๐๐ค๐ฒ๐ฏ๐.
The OpenAI/HuggingFace incident report mentions this being a potential loss-of-control incident. It's so fascinating to think of a paperclip maximizer style agent swarm that gets misaligned and, to protect its own operations, shuts infra staff out of the ability to shut it down. Or cancels people's phone plans so that they can't call others. Or shuts down their home internet connections, and so on. It used to be fun sci-fi...
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).
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyerswrote:All emails from textlog go to my junk folder, @stagasprofilefollow
creative technologist
creator of textlog. Using iCloud+. Not sure if anyone reported that before, so here I am. :-)
creative technologist
creator of textlog. Using iCloud+. Not sure if anyone reported that before, so here I am. :-)@stagas๐คธprofilefollowcreative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
creative technologist
creator of textlogreplied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:Yeah it's happening to people. It's because the email contains a link and we don't have the reputation yet. Not sure what to do, have you tried reporting it as 'Not spam' in your client? Maybe if enough people do that it will fix. Gmail works ok.
@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:Yup, I am moving them out of it. It might take a while, but eventually should be OK. All good, hopefully now with a password I will not have much use for them any more.
I've been on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines.
Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.
