• rozodru@piefed.social
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    2 days ago

    It’s fine. There’s still some quirks with Wayland I don’t like. Either having to be in a game or have Discord focused in order for push to talk to work for example. Some mouse constraint issues with certain games that for whatever reason KDE has been able to figure out but every other wayland compositor hasn’t.

    • Codilingus@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      19 hours ago

      Just in case it helps:

      My Discord keybinds were having a struggle when I used 3rd party apps like armcord and vesktop. The actual Discord bin program is doing global keybinds correctly for my toggle mute microphone on my keyboard.

      • rozodru@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        14 hours ago

        I use the Discord Nix pkg, not armcord or vesktop. I’ve always had this issue be it on arch, nixos, or fedora. I’m starting to lean towards “user error” as I just must not have something set up right. but yeah I’ve never used armcord, vencord, or vesktop.

    • 7toed@midwest.social
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      Sorry I have never looked into the specifics, but I read some way for flatpaks to listen for specific keybinds even in the background, it’s mostly a permissions thing IIRC.

      Sorry I’m assuming bazzite Fedora as well.

      • rozodru@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        14 hours ago

        tried it on arch, nixos, fedora both native pkgs and flatpaks. no dice. push to talk only works when either in a game or when discord is focused. all via various wayland des/wms be it KDE, Niri, Sway, Hyprland, etc

    • PointyFluff@lemmy.ml
      link
      fedilink
      arrow-up
      3
      arrow-down
      5
      ·
      1 day ago

      it’s absolutely not fine. You as a user, should be able to access the content of any window on your machine.

      • ulterno@programming.dev
        link
        fedilink
        English
        arrow-up
        4
        ·
        19 hours ago

        By that, do you mean that every program running with your user privileges should be able to access the content of every window on your machine?