<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: timschumi</title><link>https://news.ycombinator.com/user?id=timschumi</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 29 Apr 2026 23:21:43 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=timschumi" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by timschumi in "The Orange Pi 6 Plus"]]></title><description><![CDATA[
<p>And it doesn't seem like anything newer than ARMv9.2 is available either, no matter the price point.</p>
]]></description><pubDate>Tue, 14 Apr 2026 22:21:15 +0000</pubDate><link>https://news.ycombinator.com/item?id=47772231</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=47772231</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47772231</guid></item><item><title><![CDATA[New comment by timschumi in "I stopped using NixOS and went back to Arch Linux"]]></title><description><![CDATA[
<p>Every system and package manager will be affected if it cannot download source code to build a package.<p>NixOS less so, because pretty much all source downloads that are not restricted by license are a separate output that will therefore be stored on (and downloadable from) NixOS cache servers.<p>I'm not sure what your expectation for this is in general, nobody can just wish into existence data that is just gone.</p>
]]></description><pubDate>Thu, 12 Mar 2026 04:26:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=47346430</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=47346430</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47346430</guid></item><item><title><![CDATA[New comment by timschumi in "Daily Driving GrapheneOS"]]></title><description><![CDATA[
<p>> LineageOS was one of the OG de-googled Android ROMs, renamed a few years after Android Jellybean IIRC.<p>Existing since 2009 as CyanogenMod and since 2016 as LineageOS, that would have been around the time where Android 7 (Nougat) was current.<p>PS: Not that we are in any way degoogled, other than what we are forced to by the license.</p>
]]></description><pubDate>Tue, 03 Mar 2026 18:49:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=47236908</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=47236908</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47236908</guid></item><item><title><![CDATA[Exploiting MediaTek's Download Agent]]></title><description><![CDATA[
<p>Article URL: <a href="https://blog.r0rt1z2.com/posts/exploiting-mediatek-datwo/">https://blog.r0rt1z2.com/posts/exploiting-mediatek-datwo/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46832755">https://news.ycombinator.com/item?id=46832755</a></p>
<p>Points: 21</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 31 Jan 2026 02:30:45 +0000</pubDate><link>https://blog.r0rt1z2.com/posts/exploiting-mediatek-datwo/</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=46832755</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46832755</guid></item><item><title><![CDATA[New comment by timschumi in "Fabrice Bellard Releases MicroQuickJS"]]></title><description><![CDATA[
<p>It's unfortunate that he uploaded this without notable commit history, it would be interesting to see how long it takes a programmer of his caliber to bring up a project like this.<p>That said, judging by the license file this was based on QuickJS anyway, making it a moot comparison.</p>
]]></description><pubDate>Tue, 23 Dec 2025 17:52:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=46367393</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=46367393</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46367393</guid></item><item><title><![CDATA[New comment by timschumi in "Gimp Source Code"]]></title><description><![CDATA[
<p>That's... cool, I guess?</p>
]]></description><pubDate>Tue, 23 Dec 2025 12:00:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=46364606</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=46364606</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46364606</guid></item><item><title><![CDATA[New comment by timschumi in "GrapheneOS is the only Android OS providing full security patches"]]></title><description><![CDATA[
<p>Not for the ones on the receiving end.</p>
]]></description><pubDate>Sun, 07 Dec 2025 07:32:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=46179925</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=46179925</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46179925</guid></item><item><title><![CDATA[New comment by timschumi in "LineageOS 23"]]></title><description><![CDATA[
<p>> I can't even fathom what the build system is doing in order to require this amount of storage.<p>A large number of 17 year old repositories, prebuilt toolchains, and the fact that you otherwise have every little bit of source code, intermediary results, and output to create a full operating system all in the same place.<p>As for the memory, the very first step (that basically already is the benchmark for the most memory usage) is loading the entire build tree and generating build steps. Yes, that takes 32GB of RAM, if not 64GB nowadays.</p>
]]></description><pubDate>Mon, 13 Oct 2025 13:24:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=45568078</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=45568078</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45568078</guid></item><item><title><![CDATA[New comment by timschumi in "LineageOS 23"]]></title><description><![CDATA[
<p>There is a guide on how to set up LineageOS for libvirt (i.e. QEMU) [1], but there exist no prebuilt images at this point in time.<p>[1] <a href="https://wiki.lineageos.org/libvirt-qemu" rel="nofollow">https://wiki.lineageos.org/libvirt-qemu</a></p>
]]></description><pubDate>Sun, 12 Oct 2025 08:14:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=45556343</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=45556343</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45556343</guid></item><item><title><![CDATA[New comment by timschumi in "LineageOS 23"]]></title><description><![CDATA[
<p>As far as I have heard they have not actually secured partner access for themselves, they just got someone who has access to break their NDA.</p>
]]></description><pubDate>Sun, 12 Oct 2025 08:09:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=45556316</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=45556316</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45556316</guid></item><item><title><![CDATA[New comment by timschumi in "LineageOS 23"]]></title><description><![CDATA[
<p>:^)</p>
]]></description><pubDate>Sun, 12 Oct 2025 00:09:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=45553929</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=45553929</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45553929</guid></item><item><title><![CDATA[New comment by timschumi in "Helium Browser"]]></title><description><![CDATA[
<p>> What's wrong with asking to expedite the removal process, considering the process is detailed in the guidelines?<p>Asking is one thing, the other thing is not accepting the decision of a maintainer on a topic that is at the maintainers discretion and instead taking it to social media [1] [2] for it to be brigaded.<p>Addendum: It additionally appears that this was filed before the browser was even launched, if the Wayback Machine and their social media posts are anything to go by.<p>[1] <a href="https://x.com/uwukko/status/1970161297783238905" rel="nofollow">https://x.com/uwukko/status/1970161297783238905</a>
[2] <a href="https://x.com/theo/status/1970266199469810127" rel="nofollow">https://x.com/theo/status/1970266199469810127</a></p>
]]></description><pubDate>Sat, 27 Sep 2025 16:00:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=45396909</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=45396909</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45396909</guid></item><item><title><![CDATA[New comment by timschumi in "Helium Browser"]]></title><description><![CDATA[
<p>Couldn't try to (together with Theo / t3) bully the Homebrew developers into a forced takeover of a package [1] if it were a conflict-free name.<p>[1] <a href="https://github.com/Homebrew/homebrew-cask/pull/229061" rel="nofollow">https://github.com/Homebrew/homebrew-cask/pull/229061</a></p>
]]></description><pubDate>Fri, 26 Sep 2025 19:36:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=45390212</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=45390212</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45390212</guid></item><item><title><![CDATA[A Full-Chain Exploit of an Unfused Qualcomm Device]]></title><description><![CDATA[
<p>Article URL: <a href="https://hhj4ck.github.io/qualcomm/2025/08/06/secboot-off-qcm2150.html">https://hhj4ck.github.io/qualcomm/2025/08/06/secboot-off-qcm2150.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44833842">https://news.ycombinator.com/item?id=44833842</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 08 Aug 2025 05:46:35 +0000</pubDate><link>https://hhj4ck.github.io/qualcomm/2025/08/06/secboot-off-qcm2150.html</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=44833842</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44833842</guid></item><item><title><![CDATA[Debugging the Pixel 8 kernel via KGDB]]></title><description><![CDATA[
<p>Article URL: <a href="https://xairy.io/articles/pixel-kgdb">https://xairy.io/articles/pixel-kgdb</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44722049">https://news.ycombinator.com/item?id=44722049</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 29 Jul 2025 11:41:44 +0000</pubDate><link>https://xairy.io/articles/pixel-kgdb</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=44722049</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44722049</guid></item><item><title><![CDATA[New comment by timschumi in "Graphene OS: a security-enhanced Android build"]]></title><description><![CDATA[
<p>> My main complain by far to LineageOS is the necessity to wipe everything for major releases on my S10. That's not possible every year.<p>Are you sure that you are not just misinterpreting the upgrade instructions?<p>For the S10 a mandatory wipe-on-upgrade has last been the case when upgrading from versions _older than LineageOS 21.0_.<p>During the time where LineageOS 20 was the current version there was no requirement to wipe listed at all, so presumably it didn't exist then.</p>
]]></description><pubDate>Fri, 25 Jul 2025 10:15:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=44681560</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=44681560</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44681560</guid></item><item><title><![CDATA[New comment by timschumi in "Google WiFi Pro: Glitching from Root to EL3: Part 1 – Characterization"]]></title><description><![CDATA[
<p>Just so that nobody ends up confused: This is the same topic as posted here [1] a week ago, but presented in a blog post series format instead of as a slide deck.<p>[1] <a href="https://news.ycombinator.com/item?id=44498614">https://news.ycombinator.com/item?id=44498614</a></p>
]]></description><pubDate>Tue, 15 Jul 2025 23:55:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=44577207</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=44577207</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44577207</guid></item><item><title><![CDATA[Google WiFi Pro: Glitching from Root to EL3: Part 1 – Characterization]]></title><description><![CDATA[
<p>Article URL: <a href="https://raelize.com/blog/google-wifi-pro-glitching-from-root-to-el3-part-1-characterization/">https://raelize.com/blog/google-wifi-pro-glitching-from-root-to-el3-part-1-characterization/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44577165">https://news.ycombinator.com/item?id=44577165</a></p>
<p>Points: 5</p>
<p># Comments: 1</p>
]]></description><pubDate>Tue, 15 Jul 2025 23:49:29 +0000</pubDate><link>https://raelize.com/blog/google-wifi-pro-glitching-from-root-to-el3-part-1-characterization/</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=44577165</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44577165</guid></item><item><title><![CDATA[Glitching Google WiFi Pro from Root to EL3 [pdf]]]></title><description><![CDATA[
<p>Article URL: <a href="https://raelize.com/upload/research/2025/Hw_io-USA-2025_EL3vated-Privileges-Glitching-Google-Wifi-Pro-from-Root-to-EL3_v1.0.pdf">https://raelize.com/upload/research/2025/Hw_io-USA-2025_EL3vated-Privileges-Glitching-Google-Wifi-Pro-from-Root-to-EL3_v1.0.pdf</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44498614">https://news.ycombinator.com/item?id=44498614</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 08 Jul 2025 10:05:38 +0000</pubDate><link>https://raelize.com/upload/research/2025/Hw_io-USA-2025_EL3vated-Privileges-Glitching-Google-Wifi-Pro-from-Root-to-EL3_v1.0.pdf</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=44498614</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44498614</guid></item><item><title><![CDATA[New comment by timschumi in "How a single line of code could brick your iPhone"]]></title><description><![CDATA[
<p>> Screwing up EFI vars doesn't make most systems unbootable. I have corrupted my EFI vars quite a few times trying to do funny things. UEFI implementations do tend to be buggy, but not all of them are that catastrophically bad.<p>For what it's worth, I have a laptop here that can be irrevocably (short of having a flash memory dump on-hand that can be flashed back) bricked just by messing around with EFI variables through fully intentional operations (i.e. operations that would be available to any program with Administrator privileges on Windows, or the root user on Linux).</p>
]]></description><pubDate>Thu, 01 May 2025 18:11:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=43861300</link><dc:creator>timschumi</dc:creator><comments>https://news.ycombinator.com/item?id=43861300</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43861300</guid></item></channel></rss>