teams-for-linux VS teams-api

I've never used this but apparently this wrapper is useful for linux people: https://github.com/IsmaelMartinez/teams-for-linux

Have you tried an unofficial electron client?

I use https://github.com/IsmaelMartinez/teams-for-linux . It's "just" a wrapper around the PWA but a very decent one at that.

Unofficial and not Microsoft supported, but might be an alternative to Microsoft's official PWA. How do the two compare in your experience with them?

You can try the unofficial client Teams for Linux. It's available as a Flatpak and I didn't have any issues sharing my screen with it. https://github.com/IsmaelMartinez/teams-for-linux

This client works well for me: https://github.com/IsmaelMartinez/teams-for-linux

There is also: https://github.com/IsmaelMartinez/teams-for-linux

That always frustrated me, even more-so considering how that volunteer-built package I mentioned (https://github.com/IsmaelMartinez/teams-for-linux - an Electron build of the web app, nothing flashy but does the job just fine) does support screen sharing. I haven’t checked whether it supports backgrounds as I only use voice when on calls, but I’m guessing it does if the browser variant does.

https://github.com/fossteams/teams-cli uses https://github.com/fossteams/teams-api

That's why we're building FossTeams [1] (:

The idea is to have a backend [2], powered by a library [3] that does the heavy lifting and a / multiple frontends to be used with that (e.g: CLI[4], Web frontend[5], Flutter app[6]).

We're looking for contributors! If you hate Teams and want to improve an Open Source version, PRs are welcome (:

[1]: https://github.com/fossteams

[2]: https://github.com/fossteams/fossteams-backend

[3]: https://github.com/fossteams/teams-api

[4]: https://github.com/fossteams/teams-cli

[5]: https://github.com/fossteams/fossteams-frontend

[6]: https://github.com/fossteams/fossteams_gui

These tokens are collected by replicating the Oauth flow with an Electron app that basically intercepts the redirection and gets the tokens. These tokens are then saved in a directory and are picked up by teams-cli (actually teams-api) when you use it.

This is indeed frustrating, but there might be a technical explanation behind it: AFAIK message ids on Microsoft Teams are generated by the clients, and one cannot easily jump to a message ID.

Their Teams mobile app does something more stupid, but that kinda works: when you reply to a message, the message is copy-pasted as a quote and you are basically sending back the original message to the user.

I really don't get why Microsoft Teams is _that_ overengineered and (IMHO) badly develooed. Their clients are super heavy on CPU and memory and I can barely use the web version.

On a side note, I'm trying to fix part of this mess myself by writing a Microsoft Teams library (and later a / multiple clients) so that I can finally use without complaining about it: https://github.com/fossteams/teams-api