Maciej Rutkowski

Maciej Rutkowski

@macbirdie.net

I code for Apple platforms, build things that move and optionally push melted plastic through a hole. I like Star Treks and Missions Impossible. I made Headlines RSS for iOS (https://macbirdie.net/headlines). I like sync, self-hosting, and local LLMs.

304 followers116 following344 posts

By the way. I've been hunting for a new iOS Dev opportunity for the last 4 months. Want help with the iPhone Duo makeover? Launching a startup that needs an iOS app? I can set up the coding/building infrastructure, CI pipelines, architecture, and ship your product.

Wow, this is a huge change, kind of in line what Apple's been doing the past two years. xcodegen and in one way Tuist were the true heroes when it comes to keeping the Xcode project description sane in a multi-dev and agentic setup. JSON-based Xcode project format coming in Xcode 27.2 ❤️

I didn't even know such a movie was coming out but now I'm definitely seeing it after that review! 🔫🐓

Todd Vaziri@tvaziri.com

"The End of Oak Street" (2026) review: www.instagram.com/reels/Db_ybi...

Using Qwen 3.6 27B I wanted to reverse engineer the app that resets the waste counter in Epson printers which makes them otherwise unusable unless you pay up to change a variable in its config. It however refused due to DMCA and other consumer-hostile laws. Changed to an uncensored model and...

now i have a decrypted printer description file the app downloads from the internet, and a python script that resets the waste counter for any one of them. Impressed! Now I can actually fix the stuff I already paid for.

bought a broken UPS, fixed it, replaced battery, connected a router and a PoE switch to it, connected some devices through PoE throughout the home, power goes down, said devices stay powered on *surprised pikachu face*

how in the vibe coding hell is it that an OAuth session may expire WHILE using the product authenticated? how can one screw up the most common authentication scheme on the internet so badly?

I feel like during the last two years software quality has gone significantly down. What the hell is going on? People just stopped caring didn’t they.

Made an Ollama API proxy to llama-server's default OpenAI-style one so VSCode can use it natively without any extensions, err, and why is it writing a 500-word essay on dragons? is this some token use gauge calibration?

Some exciting new stuff in the PS5 jailbreak scene happened in the recent few weeks. Trying the new exploit with my 12.70 console, the console crashes on game exit (using a raunchy japanese Lua-based game); I thought, why don't I ask an seemingly all-knowing coding entity about the possible causes.

Claude was *THIS CLOSE* to calling the police on me - refused to talk about the topic completely. Ok then, I asked my own agent harness running on Qwen 27B and got a complete explanation how the exploit works, what the possible causes may be, and a fixed LUA source in the workspace to try out.

The resulting source took me a lot further in the exploit, but the game still crashed, and the kernel right after it, so there is some space for improvement. But THIS is the fundamental difference between being a token consumer, and a token producer.

Home Assistant finally executed an automation I set up *two years ago* that would check sun's position and cloud covering to figure out if it should lower one window shade to stop blinding me when sitting at the living room table. AGI is here.

I'm a dimwit. I've been running this power-hungry moster of a GPU, RTX3090, on a single PCI-E cable essentially - simply connected the two plugs from the same cable to GPU's sockets, instead of providing it with power from two separate rails. Symptoms? Voltage drops, crashes, oxidated pins.

Made a second cable out of a spare one I had from a different PSU and the improvement has been pretty dramatic. It just works now. And the recently added MTP support to llama.cpp made Qwen 3.6 27B really snappy. Good times for us local LLM masochists.

Have a question, go to google, enter the query, skip irrelevant product results, go to a website with the answer, skip the cookie banner, privacy banner, interrupting newsletter banner, interrupting cross promo banner, autoplayed silent video overlay. ✋ Have a question, tell Claude to find one. 👈

Funny that if I host our music at home from a server and something stops working (which it never does) it’s my job to fix it. But also, if Spotify is down for several hours, somehow it’s my job to fix that too.

Using port 8086 for a server exposing intel documents on finance and tech, that also tracks Intel's revival in CPU and AI space, is pretty funny. Even Hermes appreciated this genius move.

So, an update on self-hosted Qwen 3.6 crashing issues - looks like it was all LM Studio's fault all along - now running on llama-server again, with a a 150k context, 4096 ubatch, 2048 batch, KV cache at Q4_0, and only a few times llama-server simply shut down without any messages

which is a LOT better than crashing every time I came close to ~60k context or tried to compact the conversation plot twist - it's all still running on <vomit>Windows</vomit>, as it's on my gaming PC, so until my Arc Pro B70 arrives, I'm still stuck with this abomination of an OS

interesting how models love their waterfall, don't they even if I plan out a project with specific minimal complete functionality in each step with future iterations, they insist on developing complete layers instead - say, first backend, then frontend

Has an awesome sunday morning session with Claude before family woke up. Updated my motorized camera slider's stale firmware to make more room for new features, by changing partitioning, replacing some heavy C++ stream code with snprintf calls - gained >600KB free space, wooo.

View full thread

The physical slider is the next thing that needs "refactoring". I designed it in Blender almost 5 years ago. It handles big cameras, uses an aluminium extrusion as the base with the platform moving on pom wheels, so it's more of a prototype, but works great.

Want to make it more compact with all components nicely enclosed. Would be great to add encoders so I'm able to set up all intermediate steps simply by pointing the camera at the target, instead of fiddling with software sliders.

Has an awesome sunday morning session with Claude before family woke up. Updated my motorized camera slider's stale firmware to make more room for new features, by changing partitioning, replacing some heavy C++ stream code with snprintf calls - gained >600KB free space, wooo.

View full thread

Before that the iOS companion app also got vastly improved with new UI and refactored the code for better maintainability. So the stop motion feature has been planned out, was ready to start implementing, buuut I hit the daily ration of tokens - still ridiculous and distopian.

Finished all up in the following session, then jumped on my thinking rock at home, but before that I ensured to prevent Claude from having job security, by saving all research in documents in the repo. The new stack is working great, and the app is now pwetty.

Has an awesome sunday morning session with Claude before family woke up. Updated my motorized camera slider's stale firmware to make more room for new features, by changing partitioning, replacing some heavy C++ stream code with snprintf calls - gained >600KB free space, wooo.

Until now the slider only allowed recording timelapses (e.g. 5 hour star watching with a camera in bulb mode), or programmed movement for fast pans, but what was missing is the ability snap a, say, 13fps stop motion animation by advancing the frames manually, while keeping the motion curves.

From some initial testing with coding, Qwen 3.6 27B slaps. Haven’t seen any reasoning loops, so far no failed tool calls. Really smooth. At least for Golang and Swift projects. Much better experience than the predecessor. The model used: Q4_K_M, KV cache q4_0. And 4gb VRAM left. 🤘

Just as I said some nice things about it, entire morning spent on autopilot retry failures, incorrect tool calls in thinking blocks, my word. Gotta get to the bottom of this. Sometimes the model (or llama.cpp) just crashes, and prefill taking ages will cause timeouts too.

From some initial testing with coding, Qwen 3.6 27B slaps. Haven’t seen any reasoning loops, so far no failed tool calls. Really smooth. At least for Golang and Swift projects. Much better experience than the predecessor. The model used: Q4_K_M, KV cache q4_0. And 4gb VRAM left. 🤘