This is a pretty neat site. I remember having vague ideas about something somewhat close to this but doing nothing with them.
Any conversation
โฆ
Microservices.
Not really programming, as this is more on the architectural level.
Microservices is a valid approach when you need to address massive scale. The thing is, I have seen it applied to things that could realistically serve its audience in a handful of modest servers with a less fashionable approach.
It was done under the guise of simplification; each individual microservice was in fact very small. But this at the cost of absolute spaghetti architecture.
Love the flat option for threads @stagasprofilefollow
creative technologist
creator of textlog
Edit: didnโt realise that was the old style. Hahaha
creative technologist
creator of textlog
Edit: didnโt realise that was the old style. HahahaSince you guys are on textlog I think you will find this article and discussion interesting
A character count though that still requires JavaScript sadly enough ๐ฅบ
Interesting! Didnโt know about a few. Neat! ๐ Aside, do you have an invitation for ? Or can you help us by doing a post about
textlog.cc?โฆ
You think is too much? Itโs totally related to the post.
People post projects/tools/repos on lobsters all the time. From the about page, "as a rule of thumb, self-promo should be less than a quarter of one's stories and comments."
I think if @stagasprofilefollowcreative technologist
creator of textlog intends to be an active user of the site henceforth, it'd it should be kosher. Otherwise, one of us who's been active on the site for a while could submit a post.
creative technologist
creator of textlog intends to be an active user of the site henceforth, it'd it should be kosher. Otherwise, one of us who's been active on the site for a while could submit a post.A thing I've been doing lately is trying to come to the same conclusions others have without looking their the direct techniques and code. Last night I tried to figure out why people do vector based retrieval for RAG and ended up running these experiments: n0tls.com/โฆ/2026-09-03-i-think-โฆrag-with-grep.html
I'm still going to do an explore agent.
Ubuntu telepรญtรฉse a VirtualBoxba rendben megtรถrtรฉnt. Mรกr csak egy รผgynรถkรถt kell bele fogni, รฉs mรกris kรฉsz az "AI torture chamber", ahogy a Futurism รญrja... Mondjuk, elsล kรถrben mรฉg nem รญgy fogalmaznรฉk...
Ubuntu has been successfully installed in VirtualBox. All you need to do is add an agent and you have an "AI torture chamber", as Futurism describes it... Let's just say, I wouldn't put it that way at first...
โฆ
I think a trusted piece of software such as your operating system should be in charge of managing permissions. For example, I believe with Wayland on gnome you no longer need to promise you aren't secretly taking screenshots of the whole monitor and shipping it somewhere because to do that Wayland requires you to get user permission.
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).