HackerNews Digest

ymawky is a static‑file web server written entirely in hand‑crafted ARM64 assembly for macOS (Apple Silicon). It operates without libc, using only syscalls, and follows a fork‑per‑connection model (debug mode disables forking). The server serves files from a configurable document root (default www/), automatically prepending this path, and provides custom error pages from err/. Supported HTTP methods are GET, PUT, DELETE, OPTIONS, and HEAD. Features include percent‑encoding decoding, path‑traversal protection, symlink rejection (O_NOFOLLOW_ANY), 10‑second receive timeout, and rate‑limited PUT uploads (default max 1 GiB, configurable via PUT_GRACE_SECS, PUT_MIN_BPS). It handles byte‑range requests, MIME type detection based on extensions, and directory listings. Configuration constants (e.g., DEFAULT_DIR, ERR_DIR, RECV_TIMEOUT, MAX_PROCS) are defined in config.S. macOS‑specific syscall conventions, error handling, fork return values, and certain flags (SO_NOSIGPIPE, renameatx_np) make porting to Linux require substantial adjustments. The server responds with a wide set of HTTP status codes and can be built with Xcode command‑line tools.

The page consists solely of an error notice indicating a failure to load the intended content (“Something went wrong, but don’t fret — let’s give it another shot”) and a placeholder for visual media. Under the “Images and Visual Content” heading, a single image entry is listed, identified only by an alt‑text label of a warning emoji (⚠️). No additional text, data, headings, or functional information is provided beyond this brief apology and the image placeholder. Consequently, the document contains no substantive narrative, technical details, or actionable content to summarize further.

Gemini API File Search now supports multimodal queries, enabling retrieval from text documents and images. Users can attach custom key‑value metadata (e.g., department, status) to unstructured files, and apply metadata filters at query time to narrow results, reducing irrelevant hits and improving RAG speed and accuracy. The service records page numbers for each indexed segment, allowing responses to be directly linked to source locations for precise verification. File upload and search are handled by the File Search tool, abstracting infrastructure concerns. Early adopters report strong performance on mixed‑modality scientific corpora and image‑rich collections, noting higher semantic retrieval quality, reduced hallucinations, and significant context‑window savings when indexing diagrams and other visual assets. The update emphasizes reliable, citation‑backed outputs across text and visual content.

None

