us.zoom.Zoom

Discover this repository through its Hacker News conversations.

Explore on GitHub Read Hacker News discussions

6Distinct people

6Mentions

0Explicit recommenders

50GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2020-04-17 16:43:59 UTC to 2025-06-06 12:19:47 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	4	4
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	0	0
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	1

What Hacker News says

6 sources

hello_computer·Jun 6, 2025

2016-01-23 https://github.com/MaartenBaert/ssr/issues/431 2019-01-04 (only took 3 1/2 years to resolve!) https://github.com/flathub/us.zoom.Zoom/issues/22 2020-03-07 https://github.com/vkohaupt/vokoscreenNG/issues/51 2020-03-07 https://github.com/obsproject/obs-studio/issues/2471 2020-03-24 https://github.com/jitsi/jitsi-meet/issues/6389 2023-09 https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/ 2023-11-17 https://github.com/raspberrypi/bookworm-feedback/issues/149

In The X.Org Server just got forked (announcing XLibre)

noahtallen·Dec 15, 2021

There is a lot of conversation about Zoom here: https://github.com/flathub/us.zoom.Zoom/issues/22 Apparently, there has been some recent activity via support channels. But I’d bet it’s probably not that difficult, just a matter of the team’s priorities to get to it. Then again, zoom isn’t very active or transparent in the OSS world, so it’s hard to say.

In Gaming on Wayland

smlx·Dec 15, 2021

More accurately, the developers need to a) fix the buggy implementation of the Gnome-specific protocol they currently use, and b) switch to the standard screensharing protocol. https://github.com/flathub/us.zoom.Zoom/pull/182#issuecommen...

In Gaming on Wayland

smallerfish·Nov 23, 2021

I agree that the implementation is lacking. Snap has the abysmally named "--classic" parameter to allow installs to "run without confinement". Flatpak can request permission changes at install time (albeit declaring them), where users are likely to just click OK/OK/OK. The sandboxing needs to be tightened up. Flathub is a strange beast. There's no mention of security on their wiki. They stopped publishing minutes (or moved them elsewhere?) in 2017 (https://github.com/flathub/flathub/wiki). They have a buildbot for automated updates from developers, but they accept binaries anyway (e.g. https://github.com/flathub/us.zoom.Zoom/blob/master/us.zoom....), so what's the point? It appears to be a fairly amateur effort, and yet is at the center of the infrastructure Red Hat and Gnome are pushing. I'd love to see some white hat activity targeted a

Read the rest

t compromising it, to demonstrate the shaky foundations. But on the other hand, it's nice that I can run Zoom sandboxed (apparently - it's not obvious what the granted permissions are: https://www.flathub.org/apps/details/us.zoom.Zoom). It's nice that Jetbrains and Zoom have a way to publish apps that can run on all distros. It's nice that I could rollback a version of IntelliJ that was buggy with a single snap command that took 5 seconds. The goals are good. I wish Linus took more of a BDFL approach to the desktop occasionally. Ubuntu & Red Hat need to sit down in a room and have a constructive conversation to converge Snap and Flatpak into something new, deprecating the infrastructure built to date, and fixing some of the glaring problems. There's room for both to make money without further diverging the ecosystem.

In Flatpak Is Not the Future

dylan-m·Oct 3, 2021

The weird screenshot thing also leads to confusing issues like this one: https://github.com/flathub/us.zoom.Zoom/issues/223. Zoom tries to avoid sharing its own windows by using an X window property that specifies the owning PID, so it filters out any window where `_NET_WM_PID == Zoom's PID`. In a modern Linux desktop where applications are sandboxed, many different applications can think they have the same PID, so it ends up filtering out other applications. Not sharing its own windows is nice and all, but I don't think Zoom even does that on other platforms. It's weird how much effort they have put in to doing the wrong thing.

In PipeWire and fixing the Linux Video Capture stack

ryukafalz·Apr 17, 2020

Some, I guess, but not enough to make much difference. The Flatpak for it mounts the user's home directory: https://github.com/flathub/us.zoom.Zoom/blob/master/us.zoom.... ...and the Snap seems to as well, though I'm less familiar with Snaps and it seems like this may not provide access to hidden files: https://github.com/ogra1/zoom-snap/blob/master/snap/snapcraf... So your SSH keys may be safe there, your photos and documents probably aren't.

In Zoom Endpoint-Security Considerations