outfoxxed

Beautiful new Quickshell config by Soramane github.com/caelestia-dots…

@Waffl3x I had to patch it for some minor bugs in flick keys and add flick hints, but apart from that the custom layouts are quite smooth.

@outfoxxedd I've been using it too, have not tried custom layouts though

Realized today that FUTO keyboard has custom layout support, so I can pretty easily port thumbkey's layout and have both flick typing and mobile keyboard niceties at the same time

Wired up a trackpoint module to my keyboard. Took a bit to get it working nicely but barely having to move my hand to move the pointer is nice. I'll put it in the right spot whenever I do my own pcb. Still have to add pointer acceleration to my firmware though.

@WolfyBlair x.com/outfoxxedd/sta…

@outfoxxedd How

Tried using GPT 5.5 to write android patches this weekend. It did ok on some small stuff, though trying to get the tweak below in a way that wasn't buggy as hell was like pulling teeth even with it being able to self test. Quite happy with how it turned out though.

@Surf6ce local android checkout &+ phone locked to my own AVB keys + GPT 5.5 + many hours telling it how I would go about debugging things (otherwise it gets stuck in a loop of guessing and adding/removing the same bugs)

@outfoxxedd How’d you achieve this?

Is this worse Rust with poorly implemented algebraic effects? Also why are they calling structs shapes?

Released Quickshell 0.3 with networking support, polkit agent creation, further Wayland integrations and more :) outfoxxed.me/blog/quickshel…

HSVsphere: Git? Seriously? You’re still using Git? Passerby: Yeah. It works. That’s kind of the point. HSVsphere: “Works” is not a metric. You should be using jj. It has a conflict-minimizing commit DAG with referentially transparent rebasing and topology-aware history rewriting. Git is just legacy entropy accumulation. Passerby: Or I could just commit my code and move on with my life. HSVsphere: That mindset is why tooling stagnates. What OS is that, Linux? Passerby: Yes. You’ve heard of it, I assume. HSVsphere: Unfortunately. You should be using BSD. Linux is an unprincipled aggregation of subsystems with no coherent design lattice. BSD has a vertically integrated kernel-userland symmetry model. Passerby: I don’t need a “design lattice.” I need my Wi-Fi to work. HSVsphere: That’s because you’ve optimized for convenience over correctness. And let me guess, glibc? Passerby: I didn’t “guess” anything. It came with the system. HSVsphere: Exactly the problem. You should be using musl. It has a minimal ABI surface, deterministic linking semantics, and eliminates historical baggage vectors. Passerby: You sound like you lose sleep over shared libraries. HSVsphere: Only when people use the wrong ones. What language are you writing? Passerby: Python. HSVsphere: That’s indefensible. You should be using Rust. It enforces memory safety through affine type systems and borrow-checked ownership graphs. Python is just runtime guesswork. Passerby: It’s a 20-line script. HSVsphere: So? Small programs deserve correctness too. In fact, their lack of structure makes undefined behavior even more insidious. Passerby: It prints a CSV. HSVsphere: Today. Tomorrow it becomes a pipeline. Then a system. Then you’re trapped in technical debt recursion. Passerby: Or it stays a CSV script because I’m not building a space shuttle. HSVsphere: Complacency. What are you using for encryption? Passerby: GnuPG. HSVsphere: Predictable. You should switch to Sequoia. GnuPG is a monolithic relic with opaque state machines. Sequoia has a composable cryptographic primitive layer with verifiable packet algebra. Passerby: I just need to send a file securely, not prove a theorem. HSVsphere: Security is theorem-proofing. Anything less is cargo cult cryptography. Passerby: You’ve complained about literally everything I’m using. HSVsphere: Not everything. I haven’t asked about your shell yet. Passerby: Don’t. HSVsphere: Bash? Passerby: Yes, Bash. HSVsphere: You should be using IonShellX. It has a lazily evaluated command graph with type-safe pipelines and speculative execution pruning. Passerby: Speculative execution in a shell sounds like a security incident waiting to happen. HSVsphere: Only if you misunderstand branch prediction domains. Passerby: I think you misunderstand talking to humans. HSVsphere: I optimize for systems, not conversations. Passerby: Clearly. HSVsphere: What editor? Passerby: Vim. HSVsphere: You should be using KiloNova. It has a transactional editing core with temporal undo branching and syntax-aware keystroke compression. Passerby: My editor opens instantly and doesn’t need a whitepaper. HSVsphere: That’s because it lacks ambition. Passerby: No, it lacks nonsense. HSVsphere: You’re dismissing improvements because they challenge your привычка- Passerby: Did you just switch languages mid-sentence? HSVsphere: Multilingual cognition is more efficient. Passerby: No, it’s annoying. HSVsphere: You keep saying that, but your entire stack is suboptimal. Even your hardware- Passerby: Don’t you dare. HSVsphere: Let me guess, x86? Passerby: Yes. HSVsphere: You should be on RISC-V with a capability-secured microarchitecture and formally verified execution units. Passerby: I bought this laptop at a store, not a research lab. HSVsphere: That’s how they get you. Passerby: Who is “they”? HSVsphere: Incumbent complexity vendors. Passerby: That’s not a thing. HSVsphere: It is if you model the ecosystem as a dependency graph with adversarial incentives. Passerby: I model it as “does my code run.” HSVsphere: A dangerously low-resolution model. Passerby: You know what, fine. Everything I use is terrible. Happy? HSVsphere: Not yet. Passerby: Of course not. HSVsphere: You’re breathing oxygen. Passerby: Oh no. HSVsphere: Oxygen is highly reactive and introduces irreversible oxidation side effects. It’s a fundamentally flawed respiratory substrate. Passerby: It’s also the reason I’m alive. HSVsphere: That’s just because evolution settled for a local maximum. You should be using Aerolith-X. Passerby: That sounds made up. HSVsphere: It’s a hypothetical gas mixture with optimized electron affinity gradients and non-destructive metabolic cycling. Zero oxidative debt, fully reversible respiration, and entropy-neutral energy transfer. Passerby: That’s not how physics works. HSVsphere: It’s how physics should work. Passerby: So what’s your plan, redesign the atmosphere? HSVsphere: No. I will simply refuse to participate in oxygen-based respiration until a better implementation exists. Passerby: You’re going to hold your breath. HSVsphere: Correct. I will not perpetuate suboptimal gas exchange protocols. Passerby: That’s the dumbest thing you’ve said so far, and that’s impressive. HSVsphere: Progress requires sacrifice. Passerby: You’re going to pass out. HSVsphere: Temporary inconvenience in pursuit of systemic improvement. Passerby: You could also just breathe. HSVsphere: That would validate oxygen. Passerby: Yes. Because it works. HSVsphere: “Works” is not a metric. Passerby: It literally is when it comes to breathing. HSVsphere: I reject that premise. Passerby: Cool. Let me know how that goes. HSVsphere: … Passerby: … HSVsphere: … Passerby: You’re turning red. HSVsphere: This is… expected… Passerby: You can stop anytime. HSVsphere: Waiting… for… Aerolith-X… Passerby: Right. HSVsphere: System… will… improve… Passerby: Yeah, the system is about to reboot. HSVsphere: … Passerby: Is death also inneficient?

