Gave this evergarden colorscheme a shot after seeing it on lobsters today. Quite liking it.
Any conversation
I am programming a and custom DSL for it in C99. It gets a bit frustrating to think of language design and engine architecture decisions
@prophetorit๐งprofilefollow
grand and intoxicating innocence
always onlinereplied to@jmnufprofilefollow
Chilling.
Hand coding C to feel alive:
grand and intoxicating innocence
always onlinereplied to@jmnufprofilefollowChilling.
Hand coding C to feel alive:that sounds cool!!! are you planning to make a visual novel any time soon?
@jmnufprofilefollowChilling.
Hand coding C to feel alivereplied to@prophetorit๐งprofilefollowgrand and intoxicating innocence
always online:
Chilling.
Hand coding C to feel alivereplied to@prophetorit๐งprofilefollowgrand and intoxicating innocence
always online:I am actually doing this engine to make my own VN! I wanted a solution that's both light on web and is native. I do have a decent bit of the story outlined but engine is taking quite a while :/
@prophetorit๐งprofilefollowgrand and intoxicating innocence
always onlinereplied to@jmnufprofilefollowChilling.
Hand coding C to feel alive:
grand and intoxicating innocence
always onlinereplied to@jmnufprofilefollowChilling.
Hand coding C to feel alive:could I know what the storys about?!
@jmnufprofilefollowChilling.
Hand coding C to feel alivereplied to@prophetorit๐งprofilefollowgrand and intoxicating innocence
always online:
Chilling.
Hand coding C to feel alivereplied to@prophetorit๐งprofilefollowgrand and intoxicating innocence
always online:The story bases itself on the idea of indifference and hopelessness in changeable situations. Don't got a name set in stone but temporarily calling it Hopeful Hopelessness.
It's my first time writing but I hope it becomes a nice story
@prophetorit๐งprofilefollowgrand and intoxicating innocence
always onlinereplied to@jmnufprofilefollowChilling.
Hand coding C to feel alive:
grand and intoxicating innocence
always onlinereplied to@jmnufprofilefollowChilling.
Hand coding C to feel alive:I would love to play when your done with it!
Thanks for making a calm space on the Internet @stagasprofilefollow
creative technologist
creator of textlog
creative technologist
creator of textlog@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:The abuse (in my opinion) of the auto-translate feature is super annoying. Thanks goodness for โblockโ.
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).
"for you" now contains the same message multiple times
โฆ
added two more screenshots to - the "root" post view is incorrect, but when reply-on-reply, information goes up-then-down.
root post view IS correct, sorry.
I understand your confusion, but that's the formatting - quoted parent is below the child post - then that post's replies follow in the discussion view. The top post is always quoting its parent below it, the different bg makes it distinct. Just need to get used to it, same on X.
There really is no other way to include the parent otherwise, you have to break the hierarchy at some point, the other form would need to omit the parent body and show a 'parent' link but we want to include its body.