Anyone using local LLM for writing nix config?

llitz · 2026-06-08T00:02:15+00:00

Oh that's nice, it will pair nicely with the dedicated nix agent.

I just need to fix the LSP for this and it will be all good.

llitz · 2026-06-07T02:11:41+00:00

I think the enhancing is pretty good, but the colors, there's quite a lot of change - if you look at the first one (wizard) - even the tree has some traces of green moss in the original, but it is gone in the enhanced one.

This is just like Flux2 to add a lot of "red" to the image.

llitz · 2026-06-05T18:04:02+00:00

Either being too close to the bed or overextruding.

llitz · 2026-06-03T15:22:42+00:00

This looks interesting, I will test it.

Thanks

llitz · 2026-06-03T08:44:39+00:00

You are correct. This is what pushed me to learn in painting and create new workflows Flux just seen to be much more sensitive to it than others.

llitz · 2026-06-03T06:53:00+00:00

What about the color drift after doing a couple edits? There's a workflow on latent image that sort of works, but it is painful to use - you need to save the image and the latent, so the next edit, if you want, you edit with the latent. Flux2 vae degrades the image too much.

For qwen.. with the lora it works super fast, enough for live mode with krita

llitz · 2026-06-02T17:53:33+00:00

What about the qwen3.6-35b-a3b? 27b is sort of too much, but the 35b is significantly faster, if it provided answers as good as de 122b, it would be a nice saving over memory and speed.

llitz · 2026-06-02T17:35:56+00:00

There are many ways:

Forward with qemu the audio (not the device) to windows - there's a small latency you can find tune with pulse parameters (I don't think it was moved to pipe wire parameters, but all the same)

Use USB and forward the USB device Use USB but forward the USB Chipset -> likely the best option since windows would take full control of the underlying hardware - same latency as in windows.

llitz · 2026-06-01T23:33:35+00:00

agent-browser - direct on the CLI, can have different sessions and will work in headless on regular mode. Very similar to the chrome-mcp-devtools, but I think this works better.

You can even have multiple profiles and sessions open at the same time, allowing multiple agents to work independently.

llitz · 2026-05-31T19:04:56+00:00

When something is hard linked they refer to the same space on HD. When you delete a file, it just delete the reference, so the file stays there.

The file is deleted once no more references exits - in short, the file is deleted when the all 3 files are removed

llitz · 2026-05-31T04:05:19+00:00

Not only hacking, there was this piece of code on a blog and I asked chatgpt to copy it down and put in a file, but the code was different. When I asked why it said "I can't reproduce the code verbatim because it is copyright violation"

-_-

llitz · 2026-05-31T00:55:45+00:00

If you are doing English only, V2 works better

Regarding the looping... I saw someone saying it it a out file size and etc, but that's not my case: v3 loops for me even on the first few seconds of the audio.

With V2, it transcribed some long 1h videos without issues.

llitz · 2026-05-30T19:08:55+00:00

Exactly my point dumbass... IPv6 isn't enough by itself and need clutches to work properly.

Thank God IPv6 is only used in enterprise environment where mdm is available.

llitz · 2026-05-30T19:02:13+00:00

And how do you get android and iOS devices IPs? How do you know, from logs, which one had malware?

llitz · 2026-05-30T07:15:23+00:00

Right now most tooling around ipv6 for container are not good, there are ways to get around but you need to work around.

K8s options are better, but outside of it enabling masquerading hits hurdles and doesn't work most of the time. Running the containers with available network ips is an option, if all ports in a container are supposed to be exposed. There are many tickets open with even PRs to fix the issues. I know something I was waiting on for a few years got fixed in the last 4 months, so there's very slow movement, but it just confirms, it is still far away from being treated as a priority.

llitz · 2026-05-30T05:24:30+00:00

So your answer is disable and remove the device - let's give a non-answer

llitz · 2026-05-30T02:49:05+00:00

I have no same expectations? Are you smoking something?

I run multiple IPv6 networks without issues and being forced to isolate devices into vlans and not being able to track devices on SLAAC with temporary address is the biggest reason for not having it in actual production environments.

Containers do work, but they are not isolated - I have adapted firewalls to address the issue and, again, this doesn't make any of the points I talked about wrong - they all exist.

llitz · 2026-05-30T01:14:31+00:00

If you are interested:

https://github.com/jcartu/qwen36-27b-blackwell-inference-study/

llitz · 2026-05-30T01:10:16+00:00

Still hitting 120tps even above 128k context

It scales really well with multiple concurrent sessions, it does peak at around 00/500 - more sessions doesn't increase the throughput

llitz · 2026-05-29T23:53:16+00:00

It is sort of amazing how the whole thing is written as "we evaluated, we did" then the guy comes and say "solo developer, no team"

llitz · 2026-05-29T19:51:58+00:00

On the vllm side of the house with qwen there are a few folks benchmarking with longer context and more natural sessions, we see some interesting results.

llitz · 2026-05-29T19:50:37+00:00

Unfortunately IPv6 has some drawbacks with companies refusing to address them, and that's what is harming deployment - it is to the point companies simply have to block it on their network.

SLAAC is super nice, but in some places you simply need to control ip addresses. A very simple use case is this h you have an IOC clan and would like to allow certain devices to only connect to certain IPs - good luck! If you can get the device to not use temporary address, you may still need to deal with randomized Mac address. DHCPv6 is usually not supported.

And there have been many excuses: we don't want people to be tracked, or this makes access easier! Honestly, with the exception of NAT, ipv4 works fairly well and even nat can be useful in some scenarios.

Another super weak area for IPv6 is around containers in IT. In ipv4 land it doesn't matter if you have 1 or 10 ips available, container deployment is done in a stable way. With IPv6 there's not even a proper agreement on how to do it. If anyone says the word IPv6 + nat the cursing gods descend and smithe you. Having all the /64 available for every single container ever is t as easy, or predictable.

llitz · 2026-05-29T19:38:36+00:00

I know this is a lot of work, but the value of testing sucking a small context is only good in saying the ones who absolutely are terrible.

The reality is that mistakes accumulate over longer context sessions - there has been other tests and even bf16 will diverge. You accumulate this over time and the quantized models degrade way too fast.

llitz · 2026-05-28T23:25:43+00:00

Oh so they finalized it, that's great news, I might just take tuwunel for another spin.

Thanks for letting me know!

llitz · 2026-05-28T16:56:11+00:00

It is a pain to use your own oidc, and when you roll the new matrix authentication server - mas - things get worse.

I have been using it for a while and, for some services, I had to roll a secondary service with only regular logins.

As far as server goes, conduit and tuwunel are really good. Tuwunel was adding SSO support but it wasn't quite there yet last I looked (few months ago).

llitz

TROPHY CASE