Wayland and audio is fixed, but only on the canary branch for the moment, this isnt lazy either, they changed the whole screenshare flow to suit linux's permission prompts
this post was submitted on 26 Nov 2024
1043 points (97.4% liked)
Linux
48626 readers
1489 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not sure if this is actually possible - as far as I know, applications can't track key presses/mouse movement when their associated window isn't in focus. It'd be great if they just gave the option to disable the AFK detection since it doesn't work...
Works fine with a plugin, so clearly it can't be that hard.
Ah, I thought this was in regards to AFK tracking when discord isn't focused (which this plugin still won't fix due to the mentioned Wayland restrictions) - I didn't realize that it still didn't work even when discord was focused, which is strange.
I've been using Vesktop since screen share wasn't working on Wayland, and it already seems to do what this plugin does hence my confusion.
What happens now in afk detection? I never noticed it.
Haven't used it in a while but from what I remember it always puts you in idle if you do something else and only back to online if you do something in Discord itself, as expected from the Wayland limitation.
It could be implemented with the ext-idle-notify-v1 protocol.
In my case it refused to ever mark me as idle, which meant I never got any notifications on mobile...