First post on textlog!
Any conversation
I got an email from battle.net to confirm my age. Apparently some content may be restricted to minors in the region my account is from.
You would think that the account having been created 19 years ago, and with some CD-keys of games from the late 1990's having been added to it would be enough proof, but oh well.
one-point-five-shotted a local node app for creating social posts. drawing from static pages (hey this exists) or new blog posts (timely). with copy/paste to x, and one click post to bluesky and mastodon, tag manager and stale/archive/reject/refresh options. An idea and a solution in about 10 minutes. Madness.
This #tome about #Tcl/Tk has me re-evaluating my plans to move to the woods to be a carpenter hermit.
Now I want to move to the woods and be a programmer hermit.
Testing this quiet corner of the web. I collect small notes about everyday tools ๏ฟฝ๏ฟฝ file formats, tiny utilities, offline workflows. First post is just a hello; longer notes will follow once I settle in. Plain text feels good after years of heavy editors.
Sharing a great read today:
Some of the takes are on the extreme end, but like most IT decisions, you can dial the pain to exactly what you want.
^C
textlog runs on a 2.5โฌ/mo vps 1 core/2gb ram, using just one instance of Bun with its embedded SQLite. Works perfect and I run a few other apps as well on that machine.
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).
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