IdeaWell

Project ideas from Hacker News discussions.

Whistleblower warns Postal Service mail ballot system has catastrophic problems

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1 – Alleged deliberate interference / voter suppression
Many commenters view the USPS‑driven ballot‑screening policy as a purposeful attempt to create chaos and suppress votes that favor the opposition.
- “The administration doesn't care about fixing whatever hypothetical mail ballot fraud may or may not exist; they are doing this to inject chaos into the election results, giving them cover to claim any result they want or even to just throw out the results entirely. Catastrophic problems are the means to that end.” – hackyhacky
- “There is something incredibly cancerous when a certain party abhors democracy, and does everything they can to undermine the voting rights or access to groups they think won't vote for them.” – llm_nerd
- “This thing is unmistakable malice, not mere incompetence.” – Terr_

Theme 2 – Statistical and procedural flaws in the sampling approach
Critics argue that the 400‑out‑of‑10 000 sample is statistically weak, easily gamed, and could produce high false‑positive or false‑negative rates.
- “That sample is wrong for statistics, 4% is literally not significant. It's also too much for sample controls.” – downrightmike
- “Some nefarious actor could find 100 messed up ballots and include one in each sample of 400, and viola! 100 ballots invalidates 1 million votes.” – peterleiser
- “Assuming they check 400 out of 10k… this system would catch it 98,3% of the time. Pretty good, I'd say.” – grim_io (showing the disputed confidence level)
- “Ok now what's the potential false positive rate?” – tenuousemphasis

Theme 3 – Debate over the USPS’s role and the legality of federal involvement in state‑run voting
Discussion centers on whether the Postal Service, as a federal entity, may lawfully intervene in state election procedures.
- “good thing it's completely illegal for the federal government to interfere with state voting proceedure” – ck2
- “USPS is the government. The wrong government! Voter rolls etc. are state responsibilities, not a federal ones.” – Terr_
- “Fallacy of composition. It would be factual to say that the USPS is part of the federal government, but then the statement becomes completely irrelevant.” – jibal
- “You realize USPS is the government right? It’s literally in the Constitution” – mcmcmc (counter‑point)
- “And no, the USPS is not in the Constitution. Article I Section 8 gives Congress the power …” – jibal (clarifying the legislative origin)

🚀 Project Ideas

BallotTrax – Real‑Time Mail‑In Ballot Tracking & Verification Portal

Summary

  • Provides voters and election officials with live status updates for each mail‑in ballot using QR‑code tracking and USPS scan logs.
  • Core value proposition: eliminates uncertainty about ballot receipt and flags mismatches instantly, reducing the risk of whole‑batch rejections.

Details

Key Value
Target Audience Voters, state/local election officials, watchdog groups
Core Feature End‑to‑end ballot tracking with QR codes, automated alerts when a batch scan fails or a ballot is missing
Tech Stack React (frontend), Node.js/Go (backend), PostgreSQL, AWS Lambda/API Gateway, optional USPS Integration API
Difficulty Medium
Monetization Revenue-ready: subscription per jurisdiction ($0.01 per tracked ballot) or tiered SaaS plans

Notes

  • HN users criticized the current “sample‑based” verification as error‑prone: “If even one barcode on a single ballot in the batch doesn’t scan … the entire batch would be rejected” (ck2). BallotTrax gives voters a direct way to see if their ballot made it through.
  • Quote from goalieca: “If I take a look, through a security lens, of the existing mail in process from registration to recording votes, it’s quite shocking.” – BallotTrax adds transparency that addresses that shock.
  • Enables public audits and discussion on ballot handling efficiency, potentially reducing partisan claims of fraud.

VoteSampleOpt – Interactive Statistical Tool for Optimal Mail‑Ballot Sample Sizing

Summary

  • Helps election officials determine the smallest sample size needed to detect fraud or errors with a desired confidence level while minimizing false‑positive batch rejections.
  • Core value proposition: replaces arbitrary 400‑out‑of‑10 000 sampling with data‑driven, risk‑based sample calculations.

Details

Key Value
Target Audience State election officials, auditors, academic researchers, advocacy groups
Core Feature Web‑based calculator that simulates batch verification outcomes, outputs required sample size for user‑specified detection power and false‑positive tolerance
Tech Stack Python (Streamlit), NumPy/SciPy, hosted on Vercel or Heroku; optional Docker container for on‑premise use
Difficulty Low-Medium
Monetization Hobby (open‑source MIT license) – can be adopted freely by jurisdictions

Notes

  • Commenters highlighted statistical flaws: “That sample is wrong for statistics, 4% is literally not significant.” (downrightmike) and “They will use 400 ballots from each batch as a sample, and if anything is wrong for one of those 400 sample ballots, then the entire batch of 10,000 is sent back.” (peterleiser). VoteSampleOpt directly addresses these concerns.
  • Provides a concrete tool for discussion on HN about proper statistical practices in election security.
  • Encourages practical utility: officials can plug in their batch size, expected error rate, and get an optimal sample, reducing unnecessary batch rejections.

BallotGuard – Tamper‑Evident Cryptographic Ballot Receipt System

Summary

  • Issues each voter a unique, zero‑knowledge proof‑based receipt that proves their ballot was included in the final tally without revealing how they voted.
  • Core value proposition: gives voters verifiable confidence that their mail‑in ballot was counted, mitigating fears of selective discarding or batch rejection.

Details

Key Value
Target Audience Voters, election integrity NGOs, advocacy groups, technologists
Core Feature Cryptographic receipt generation and verification via a public ledger; voters can check online that their receipt corresponds to a counted ballot
Tech Stack Rust/Go for zk‑SNARKs (circom or halo2), PostgreSQL for metadata, React frontend, IPFS or decentralized storage for receipts, optional Ethereum L2 for public audit trail
Difficulty High
Monetization Revenue-ready: per‑ballot fee ($0.005) or grant‑funded model with optional premium verification UI

Notes

  • HN users expressed fear of deliberate chaos: “Catastrophic problems are the means to that end.” (hackyhacky). BallotGuard provides a cryptographic guarantee that even if a batch is delayed, the voter can prove their ballot was counted.
  • Quote from llm_nerd: “They’ve already gotten a ruling that ballots received after a cutoff do not count… engineering assurances that they get to choose from where ballots can be selectively delayed.” – BallotGuard counters selective delay by giving voters immutable proof of inclusion.
  • Sparks discussion on balancing privacy with verifiability, a hot topic on HN, and offers a practical utility for restoring trust in mail‑in voting.

Read Later