<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on MrAgui</title><link>https://mragui.dev/posts/</link><description>Recent content in Posts on MrAgui</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mragui.dev/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Open firmware for the 3.5" NerdQAxe++ clones, with optional Ethernet</title><link>https://mragui.dev/posts/nerdqaxe-big-screen-ethernet-firmware/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://mragui.dev/posts/nerdqaxe-big-screen-ethernet-firmware/</guid><description>&lt;p>The NerdQAxe++ is a small open-source Bitcoin (SHA-256) miner. On AliExpress you&amp;rsquo;ll find clones with a bigger &lt;strong>3.5&amp;quot; (480×320) screen&lt;/strong>, from sellers such as YYSlupping. The hardware is nice. The firmware is the problem.&lt;/p>
&lt;h2 id="the-problem-closed-firmware-on-an-open-source-miner">The problem: closed firmware on an open-source miner&lt;/h2>
&lt;p>These clones ship with &lt;strong>pre-installed firmware whose source code isn&amp;rsquo;t published&lt;/strong>. A miner has your pool login, your payout address and all your hashrate, and with closed firmware there&amp;rsquo;s no way to check what it does with them.&lt;/p></description></item><item><title>Building Fritzing 1.0.7 from source on macOS with one script</title><link>https://mragui.dev/posts/building-fritzing-on-macos/</link><pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate><guid>https://mragui.dev/posts/building-fritzing-on-macos/</guid><description>&lt;p>&lt;a href="https://fritzing.org">Fritzing&lt;/a> is a great tool for breadboard, schematic and PCB diagrams. It&amp;rsquo;s open source (GPLv3), but the prebuilt binaries are a paid download. You can build it yourself, but on macOS the build is fiddly: Fritzing expects a very specific set of dependencies in specific places.&lt;/p>
&lt;p>So I wrapped the whole build in one script: &lt;strong>&lt;a href="https://github.com/AguiMr/Fritzing-macos">Fritzing-macos&lt;/a>&lt;/strong>.&lt;/p>
&lt;h2 id="usage">Usage&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>git clone https://github.com/AguiMr/Fritzing-macos.git
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>cd Fritzing-macos
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>chmod +x build_fritzing_macos.sh
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>./build_fritzing_macos.sh
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You need &lt;a href="https://brew.sh">Homebrew&lt;/a> and the Xcode Command Line Tools. If the tools are missing, the script starts their install and asks you to run it again. The first build takes about 20–40 minutes. After that, re-running skips everything that&amp;rsquo;s already built.&lt;/p></description></item></channel></rss>