Papas Gatitos
Any conversation
@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:The proverbial first post should have been โhello worldโ. :-P You are the first rustacean I come across!
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:LOL! Good point:)
I'm looking for a way to manage my bookmarks easily on desktop and Android. Anyone have any experience with software like that? It'd be nice to be able to tag or categorize pages, and maybe to keep local mirrors for certain ones. I'm open to self-hosting.
Thanks for reading!
I've stopped managing bookmarks after del.icio.us died - now i just hit the browser star but they seem to disappear and never visit them again, apart from the most recent. The situation sucks really. I'm also interested in a good solution.
I got jumpscared by the moon rising because itโs visible from where Iโm sitting and itโs huge.
I love full moon. It does something to me.
โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโ โโโโโโ โโโ
โโโ โโโโโโโโโโโโ โโโ โโโ
โโโ โโโโโโโโโโโ โโโ โโโ
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).