Project ideas from Hacker News discussions.

Google is silently linking your phone number across all signed-in accounts

📝 Discussion Summary (Click to expand)

1. Google’s aggressive privacy‑eroding verification and tracking
Many commenters describe how Google now forces phone‑number linkage, QR‑code scans, and VPN‑based restrictions that make anonymous use nearly impossible.
- “Google is probably the most aggressive anti‑privacy big tech company currently operating.” – maxo133
- “The requirement to have a mobile device to scan a QR code to verify that you're human… Reverse SMS verification… You think of signing up using a VPN server in another country? The phone number you use to send the SMS from must also be from that country.” – maxo133
- “It's essentially almost impossible to create a Google account without giving up your identity, and your phone number often leads directly to your real‑life identity.” – maxo133

2. Motives: ad‑driven data hunger and regulatory pressure to curb fraud/bots
Users point out that Google’s data collection fuels its ad business and that governments push for stricter identity verification to fight scams, fraud, and bot activity.
- “More data = better ad sales.” – fred_is_fred
- “line go up” – baggachipz (referring to profit motive)
- “Governments have told them its time to start violating users privacy in order to combat these other problems.” – ninininino (linking regulatory demands to privacy loss)

3. User coping strategies and the sense of futility
Commenters discuss workarounds like carrying a second phone, separating accounts, or trying to opt‑out, while acknowledging the difficulty and limited effectiveness of such efforts.
- “I carry two phones now - since I have my 'privacy' enabled phone that basically has nothing on it… Trying to fight it takes an enormous amount of time and energy.” – burningChrome
- “Bene vixit, bene qui latuit.” (To live well is to live concealed.) – burningChrome
- “Having two phones is more common than you think… One is my work phone… other one is mine.” – mixdup
- “It did not leave a good taste that I had to do this after the fact, I would have appreciated a notice with a chance to opt out first.” – anygivnthursday

These three themes—Google’s invasive verification tactics, the underlying ad‑ and regulation‑driven motives, and users’ mixed‑success attempts to preserve privacy—dominate the discussion.


🚀 Project Ideas

Generating project ideas…

VerifyLess: Virtual Phone Number Service for Privacy‑First Account Creation

Summary

  • Provides disposable, country‑specific virtual phone numbers that can receive SMS verification codes, letting users create Google accounts without exposing their real number.
  • Core value: Enables anonymous sign‑ups while satisfying Google’s phone‑verification requirement.

Details

Key Value
Target Audience Privacy‑conscious users, expats, travelers, developers needing test accounts
Core Feature On‑demand SMS‑receivable numbers via web UI/API, auto‑expiry after use
Tech Stack Node.js/Go API, React frontend, Twilio‑compatible VoIP provider (Bandwidth/Vonage), Docker
Difficulty Medium
Monetization Revenue-ready: pay‑per‑number or $5/mo subscription for 10 numbers

Notes

  • HN commenters note: “It's essentially almost impossible to create a Google account without giving up your identity…” – VerifyLess directly removes that barrier.
  • Offers a practical utility for those who need multiple accounts (e.g., testing, separating work/personal) without buying extra physical phones.

VPN‑Friendly Google Access Extension

Summary

  • Browser extension that masks VPN traffic as legitimate Google‑trusted traffic, preventing bot‑detection blocks on YouTube, Gemini, and other Google services while the user remains signed out.
  • Core value: Lets VPN users enjoy Google services without forced sign‑in or CAPTCHA walls.

Details

Key Value
Target Audience VPN users, privacy advocates, remote workers
Core Feature Automatically adjusts headers, cookies, and token signals; integrates a lightweight CAPTCHA‑solving helper to bypass challenges
Tech Stack Manifest V3 Extension (JS/TS), background service worker, optional Rust/Wasm for crypto, optional reCAPTCHA‑solving API
Difficulty High
Monetization Hobby (open‑source, donation‑supported)

Notes

  • Users complain: “Not being able to watch YouTube videos when using VPN - without signing in to a Google account…” – this extension restores that ability.
  • Sparks discussion on the trade‑off between bot mitigation and privacy, a hot topic on HN.

Multi‑Phone Account Manager (MPAM)

Summary

  • Desktop/mobile app that creates isolated containers for each Google profile, each with its own storage, cookies, device fingerprint, and optional VPN profile, preventing cross‑account linking.
  • Core value: Lets users maintain multiple separate Google identities without needing two physical phones.

Details

Key Value
Target Audience Professionals, privacy‑savvy users, anyone juggling work/personal Google accounts
Core Feature Containerized Google sessions (like Firefox Multi‑Account Containers) with per‑profile VPN routing and automatic clearing of phone‑number data
Tech Stack Electron (or Tauri) desktop, React UI, IndexedDB storage, optional WebExtension for browser integration
Difficulty Medium
Monetization Revenue-ready: freemium – free basic (2 profiles), $3/mo for unlimited profiles + VPN integration

Notes

  • HN users say: “I carry two phones now - since I have my 'privacy' enabled phone…” – MPAM eliminates the need for a second device.
  • Provides tangible utility for preventing the “ban‑all‑accounts” effect described by commenters, and invites conversation about identity compartmentalization.

Read Later