PACO.IO

Obsidian Vault Portal v2.0
guest@paco.io:~$cat "_posts/2026-08-09-ptir-evening-briefing.md"

Verification cutoff: August 9, 2026, evening edition.

Executive Summary

Two open-source projects merit a short look tonight. Pingularity is a new single-binary connectivity monitor with unusually explicit local-only defaults, but its pre-1.0 status calls for a contained trial rather than immediate infrastructure adoption. ESP32-AI runs a 28.9-million-parameter text model entirely on an ESP32-S3; its output is deliberately limited, but its tiered-memory design is a compact lesson in local AI engineering.

Action Queue

1. Inspect Pingularity before considering a contained Linux trial

Urgency: This week
Importance: ★★★★☆

What it is: Pingularity is an MIT-licensed, single-binary internet monitor for latency, outages, IPv4/IPv6 status, scheduled Ookla or iperf3 tests, SQLite history, alerts, and optional Prometheus metrics. Version 0.60.3 was released August 8 with signed-off release assets and SHA-256 checksums for Linux, macOS, and Windows.

Why it matters: A local history of latency and outages can distinguish an ISP problem from a host or service problem without sending monitoring history to another dashboard provider. The project also starts localhost-only—even in a container—which is a better default than many young self-hosted dashboards.

Recommended action: Read the security and access sections first. If the design still fits, verify the release checksum and test the RPM or static binary on a noncritical Linux host with the dashboard left localhost-only. Compare a day of its results with existing router or ISP evidence. Do not expose it to a LAN or reverse proxy until login is enabled; use TLS in front of it for any untrusted network.

Status: Repository, MIT license, security policy, documentation, checksums, and v0.60.3 release verified August 9, 2026. This is a very young, pre-1.0 project, so its architecture and upgrade behavior should be treated as unsettled.
Deadline: No deadline.
Cost: Genuinely free and open source under the MIT License; no trial, regular price, certificate, or badge. Automated speed tests may consume substantial bandwidth.
Requirements: Linux, macOS, or Windows on amd64/arm64; roughly 6 MB for the binary plus SQLite history; raw-socket capability for its traceroute panel; and administrator privileges only when installing it as a system service. Building from source requires Go 1.25.12 or later.
Official links: Repository and documentation · v0.60.3 release and checksums · Security policy

2. Save ESP32-AI as an honest example of extreme local inference

Urgency: No deadline
Importance: ★★★★☆

What it is: ESP32-AI is an MIT-licensed experiment that runs a 28.9-million-parameter, 4-bit model entirely on an ESP32-S3 with 512 KB SRAM, 8 MB PSRAM, and 16 MB flash. The author reports 9.88 tokens per second by keeping a 25-million-parameter lookup table in flash and reserving faster memory for frequently used computation.

Why it matters: The project demonstrates that “local AI” is a memory-placement problem as much as a model-size problem. It also states its limits clearly: the TinyStories model produces short fiction but cannot reliably answer questions, follow instructions, write code, or supply facts.

Recommended action: Read the README’s “Why it is hard” and “What it does not” sections, then save the memory-tier diagram as a teaching example. Reproduce the project only if the embedded-systems exercise itself is the goal; it is not a substitute for a useful desktop local LLM.

Status: Source, measurements, limitations, deployment commands, and MIT license verified August 9, 2026; the repository was published July 23, 2026 and remains active.
Deadline: No deadline.
Cost: Software, model tooling, and source are genuinely free under the MIT License. Compatible ESP32-S3 hardware and a display are sold separately; no official fixed or regular hardware price is established by the project. No trial, certificate, or badge.
Requirements: Reading requires only a browser. Reproduction requires an ESP32-S3 N16R8-class board, an I2C display, the project’s firmware toolchain, and enough network access to fetch one model before flashing it to the offline device.
Official links: ESP32-AI repository · Measured results · Gemma 3n Per-Layer Embeddings background

Free Software

Both Pingularity and ESP32-AI are genuinely free, MIT-licensed software. Pingularity has downloadable packages; ESP32-AI requires separate embedded hardware to reproduce.

Free Courses & Certifications

No noteworthy developments today.

AI

ESP32-AI is valuable because it separates architectural achievement from model capability. Moving rarely accessed parameters to flash expands what fits, but it does not make a small model knowledgeable or instruction-following.

Open Source

Both projects publish source and permissive licenses. Pingularity additionally publishes a security policy, release checksums, a documented outbound-call inventory, and conservative network-access defaults—useful signals, though not substitutes for maturity or an independent audit.

GitHub Discoveries

Web Development

Pingularity’s embedded dashboard is a useful case study in shipping a complete web interface inside one Go binary. Its repository documentation also shows why access control, authentication, API exposure, and reverse-proxy TLS must be designed together.

Linux & Self-Hosting

Pingularity’s Linux packages install an unprivileged systemd service and grant only the raw-socket capability needed for traceroute. A trial should stay on a noncritical host and localhost until its measurements and upgrade behavior earn trust.

Technical Books

No noteworthy developments today.

Newsletter Highlights

A MakeUseOf homelab roundup was a discovery lead, not proof. Its individual recommendations were not repeated here. The two selected projects were independently checked through their source repositories, licenses, documentation, releases, and measured limitations. The read-only Spam and Trash recovery pass found no exceptional new ICYMI item.

Reddit Pulse

The weekly r/selfhosted project thread surfaced Pingularity. Community enthusiasm was not treated as validation; the recommendation rests on the project’s own release artifacts, checksums, source, security policy, and documented defaults.

Teaching Corner

Use ESP32-AI’s memory layout to ask students where data belongs when SRAM is fastest and smallest, PSRAM is larger and slower, and flash is largest but least suitable for repeated reads. Then ask the more important question: why does fitting 28.9 million parameters onto a chip not automatically create a capable assistant?

PKb Candidates

  • For self-hosted dashboards, “local-only by default” is a meaningful security property; “self-hosted” alone is not.
  • Verify checksums before installing release binaries, especially from young projects.
  • Once a dashboard is reachable beyond localhost, authentication and transport encryption become separate requirements.
  • Model parameter count does not describe usefulness; dataset, architecture, task, and evaluation matter.
  • Memory hierarchy can make an otherwise impossible model fit by placing data according to access frequency.

Small self-hosted tools are increasingly shipping as static binaries with embedded interfaces and SQLite rather than multi-container stacks. At the other extreme, local AI work is pushing inference into microcontrollers by treating flash, PSRAM, and SRAM as distinct architectural resources. Both trends reduce infrastructure requirements, but neither eliminates the need for threat modeling or honest capability evaluation.

Sources Consulted

Official GitHub repositories, licenses, security policies, documentation, release assets, and checksums for Pingularity and ESP32-AI; current technology newsletters used only for discovery; the r/selfhosted project thread; Grumpy Old Geeks show notes; official-source searches; and a controlled read-only Gmail Spam/Trash recovery pass. No unchanged morning item was repeated.