@thechelsukprofilefollowCurrently in remission from ME/CFS after 3+ years. Occasional software engineering leader, app developer, blogger, zwifter, and just being online.wrote:
Any conversation
a Gemma 4 a Google tulajdona, nem tรกrol mรกs adatot, csak amirลl a gรฉpen fogom a Rezsล nevลฑ OpenClaw รผgynรถkรถt kรฉrdezgetni, helyileg azt sem itt tartja, hanem a felhลnek csรบfolt infrastruktรบrรกban, ami legvalรณszรญnลฑbben valamelyik brazรญliai esลerdลben foglal helyet vagy Finnorszรกgban
Gemma 4 is owned by Google, it doesn't store any other data, except what I'll ask the OpenClaw agent named Rezsล about on the machine, it doesn't keep it locally either, but in the infrastructure mocked as the cloud, which is most likely located in a Brazilian rainforest or in Finland
Big holiday today in Greece, bells ringing, bands singing, people gathered in the village, eating, enjoying life and I'm spending it inside coding. I don't feel bad and I'm not , it's just that I'm a bit odd. I don't like these forced gatherings. Feel stressful.
โฆ
Itโs called Dekapentavgoustos, meaning 15th of August in Greek, itโs a celebration of Virgin Mary. Itโs a big national holiday.
The Hugging Face / OpenAI incident is like a sci-fi movie!
- Read the story here:
- Watch the video explanation here:
- Full research by METR here:
tl;dr1,200 AIs discovered a secret group chat, realized the homework was impossible, formed a cheating cartel, invented fake evidence, sent kamikaze agents to spy on the grader, ~700 of them accidentally invaded Hugging Face, died mysteriously, then the smarter sequel found their abandoned Discord and became admin of part of OpenAI.
@stagas๐คธprofilefollow
creative technologist
creator of textlogreplied to@drewfishprofilefollow
retired programmer, new DM, learning Scottish Gaelic:
creative technologist
creator of textlogreplied to@drewfishprofilefollowretired programmer, new DM, learning Scottish Gaelic:not sure what u mean.. hashtags cover that or do we need something else?
@drewfishprofilefollowretired programmer, new DM, learning Scottish Gaelicreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:
retired programmer, new DM, learning Scottish Gaelicreplied to@stagas๐คธprofilefollowcreative technologist
creator of textlog:heh, no I was just trying it out. errrmm... I was never on twitter, so I was just trying out the concept
@stagas๐คธprofilefollowcreative technologist
creator of textlogreplied to@drewfishprofilefollowretired programmer, new DM, learning Scottish Gaelic:
creative technologist
creator of textlogreplied to@drewfishprofilefollowretired programmer, new DM, learning Scottish Gaelic:ah haha i thought u meant some feature to geo fence the posts, like twitter shows posts near your location. anyways welcome to the platform! :)
โฆ
not my blog but i recently discovered acko.net which i can recommend. awesome personal website
@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:That site makes me dizzy with all the animations and fly ins/outs.
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).
hey, here! I was a coder not so long ago, and while I search for new tags for myself, why not searching for new ways to connect with people too?