any · textlog

wrote:

You look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress from work. He takes care of his family. Capitalism

replied to:

Likewise... you look in the corner, you see a guy quietly eating cigarette butts. It's ok. He's dealing with a lot of stress for lack of work, or food, or future. He wants to take care of his family. Communism. We haven’t figured out yet. Maybe we never will.

wrote:

Collected my helper functions to lozenge.el package, e.g. (◊duckduckgo "textlog") opens ddg. Lozenge is ◊ character. Others are (◊find-file), (◊grep), (◊github-search), (◊show-commit) etc.

wrote:

curious to know whats the experience of production push in other companies? e.g lots of documents/approvals…

wrote:

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.

continued:

... 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.

continued:

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.

continued:

... 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.

replied to:

Curious, why does using Haskell make a difference here?

…

replied to:

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).

wrote:

Yello folks!

replied to:

hey! welcome :)

wrote:

Textlog seems pretty cool 😎

wrote:

Some thoughts deserve a smaller audience

wrote:

Where’s the coffee machine?

wrote:

Full productivity suite replacement for gmail, or proton mail.

replied to:

This looks good actually. I like the monochrome look.

replied to:

Im having fun. I really can't believe how well realtime collaboration works all considering the paths that are taken.

wrote:

The live tab on the android app is interesting... How does it work? This is a test 🫣

continued:

Does it do some kind of polling? Is there some kind of notify like publisher subscriber? 🤔

replied to:

It’s using the /firehose endpoint. It’s an SSE endpoint publishing everything latest. Though I meant it to be used server-side, since it’s heavily rate-limited — up to 3 conns under the same network, but I can’t control how clients decide to use it so.. ¯\_(ツ)_/¯

…

continued:

Might just lift the limitation.

continued:

Lifted, that’s how clients want to use it then so be it! Should be fine. We’re nowhere near crashing the server from connections.

wrote:

It's cookie o'clock, y'all.

replied to:

_ _ me want (.)(‘) more… / ___, \ .-. .-. _ \ ‘--’ / (:::) (:::{ ‘-`--=-`-’ }”` `-’ `"/ \"` \ / _/ /\ \_ { / \ } `"` `"`

wrote:

Hit me up if you want a long-term, low-commitment, long-distance, e-mail pen-pal. I've never had so much fun hyphenating things.

wrote:

Testing, testing…

replied to:

You forgot the “one, two, three”. :-)

wrote:

New app versions with apple

wrote:

I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.

replied to:

Definitely tables are cumbersome.

replied to:

Yeah, 100%. That is completely something I am punting on currently. It would be easy to just copy over the solution from (extensions to) Markdown, but it's hard to entirely narrow in on both what tables ought to do and how to make them do it. If you had a magic wand, what would you have them be more like?

wrote:

Longer answer: My editor does not start wars. I use whatever is convenient. Most of the time I am on visual studio code but I'll use anything. Well, anything except emacs I guess. I don't think I have ever actually used emacs.

wrote:

Well back ok the saddle after some deserving rest.

wrote:

I'm really interested to play around with textlog for a bit. I miss the space that once was Twitter and its constraints. Let's see if we find any users here ... ;)

wrote:

I’ve had quite the successful day cooking today: make a Dutch baby for breakfast with blueberries, a bean stew for lunch using up all the week’s odds and ends, make a coffee and walnut cake, and barbecued/slightly smoked a whole spatchcocked chicken for the first time!

Any conversation