201–210 of 264 posts
Still waiting for these guys to update their MacOS app, we use it in our company and it's so bad that our own team uses Slack.
If this is turning into a Microsoft bashing thread I'll join in as well. I don't understand how text handling (highlighting, moving around etc.) works/feels different between Teams, Excel, Outlook, Word, the OS. They're all developed by the same company. Why do they integrate so messily?
Nowadays trying to search in the start menu or trying to log in under heavy load you just have to hope it recognizes all keystrokes.
Earlier quoted context omitted.
Oh ye a code snippet I sent in Teams made me wreck our deployment system. Teams put a nobreak space or something in the code that looked like a ordinary space in the diff. I am still abit mad :)
Oh Teams started doing this too now? This was that one thing that made me absolutely hate Skype (other than being utter garbage in general) and that at least worked so far in Teams... Looks like all commercial chat-software is destined to become terrible garbage, one A/B-test at a time.
If I remember correctly, there is some difference between voice call chat rooms and the instant messaging chat rooms. I don't remember which messed up whitespace. Or if I copied between chats etc.
Can't trust the text anyhow.
No surprise at the MS non-response here. Anyone forced to use Teams every day can see that it's being maintained by a skeleton crew (at best) on the dev side. Every single day I miss basic features (like global message linkability) that I came to love in Slack, and suffer 101 little bugs and annoyances that never seem to improve much. MS clearly thinks Teams is "good enough" - enough of the feature checkboxes ticked…
More and more I wish I could work in some company that doesn't use any MS tools. VSCode seems to be the exception here.
Reading through these vulnerabilities, it feels like a handful of these are low priority or non-issues. This might be a controversial opinion, but it’s not clear to me why these issues ought to be prioritized and fixed expediently. For example, it’s not clear to me why an IP address leak is considered problematic. And breaking chat or crashing on reload seems more akin to a bug a la iMessage link bugs like https://ww…
The IP leak one is really interesting to me. Considering the quip regarding the fact that centralized servers are performing the link preview operation because it's not using E2E encryption... But if it was, and the client machine was generating the preview, then wouldn't that force exposure of the client's IP to the remote server?
Earlier quoted context omitted.
"Zoom had and continues to have a significant developer presence in China." So whats worse: a backdoor for China, or a giant hole for anyone interested? I guess the latter gives us esual opportunity...
A link preview vulnerability in Teams vs a backdoor for China. I choose the vulnerability! At work we were briefed in detail by spy from CSIS to avoid Zoom. I trust the Canadian spy before a trust I company with CCP ties. The only thing I can add from that briefing is avoid Zoom, Huawei and product from Facebook, use Telegram if you can and Teams or Google current messaging solution if you can't.
also from CSIS briefing?
Earlier quoted context omitted.
My biggest issues are that a) it starts up in the foreground (none of my other autostart apps do this) so it can happily intercept keypresses you're doing in other apps -- and b) it does not respect standard system titlebar / borders, which puts it as the only app in my KDE environment that works in a non-standard manner. A/V issues, navigation, inability to find an existing conversation / conference (happening now o…
> it does not respect standard system titlebar / borders, which puts it as the only app in my KDE environment that works in a non-standard manner. This also makes it impossible to resize the window. Well, sometimes. There are times when it works, and I have no idea what makes it work. Thankfully, I usually use Qubes OS which doesn't let programs do these user-hostile things.
As a workaround, I'm pretty sure that KDE supports Alt (or meta) + right click for resizing.
Earlier quoted context omitted.
As a cross platform desktop app developer I hate desktop linux. So many reinventions of the wheel that you have to support. Graphics, sound, video capture, GUI is all a mess.
Can you elaborate more? What would you prefer instead, with regards to developing for Linux?
There is jack, pulse, alsa and now pipewire for sound. On the system you can have multiple sound devices some available fully working only through pipewire, others fully working only through pulse.
If you want your app to integrate into your desktop nicely (basic thing like using tray icons) you can have completely different behaviors on different distros because there is so much variability.
Pipewire is now taking over a lot of things regarding audio/video. With fedora already fully on it. Great but the documentation is in a miserable state. Very few examples. Some distros while have pipewire running, using it for audio will just not work.
Earlier quoted context omitted.
Can you elaborate more? What would you prefer instead, with regards to developing for Linux?
There is X and now wayland. If you are doing something beyond basic you can quickly fall into needing two different implementations for GUI things. There is jack, pulse, alsa and now pipewire for sound. On the system you can have multiple sound devices some available fully working only through pipewire, others fully working only through pulse. If you want your app to integrate into your desktop nicely (basic thing li…
I work with several large organisations, all using Teams. In every instance, the previous solution (Slack/Zoom/Discord) was replaced by Teams following higher management making the switch for reasons like "it's included in Office 365" or a new hire influencing the migration to Microsoft solutions. In every instance, the application was/is not well received by the employees - it's slow, buggy, crazy complicated and ge…