The Internet Archive has launched a Swiss non‑profit foundation, Internet Archive Switzerland (https://internetarchive.ch/), based in St. Gallen. The organization will operate independently within Switzerland, initially concentrating on preserving endangered archives worldwide and archiving generative‑AI artifacts. It is coordinating a UNESCO‑linked conference in Paris (November 2026) to address protection of vulnerable collections. In partnership with the University of St. Gallen’s School of Computer Science, the foundation supports the “Gen AI Archive” project led by Prof. Damian Borth, aimed at systematically preserving AI models. The choice of St. Gallen leverages the city’s long archival tradition and strong academic environment. Internet Archive Switzerland joins other regional arms—Internet Archive, Internet Archive Canada, and Internet Archive Europe—to create a distributed, resilient digital library network. Roman Griesfelder serves as executive director and is the primary contact.

The author bans all unauthorised query strings on their site, citing concerns that query parameters are often used for tracking (e.g., ref, utm_source) and can abuse users. They argue that referral information should be obtained from the Referer header, and if absent it is likely intentional. Historically they used query strings for cache‑busting CSS files (e.g., ?t=…, &h=…) but now consider any such usage unnecessary and are willing to let those requests fail. If future functionality requires query parameters, only explicitly approved ones will be allowed. The restriction is enforced via a rule in the server’s Caddyfile configuration, which blocks any request containing a query string unless it matches a predefined whitelist. The post invites readers to test the behaviour by appending query strings to URLs.

The post announces a new, multi‑chapter online “Book” documenting the history of Visual Basic. Chapter 1, “Origins (1964–1992),” consists of six sequential articles covering: * The creation of Dartmouth BASIC and its early commercial implementations (1964‑1975). * Microsoft’s BASIC lineage from Altair to QBasic (1975‑1991) and the branding decision to retain “BASIC” in Visual Basic. * Alan Cooper’s Tripod drag‑and‑drop Windows shell (1985‑1988) and its sale to Microsoft, which introduced the VB form designer. * Project Thunder (1989‑1991), the internal codename merging a rejected shell tool with an embeddable BASIC interpreter, led by Scott Ferguson. * Bill Gates’s May 1989 BYTE Magazine pitch and the 1991 Windows launch, outlining Microsoft’s marketing narrative and $199 price point. * The simultaneous release of Visual Basic for Windows and for DOS (1991‑1992), their divergent code bases, and the rapid demise of the DOS version. The author emphasizes a focus on lesser‑known contributors (Cooper, Merker, Kratkin, Geary, Raab, Ferguson, Whitten) rather than the well‑documented Gates/Allen narratives, and notes upcoming chapters on version‑by‑version evolution and a “Notable Characters” directory.

The article critiques the common practice of using exposed Dupont jumper wires to access a device’s UART‑TTL pins (RX, TX, GND) for bootloader or recovery debugging, noting reliability, strain‑relief, and back‑feeding issues. It proposes adopting Julet connectors—robust, IP68‑rated M6 (or M8) plugs used on e‑bikes—as a standardized solution. Julet cables are available on AliExpress, come as pre‑tinned 20 cm pigtails, and can be assembled quickly with standard crimping tools. The author assigns red and black wires (adjacent to the notch) to TX/RX and blue to GND, using the arrow on Dupont housings to denote the RX side; the female socket on the device carries the red‑arrowed wire, while the male plug on the USB‑TTL adapter carries the black‑arrowed wire, ensuring correct cross‑connection. Strain relief is provided with zip ties. The three‑pin Julet plug remains compatible with larger 5‑ or 6‑pin sockets for future expansion, while different connector sizes (M8) can differentiate voltage levels (3.3 V vs. 5 V) and Micro‑Q adapters address lower‑voltage logic. This results in a cleaner, safer, plug‑and‑play serial interface.

FreeBSD-SA-26:13.exec, announced 2026‑04‑29, addresses a local privilege‑escalation vulnerability in the execve(2) system call (CVE‑2026‑7270). An operator‑precedence bug in the kernel permits a buffer overflow that can overwrite adjacent execve argument buffers, allowing an unprivileged user to gain superuser privileges. No workaround exists; remediation requires updating to a patched FreeBSD branch released after the correction dates. Affected releases include all supported FreeBSD versions (13, 14, 15) on amd64, arm64, and i386 (FreeBSD 13). Patching options are: * Base‑system package upgrades via `pkg upgrade -r FreeBSD-base` (amd64/arm64, 15.0‑RELEASE) followed by reboot. * Binary‑set updates via `freebsd-update fetch && freebsd-update install` (amd64/arm64 RELEASE, i386 13) followed by reboot. * Source‑code patch application using the provided `exec.patch` and recompiling the kernel. The fix is incorporated in specific Git commits for each branch (e.g., stable/15 c3e943e78e06, releng/15.0 934b48683c4f, stable/14 ae00a52921ca, etc.). Systems must be updated and rebooted to apply the correction.

rlisp is a weekend project that provides a Lisp‑style front‑end for Rust. Source files written as s‑expressions are transpiled to ordinary Rust code (.rs) and then compiled with rustc, preserving full Rust semantics: ownership, borrowing, lifetimes, generics, traits, pattern matching, and unsafe blocks. The tool implements a transparent syntax conversion without adding a runtime or garbage collector. Common Rust constructs (structs, enums, impl blocks, functions, macros, loops, match, if‑let, while‑let, etc.) have direct s‑expression equivalents, and binary operators are emitted as infix forms. rlisp’s macro system consists of compile‑time functions that transform s‑expressions; it uses quasiquote, unquote, and unquote‑splicing rather than the procedural‑macro token‑stream model. The project supports embedding raw Rust via a (rust "...") form. Missing features include some syntax such as turbofish (now fixed) and lifetime bounds (on the roadmap). The repository includes a CLI with commands to transpile, build, and run .lisp files.