Comment by ErroneousBosh

You need xdg-desktop-portal . Its probably automatic in some environments but with sway I have to set it up manually. Its one of those annoying things I forget about whenever I set up a new machine.

https://wiki.archlinux.org/title/XDG_Desktop_Portal

Works for me, using Fedora with Plasma. Just fire it up in Brave, and install it as a PWA.

The one thing that bothers me is it can't tell if I'm at my machine when I'm not actively using it. People keep thinging I've bugered off from my desk.

Screen sharing from the browser usually works for me, but if ever it doesn't, as a workaround you can use OBS with a virtual webcam to share windows and screens as an overlay to the webcam stream. It's very easy.

Which compositor/environment? Starting the correct xdg portal helped me when I ran Sway.

What kind of URLs does it use? If it's anything with a unique prefix (like Telegram's tg://), you can add it to the desktop file:

  MimeType=x-scheme-handler/foobar;

and run `update-mime-database`.

If not, I would write a shell wrapper and set it as the default browser; something to the effect of:

  #!/usr/bin/bash
  set -eu
  for arg in "$@"; do
    if [[ $arg == *whatever-url-teams-uses.com* ]]; then
      exec gtk-launch teams "$@"
    fi
  done
  exec gtk-launch firefox "$@"

(gtk-launch uses flags from the .desktop file so you don't have to repeat them)

There's something weird going on honestly.

On an i9-14900K, arguably one of the fastest CPUs in the previous few years (and excusing their design defect that causes them to die); Teams is significantly slower than on the Quallcom Snapdragon X-Elite, or my Macbook.

It seems to perform the same as it would on an i9 platform as it does on i5 laptop's of the same generation (in terms of input latency and drawing to the screen etc;)

I know it's apples/oranges, that ARM CPUs are substantially different than x86 ones, but the fact that it seems to be the same on significantly lower clocked (and lower consumptive) chips indicate to me that something very bizarre is happening when it comes to Teams.

ARM chips seem to be significantly better for electron applications, but something unique exists within Teams here.

No potato, quite the contrary, and it’s not that it hogs resources. It’s just slow within. I can also keep a video call open and do other things outside of teams. But doing any multitasking within teams is just a nightmare. Open a second chat while in a video call makes the video into a thumbnail. Searching through other chats to copy and forward into a third chat... Just not possible, because everything is modal and resetting the scroll location when toggling between. On top of that it’s just overall slow slow slow.

It's not that it hogs resources. The app is just slow. So so so so terribly slow.

And half of the time it crashes. Or the video/audio doesn't work.