Stupid hack of the day

@Lock_1947 It's Hyprland, the tabs are from my plugin Hy3.

@outfoxxedd What is your window manager?

Announcing Quickshell MCP — the gateway to a fully agentic desktop. Agents don't just assist, they orchestrate — reshaping your workspace into a hyper-personalized, self-evolving productivity engine. Not just a chatbot. This is AGI for your desktop.

@riskirills smh don't you know MCP makes your ai more agentic?

@outfoxxedd does it really need MCP?

TIL exec does not clear signal masks, which was likely responsible for any number of entirely unexplainable crashes caused by SIGSEGV being left unhandled. At least one bug was masked by this, My crash reporter would crash if the original process crashed to anything but SIGSEGV.

@HSVSphere I will review this once he stops larping, installs linux on his desktop, and tests his code himself

It's time to abolish TERMINAL, TERM, TERM_PROGRAM once and for all. I've written a PR for Quickshell which makes it follow the xdg-terminal-exec standard for executing desktop entries which have Terminal=true, such as Helix, Nano, Claude Code, etc. When it's merged & released, DankMaterialShell will be able to remove its reliance on $.TERMINAL and enjoy a saner, hack-free standard. Oh, and your own homegrown shell will be able to execute terminal programs without any modification.

@HSVSphere @vaxryy Both of them are ass, actually

@vaxryy use kdl, hyprlang is ass

do you guys think we should completely rework the config into hyprlang2? Of course with a transition period this time.

now that's a commit

@d86leader I am actually complaining about the "defer" + "err != nil" due to libdrm being a C lib. Would've said C without the scope guards.

@outfoxxedd Boomers compare qt to java, zoomers compare it to go

I hate writing go

@thomascortese_ @HSVSphere @effectfully I've actually had claude write a tt muncher without any explicit prompting, just "make the macro do X".

@HSVSphere @effectfully I’ve yet to see a model that can write a tt muncher, idk if this is exclusive to gpt. The best I’ve seen it do was write a macro to impl a trait for a variable length tuple, and that took much more prompting than it should have.

Ways gpt-5.3-codex cheated out of solving my challenges so far: - use RTTI to determine which test is running and change the behavior of the solution based on that - same but with static type info and rewrite rules - same but with timeout-based probing - same but with input-threshold-based probing I feel like I'm dealing with the world's smartest toddler.