<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Allec Terrezo</title>
    <description>The latest articles on DEV Community by Allec Terrezo (@allec_terrezo).</description>
    <link>https://dev.to/allec_terrezo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3963544%2F6eda5177-ee88-4b2b-bc81-f75502cd2017.jpeg</url>
      <title>DEV Community: Allec Terrezo</title>
      <link>https://dev.to/allec_terrezo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/allec_terrezo"/>
    <language>en</language>
    <item>
      <title>Why standard speed tests aren't enough (and why I open-sourced my own iOS network auditor)</title>
      <dc:creator>Allec Terrezo</dc:creator>
      <pubDate>Tue, 02 Jun 2026 01:08:47 +0000</pubDate>
      <link>https://dev.to/allec_terrezo/why-standard-speed-tests-arent-enough-and-why-i-open-sourced-my-own-ios-network-auditor-33bg</link>
      <guid>https://dev.to/allec_terrezo/why-standard-speed-tests-arent-enough-and-why-i-open-sourced-my-own-ios-network-auditor-33bg</guid>
      <description>&lt;p&gt;If you've ever dealt with real time pipelines, you know the frustration: severe jitter or micro disconnections completely ruin the experience, but standard network diagnostics often say everything is fine. Normal speed tests are too easy to forge and frequently mask the real issues that cause SLA breaches.&lt;br&gt;
I wanted a way to generate mathematically undeniable, tamper evident proof of network degradation. The biggest architectural constraint was privacy. Offloading the report generation to a cloud API was a non starter because it breaks the chain of custody.&lt;br&gt;
To solve this, I built NetProof. It is an iOS network auditing tool that handles RSA-2048 signing and PDF generation purely on-device. I originally considered keeping this as a closed, paid product, but I realized that true technical transparency requires open code. So, I’ve made it fully open-source.&lt;br&gt;
I'd love for you to check out the repository, review the architecture, and see how the local signing is implemented:&lt;br&gt;
&lt;a href="https://github.com/AllecTerrezo/netproof-ios-audit" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;br&gt;
I am looking for feedback from other engineers on the implementation. How do you handle SLA breaches, jitter, and network monitoring in your own stacks? Let's discuss it in the comments.&lt;/p&gt;

</description>
      <category>ios</category>
      <category>networking</category>
      <category>opensource</category>
      <category>security</category>
    </item>
  </channel>
</rss>
