Project ideas from Hacker News discussions.

Linux Zoom client proactively reading everything written to X11 clipboard

📝 Discussion Summary (Click to expand)

1. Zoom is widely criticized as a privacy/security risk
Many commenters call Zoom “malware” or “trash” because of its clipboard harvesting, unnecessary privileges, and history of vulnerabilities.
- “Zoom isn’t just a technical problem. It's literally malware… They have made it clear they absolutely don't care about security …” – wolvoleo
- “Zoom only has the access to an empty VM and no access to the clipboard.” – fsflover (describing Qubes OS)
- “I only launch the Linux Zoom client when I absolutely know I'm going to need to host a meeting… I feel equally disgusted about Zoom and the corporate EDR agent.” – saltcured

2. Avoiding Zoom is often impractical, especially for job interviews or corporate settings
Users acknowledge the ideal of ditching Zoom but note that many employers require it, leading to workarounds like separate accounts, browser‑only use, VMs, or sandboxed instances.
- “Srsly, all those neck beards who over simplify the problem with a flippant 'don't use zoom', as if everyone has the luxury to skip every job interview …” – netllama
- “Use a dedicated, otherwise empty account for job interviews… stop. using. X11.” – GuestFAUniverse
- “Just run these things in your browser… the web‑based versions are fine.” – Arbortheus

3. The X11 vs. Wayland debate surfaces as a side‑issue, with many defending X11’s maturity
Several participants argue that Wayland is not yet stable enough for daily use, while others claim the display server choice is irrelevant if you run Zoom (or any app) in a browser or sandbox.
- “Wayland doesn't work stable in kde on my OS yet so I have no choice but to use X11.” – wolvoleo
- “I don't remember any god ever claiming salvation lies in abandoning the most functional display server on the market… I'll just keep on using X11.” – hagbard_c
- “Just use a browser instead of some silly client, problem mostly solved. Use X11 or Wayland or whatever else you want…” – hagbard_c (reiterating that the display server isn’t the core problem)


🚀 Project Ideas

Generating project ideas…

ZoomBox – Sandboxed Zoom Launcher

Summary

  • Runs the Zoom desktop client inside a tight sandbox (Firejail/bubblewrap) that blocks access to personal files, clipboard, and privileged system calls.
  • Core value proposition: join Zoom meetings securely on Linux without installing Zoom natively or exposing your data.

Details

Key Value
Target Audience Privacy‑conscious Linux professionals who must attend Zoom meetings (e.g., job interviews, remote work).
Core Feature A launcher script/.desktop file that wraps Zoom in a pre‑configured Firejail profile restricting filesystem access to a temporary directory, disabling clipboard sharing, and limiting network to only Zoom domains.
Tech Stack Bash, Firejail (or bubblewrap), optional .desktop file, Docker for disposable mode (optional).
Difficulty Medium
Monetization Hobby

Notes

  • Commenters emphasized the danger of Zoom’s clipboard and root access: “I would rather have a nice popup on first attempt 'this application is monitoring your clipboard, allow?'” (nomel) and “I could probably use it over the web but that's it.” (wolvoleo).
  • Provides a practical middle ground for users who cannot avoid Zoom but want to limit its attack surface, sparking discussion on sandboxing best practices.

ClipPerm – Wayland Clipboard Permission Guardian

Summary

  • A Wayland‑level daemon that intercepts clipboard read requests and shows a user prompt before allowing any application to access clipboard contents.
  • Core value proposition: gives Linux users granular control over clipboard spying by apps like Zoom, mirroring mobile permission models.

Details

Key Value
Target Audience Wayland users concerned about silent clipboard harvesting (security‑focused developers, journalists, remote workers).
Core Feature Monitors wl‑clipboard requests, displays a GTK/Qt allow/deny prompt, logs granted/denied accesses, and optionally remembers decisions per‑app.
Tech Stack Rust (or C) using wayland‑protocols, libnotify, GTK4 or Qt6 for UI, systemd user service for activation.
Difficulty High
Monetization Hobby

Notes

  • Directly addresses the wish expressed by nomel: “I would rather have a nice popup on first attempt 'this application is monitoring your clipboard, allow?’, ideally with that process completely suspended while that prompt is up.”
  • Enables a usable permission model on Linux, likely to generate lively HN debate about desktop security vs. convenience.

JitsiEasy – One‑Click Private Jitsi Meet Rooms

Summary

  • Deploys a temporary, password‑protected Jitsi Meet instance with a single click, providing a browser‑only video conference link that requires no client installation.
  • Core value proposition: offers a Zoom‑alternative that works in any browser, ideal for interviews and quick meetings where installing Zoom is undesirable or blocked.

Details

Key Value
Target Audience Job seekers, recruiters, and remote workers who need a fast, no‑install meeting link (especially when corporate policies block Zoom).
Core Feature Web UI button that spins up a short‑lived Jitsi Meet container (via Docker API on a cheap VPS or managed service), returns a secure room URL, and auto‑cleans after use.
Tech Stack Node.js/Express frontend, Docker SDK for backend, Nginx reverse proxy, official Jitsi Meet Docker image, optional Let’s Encrypt for TLS.
Difficulty Medium
Monetization Revenue‑ready: Subscription $5/mo for unlimited rooms (or pay‑as‑you‑go per hour).

Notes

  • Many commenters advocated browser‑based solutions: “Just run these things in your browser… the web‑based versions are fine.” (Arbortheus) and “Just use Firefox, or Chromium if you must.” (jrm4).
  • Provides a concrete tool that sidesteps Zoom’s install‑and‑privacy concerns, likely to be well received on HN as a practical alternative for interview‑centric use cases.

Read Later