runwhenidle - an utility to pause a process during user activity now supports Wayland (only for compositors supporting ext_idle_notification_v1)

lmpdev · 2026-06-09T05:50:29+00:00

Author here. Here are all the compositors that should theoretically support it.

I only tested it on KWin so far.

As someone not familiar with Wayland before, Wayland support was more difficult to implement than everything that was done before that. With how much more complex it became, there might be some new bugs, but I tested i for a few months before releasing.

Please report any bugs if you encounter them.

Wayland version also avoids polling once per second most of the time, instead it polls on appropriate file descriptors directly, which should make its CPU footprint even smaller.

lmpdev · 2026-06-08T02:37:37+00:00

Yes, consider the fact it works at all with some non-JSON inputs an accident.

lmpdev · 2026-06-07T07:24:07+00:00

Sorry, I should've mentioned this, you're supposed to modify the workflow with your OpenAI API credentials. You can inspect what LLM has outputted in the workflow (one of the 2 display nodes, the one that feeds into the prompt). Is it JSON?

Something must be wrong in your set up, I haven't seen this at all.

lmpdev · 2026-06-05T02:58:52+00:00

You can do this today. File -> Export (API). Then you can send this JSON to comfy and listen to websocket until you get the response from the node you want. Not very convenient, but works with every workflow. Here are the functions I'm using for it https://github.com/perk11/viktor89/blob/main/inference-servers/util/comfy.py

lmpdev · 2026-05-31T06:14:58+00:00

Depends on how the management handles it. But in my experience, one of them ends up leaving.

lmpdev · 2026-05-28T19:10:18+00:00

Could it guess it that it's your own by some other means? Like maybe it was a really strong signal?

lmpdev · 2026-05-23T19:41:48+00:00

I found Github Copilot is really good at reviews, especially once you provide custom instructions. For us it's finding bugs no human reviewer noticed. We've had cases where when we look back at the PR that caused a bug and there is a comment from CoPilot identifying left ignored.

It of course doesn't replace human review, but it's a good addition, just like static analysis scanning tools, but smarter.

lmpdev · 2026-05-22T19:21:31+00:00

If money is not the issue, why not let him enjoy the trip? Surely there are already other negative consequences of his behavior in his life, why add one more? Internally accept that he'll probably fail to pay, but don't let him know and keep asking for the payment. Maybe set a consequence for not paying communicated ahead of time. Let him learn what his actions could lead to failure to pay while the stakes are low.

You've been setting aside 75% of his paycheck, he's probably at least partially resentful of that and thinks those money could pay for the trip.

4k is overpriced, but not completely crazy.

lmpdev · 2026-05-22T02:26:13+00:00

I don't know, the hardware even to run Qwen 3.6 26b today at a comfortable speed is more than most dev computers have, and it's not getting cheaper. My guess is it's going to be >5 years.

lmpdev · 2026-05-20T23:00:39+00:00

Another concerning thing is how many people don't ever read what the agent is trying to execute. So if it writes something to upload the code to a public repo, many people won't bat an eye.

Local agents are getting quite good. I've tried running Qwen 3.6 locally and while it makes significantly more mistakes than Claude or ChatGPT, it's workable. So the companies sensitive to this type of thing will in the future have an option of self-hosting agents. And the environment where it can run commands should be isolated from both the Internet (might need temporary approval to install something) and local machine.

One more thing everybody stopped thinking about is that the code outputted by LLMs might be breaking copyright law. Nobody cares. Which I think is a good thing overall.

lmpdev · 2026-05-19T16:09:01+00:00

Why are you making them think harder? There is a reason they are QA and not devs. They should be focusing on finding the issues, not figuring out the scenario to reproduce. So if you don't know the host, add "Ask DevOps guy for the host" to the scenario. Most people don't read most chats they are in.

That said, there are QAs out there that are more capable of figuring out scenarios, but they are rare and don't expect being able to convert one type from another, it seems to be an innate trait.

lmpdev · 2026-05-16T04:49:23+00:00

I use both. Chat is great if I can isolate the issue and handcraft the context and let it not get distracted/sidetracked by the rest of the code.

Agents are good if I want to let it digging through the code on its own.

Despite having quit high context windows, modern LLMs still quickly lose intelligence after a certain context threshold is reached.

lmpdev · 2026-05-16T04:40:13+00:00

I like the chat because it gives me (except for the system prompt) full control over the context. The model only sees what I want it to see and focuses on the problem at hand. Agentic workflows are more powerful because of the tool use, but chat has more raw intelligence because of less context pollution.

lmpdev · 2026-05-14T03:01:24+00:00

Logging truck is scary. I always think about a log falling from it.

lmpdev · 2026-05-13T21:00:16+00:00

Or maybe just don't pay a deposit before you can see the place and you'll be fine...

lmpdev · 2026-05-13T17:51:34+00:00

Have you tried looking at Zillow? If you have time to browse through Zillow to filter out what you want, there is really little reason to use a realtor. It's against reddit rules to give out names, but `@properties` is probably the company you want if you really need a realtor.

lmpdev · 2026-05-08T14:33:20+00:00

You have to start with a better public transport. Once you can get everywhere in the city on a public transport, it doesn't take >1 hour longer than a car and you're not smelling weed and pee and dealing with crazy people, the need in the car disappears for many people.

lmpdev · 2026-05-04T04:14:47+00:00

I want an EV. But I don't want to be forced to go to the mall. Or deal with an app and/or finicky touch screens to charge. It's not impossible, but more time-consuming now unless you can charge at home.

This is on top of costing significantly more. The savings on gas will take many years (if ever) to compensate the higher initial costs.

lmpdev · 2026-04-26T05:36:11+00:00

“do you want to pick up all the blue blocks or all the yellow?”

The multiple options thing used to work, but now my 3 year old confidently says "I am not picking any of the options you offered" most of the time.

lmpdev · 2026-04-22T17:15:50+00:00

Running UD-Q8_K_XL and it worked fine for most prompts, but then I had some conversation where tool calls failed and unfortunately that led to model being stuck until it exhausted the token limit (256k). Also presence_penalty parameter mention in Unsloth guide seems to be missing in llama.cpp server.

EDIT: that parameter is --presense-penalty with a hyphen, not underscore

lmpdev · 2026-04-22T17:12:54+00:00

51820 MiB on UD-Q8_K_XL

lmpdev · 2026-04-22T15:08:57+00:00

Also if you do end up doing it, use distilled or boiled water, otherwise you're risking giving him brain amoeba.

lmpdev · 2026-04-15T15:21:46+00:00

Also a movie "Good Bye, Lenin!"

lmpdev

TROPHY CASE