Article URL: https://twitter.com/lemire/status/2082851447499088173 Comments URL: https://news.ycombinator.com/item?id=49118474 Points: 15 # Comments: 1
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
A developer auditing a WooCommerce-LearnDash site found 12,301 WebP sidecar files left behind by a previously uninstalled image optimizer plugin, consuming 241MB of storage and burdening backups and malware scans. The files, generated by EWWW Image Optimizer, were completely unreferenced and served no purpose once the plugin was removed. A separate audit revealed that a plugin called disable-thumbnails-and-threshold had silently stripped 14 registered image sizes at runtime, meaning WooCommerce product thumbnails were never actually generated on disk. Rather than proceeding with a new WebP conversion tool, the developer resolved these deeper structural issues first, noting that installing another optimizer would have compounded the existing problems. The case highlights the importance of auditing inherited WordPress sites for orphaned files and misconfigured plugins before adding new optimization layers.
A developer built a Perplexity-style search assistant using a Bun backend, React 19 frontend, Tavily for search, and OpenRouter as the model provider. The system allows a language model to autonomously decide when to call a web search tool, loop through results, and stream cited answers to users. Before publishing about the project, the developer paused to honestly assess whether the build qualified as a true 'agent harness' or merely a well-dressed API call. After reviewing the core agent loop code, they confirmed it meets the harness definition: the model controls tool use, the loop iterates until completion, context is trimmed, and output is a structured event stream. The developer acknowledged the build is a single-tool harness with no retries or provider fallback, and noted that a more robust multi-tool version remains a future goal.
A developer-focused article highlights 22 built-in browser capabilities that eliminate the need for third-party JavaScript libraries in many common use cases. Features such as native dialogs, the Popover API, color pickers, and the Clipboard API are now supported directly in modern browsers without additional dependencies. The Web Share API, lazy image loading, smooth scrolling via CSS, and the Geolocation API are among the other built-in tools covered. HTML elements like details and summary enable accordion-style components, while the Notification API allows desktop alerts, all natively. The piece argues that developers can write less code and reduce reliance on external packages by leveraging these modern browser standards.
UTM parameters lack built-in validation, meaning inconsistent tagging by team members over time can silently fragment analytics data into untrustworthy reports. Key rules include always using lowercase letters, hyphens instead of spaces or underscores, and appending the year to campaign names to avoid data stacking across recurring events. Marketers often confuse utm_source and utm_medium — source identifies the specific place (e.g., instagram), while medium describes the channel type (e.g., social). UTM tags should only be applied to external links, as tagging internal site navigation can overwrite original referrer data and corrupt attribution. Maintaining a short, team-accessible reference list of approved parameter values is recommended to prevent gradual naming drift across campaigns.
Discussion (0)
Log in to join the discussion and vote.
Log in