this post was submitted on 26 Aug 2024
204 points (99.5% liked)
Open Source
31717 readers
86 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
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
This danger is why I quit using the Purple Teams plugin for Pidgin: it works well enough (considering Teams isn't exactly open to third-party clients, it works amazingly well in fact) it's GPL-3.0, the source is provided and I compiled it.
So I believe it's clean, but that's not good enough for me to hit our corporate Teams channels with it and I don't have the time to audit the code. Not to mention, while my company trusts my good judgment, I'm pretty sure running an unauthorized client is against IT policies.
So I dropped it, sadly. It's a bummer because Pidgin uses a fraction of the resources needed by that pig of an Electron app - the official client - made by Microsoft.
The newest Teams app (and I think newest Outlook amongst others) is using system/Edge provided WebViews rather than Electron, which I guess takes care of the “each app gets its own Chrome instance” part of the Electron bloat. It’s so far running better than old Teams for me. On my old work laptop, the fans spun up the second the old Teams client launched lol