16 ms·
Microsoft Teams: 1 feature, 4 vulnerabilities
- xvector 5y agoWhat is the solution? More security education for general SWEs? It seems like whatever team worked on this feature never considered any security perspectives.
- iso1631 5y agoMake all software which isn't released as open source liable for the cost of security breaches?
- baq 5y agogreat way to not have any software released ever
- emerongi 5y agoSomehow we still have medicine (they do a lot of testing before they release anything!) and doctors (they have insurance!). It would increase the barrier to releasing software massively (possibly killing the startup scene altogether), but it doesn't mean software development would end.
- ssdspoimdsjvv 5y agoIf we applied the same rigorous testing and verification processes in medicine to software, software development as we know it would definitely end. It would probably take years to convert a straight-forward requirement into a working piece of software. Something like Teams or VS Code that get new features added all the time would not be possible anymore and would cost tons of money. And while security issues should not be taken lightly, I don't consider leaking my user agent to be as big of a problem as getting permanent damage from low-quality medical care.
- LaGrange 5y ago> If we applied the same rigorous testing and verification processes in medicine to software, software development as we know it would definitely end. Good.
- simion314 5y ago>Something like Teams or VS Code that get new features added all the time would not be possible anymore and would cost tons of money. And while security issues should not be taken lightly, I don't consider leaking my user agent to be as big of a problem as getting permanent damage from low-quality medical care. It won't take years. We will have to train developers and create better tools. Then you will libraries and apps sandboxed, like we would not allow an IDE full access to the internet, or to the entire hard drive without permissions. Say you get the task to build an RSS reader, you will have to choose: 1 use a language+standard library that is safe and the vendor offers some warranty 2 use an unsafe language or some unsafe libraries but you will have to take the risks and do the work to review and evaluate 3 in case you prefer open source you find a language and ecosystem where there is some foundation that even if it can't offer some warranty it accepts donations and contributions that are directly targeted on security, so you would have packages that would have a checkmark that was reviewed by a team. So I would use a safe language(a GC one) with a trusted standard library, so now I can do the network requests to grab the XML files , parse them with the secure XML library and render the content in the safe Web View provided. This means that the guys that give or sell me the XML library and the Web View will take the risk, but they can charge for their work. We would probably get smart developers using some extremely safe languages like math safe not Rust(safer then C safe) and this guys can write a maybe slower but 100% web view (maybe with less shiny animations). Capitalism would be forced to invest in this safer tools and in training the developers, Microsoft ,Apple, Google will have to secure their unsafe OS and libraries but for sure it would not take 1 guy years to build an RSS reader that would not take over your data and send it to some hacker somewhere.
- citrin_ru 5y ago> Somehow we still have medicine (they do a lot of testing before they release anything!) and doctors (they have insurance!). The fact that doctors are relatively frequently sued in the US is one of the reasons why US has very expensive healthcare. If you are rich that's fine, but almost everybody else would prefer more available (cheaper) healthcare with doctors who don't need to spend money on liability insurance.
- thrower123 5y agoSofteare companies generally take out large (and increasingly expensive) liability insurance policies for exactly this reason.
- nopeYouAreWrong 5y agoI'm in favor of this.
- chickenchaser 5y ago...?
- southerntofu 5y agoParent suggested free software would be the exception to this rule. Personally, i don't understand why it's even legal to publish binary code without the corresponding source, but at least their point made sense: volunteer-run projects need to be exempted from such regulation, and there's exactly zero reason a volunteer-run project should not be free-software.
- vegai_ 5y agoNot sure why you were downmodded, this would be a great idea.
- billpg 5y ago"We want to make use of the open-source exception, but we don't want to actually release our source code." "I'll have some Beware-of-the-Leopard signs printed up."
- IiydAbITMvJkqKf 5y agoWhy should open source software be exempt? If your data gets leaked/abused the license of the software used does not matter in the slightest. If anything, freeware (whether open source or proprietary) should be exempt from costs. You get what you pay for, after all.
- vegai_ 5y agoMake everyone culpable but make the maximum amount of damages never be higher than what income the software generated.
- josefx 5y agoopen source did not stop Heartbleed. How about force commercial software companies to have 1 in 10 devs. dedicated to security with even a single feature ticket getting fixed by one of them resulting in a fine of ~5% of the yearly revenue.
- brnt 5y agoThere is a reason that in construction, the architect and the structural engineer are separate roles. From what I've seen in software dev, it cannot be considered engineering until a similar division is normalized, mandated and legally required. It's easy to shove things into production, too easy.
- mschuster91 5y agoSoftware engineering does have the profession of "software architects" in theory, the problem is that the only thing they get taught in academia is building useless object models for Java. (Side rant, the fact that academic computer science is so far away from real life is yet another can of worms)
- mschuster91 5y ago> It seems like whatever team worked on this feature never considered any security perspectives. The solution is simple: similar in thought to GDPR, make vendors of proprietary products above a certain size (e.g. market share, net worth, # of employees) liable for security issues even if they do not result in privacy breaches. Vendors will then either have to release their software as open source or need to carry insurance for security issues, and the insurance companies will only provide insurance if company processes are following industry standards - e.g. code reviews, security audits during concept and development, appropriate staffing of developer teams or requiring certifications/training for developers.
- pid-1 5y agoI work as a sysadmin and everyday is an uphill battle to convince people to not do dumb shit like exposing endpoints to the public internet (without need). I have no security education, but I care about stuff because I will be held responsible if we get pwned at some point. IMO the biggest issue is that SWEs very rarely have long term skin in the game in the projects they are committing to. Many have strong incentives to not care about security, day 2 ops, etc... When shit hits the fan bonuses were already paid and said professionals often moved on. I think that tends to be lessened by having small projects with clear owners that don't jump around all the time. Companies with smaller turnover win big here.
- iso1631 5y ago> I work as a sysadmin and everyday is an uphill battle to convince people to not do dumb shit like exposing endpoints to the public internet (without need). I find it helpful to have standard low cost (certainly no monetary cost, but also little in the way of bureaucratical cost) solutions which remove the need. E.G. "I need to access this device's webpage from everywhere" "Fine, go via this proxy which has oidc integration with our corporate identity, Here's the URL, let me know if there's any problems" Doesn't always work, but it certainly reduces the fights.
- citrin_ru 5y agoEducation alone would not help if SWE in many (most?) large companies have no incentives to make software more secure. Even worse - caring about security can make their performance look bad. Companies try to improve security by inflating dedicated security teams which in many cases don't care about an actual product, its code (and infrastructure) but can annoy engineers by arbitrary rules/checklists/policies e. t. c. which IMHO rarely improve product security. How to create this incentive is an open question but more laws and regulation doesn't look like a good answer to me.
- markus_zhang 5y agoRemoving micro updates, slow down and actually let engineers fix bugs. I think ultimately PM takes care of which fix/feature to be worked on?
- cloudengineer94 5y agoStill 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.
- smcleod 5y agoNot to mention it's an Intel only binary, what's the point of using these dreadful electron cross-platform apps if they can't even be built as universal binaries.
- cloudengineer94 5y agoI know right? Plus MS Teams is the among the most used apps in the enterprise world how come the only good version of it is only available in Windows 11 where most workplaces aren't even pushing it to their users. The way Microsoft handles Teams annoys the crap out of me the MacOS and Linux versions are left to die basically.
- smcleod 5y agoIt is (by far) the most horrific piece of software I'm forced to used, the UI/UX is confusing, it's a battery killer, eats all the ram (though - that's common with all electron garbage), it somehow manages to make Bluetooth headsets drop out, it significantly impacts network performance when sharing video, a lot of bugs in the calendaring system.... I could go on, but damn I just hate it.
- cloudengineer94 5y agoWhen I used to have my i9 16" MBP, the thing would go crazy and hit 90% CPU usage during web calls on Teams. I had to force myself to have it in clamshell mode to avoid crazy stuff going on.
- eitland 5y agoOn PC at least sometimes it helps to keep it on the laptop screen instead of an external screen.
- dgellow 5y ago> We reported the issues to Microsoft in March 2021, who has only remediated one so far I feel that I read something like this almost every single time Microsoft is mentioned in a vulnerability disclosure. What makes the company so bad at dealing with security reports? I don't expect it to be a lack of talents or resources, or is it?
- charcircuit 5y agoMicrosoft seemed to have responded to all of them though.
- llarsson 5y agoA response of "WONTFIX" is still a response, sure, but not the one most would want for a security-related issue.
- cloudengineer94 5y agoTheir SOC Team for consumer/prosumer oriented apps is terrible. I knew someone working there that left to join the Azure team within the company so go figure...
- clavicat 5y ago
- thrower123 5y agoNine months to fix a simple issue is cracking on for the Teams division. Their tempo is almost as ponderous as their product.
- AnimalMuppet 5y agoThere may be an element of survivorship bias. You hear about the ones where someone whines that they didn't fix it. When they fix it quickly, all you hear are the grumbles about yet another software update.
- wjnc 5y agoOne in this temperament: try accidently pasting a very large amount of data in the chatbox in Teams. Then spend the next 40 minutes re-starting Teams to try to remove the data from said box while your laptop tries to fly away and Teams keeps many processors and gigs of memory lit trying to parse your data. Microsoft should (but won't) reconsider the idea that one chatbox to rule many underlying types of software is a good idea.
- 2ion 5y agoEven a very large amount of data pasted should not blow up a text box in 2021. I mean, on Windows you can paste an object referring to a data blob pretty sure, macOS surely has something similar and on X/Wayland you could sniff and size of data pasted in advance and do something useful. If it's plain text like JSON even 5G of plain text should not bring a text box to its knees when the memory is available, it's not being rendered at the same time ... still getting irritated by Firefox taking forever to render a 10M email source code in plain text when it could do something smart and render/view only the viewport that's showing. Somewhere GUI engineers stopped being smart.
- chmod775 5y ago> still getting irritated by Firefox taking forever to render a 10M email source code in plain text when it could do something smart and render/view only the viewport that's showing. How do you know what's supposed to be in the viewport, especially if the font isn't monospaced? You have to 'render' the entire thing at least once - at least to the point of measuring the dimensions of text (not a cheap thing) and figuring out where you have to force linebreaks. And whenever the user resizes their window horizontally or does various other things, you have to do it again. Your typical browser is already pretty good at this - not to the point some dedicated text viewers/editors are, but pretty good.
- 2ion 5y agoIt's a monospaced font. Though even if it should have to render everything at least once, it should be in the blink of an eye --- at this point I'm almost convinced that getting a laptop with 10th gen i7 class CPU, 32G RAM and a RTX2060 graphics card to absolve myself of desktop performance issues was a mistake as it forces my to run Windows for flawless Optimus interop and does not get rid of desktop performance issues either. Maybe font rendering is not optimized enough or not accelerated at all, but a few million letters the most of them not even visible should be nothing on this machine drawing 100W and more but not performing much better at this specific task than my Haswell laptop from 2014.
- m_mueller 5y agoI have a hard time understanding why MS is investing so much into VS Code yet so little progress is made on MS Teams (which in theory should be more important to them as it has broader usage?).
- xxs 5y agohow do you know they are not 'investing'. It's my firm belief that even if Microsoft did try as hard as they could and they would assemble a whole teams to try and design/implement a worse product than "Teams"... that would be a spectacular failure.
- akdor1154 5y agoI think it's just the team that makes Teams is cut from a very different cloth than that who makes VS Code. Smells a bit like someone in MS saw VS Code's success and drew the conclusion that it must be because it was built with Electron, and if only all the other bits of MS who churn out crappy gunk would use Electron then they'd churn out flawless gold instead. Well, they churned out Teams, make up your own mind I guess.
- vladvasiliu 5y agoWith VSCode, they had to prove themselves in order to bring people in. No one would have used it if it were as horrible as Teams. With Teams, on the other hand, they've got nothing to "prove", they just need to show up. Enterprises eat it up automatically because they already use Office, so "it's free". I also don't think they have any hope of attracting people from outside the MS ecosystem, so they don't even try. I'm actually quite surprised they've put out a Linux version which isn't any worse than the Windows one.
- Nextgrid 5y agoExactly. Developers aren’t stupid and most have experience with legitimately good tools - you’re not going to win them over with a pile of shit like Teams. The target market for Teams however is one that’s often non-technical and has never used anything better, so for them Teams is an upgrade.
- 5y ago
- derN3rd 5y agoI think the first vulnerability could also lead to a DoS if they point the server to its own lookup route? Also sad to see how Microsoft is treating security researchers, instead of thanking them with a small bug bounty. Especially for the one (or maybe two) DoS vulns
- pydry 5y agoIn 2020 a rash of anti-zoom propaganda that I'm almost certain was driven by Microsoft led to a company-wide prohibition on using anything other than Teams "for security reasons" where i worked. This was, I am almost certain, inspired by Microsoft corporate sales getting their hooks into management. This was largely because of news stories like "end to end encryption doesnt really work as advertised" and "if you leave a room password unprotected bad people will enter". The level of press coverage was off the scale compared to what Teams got for far worse issues. The vulnerabilities werent nothing but they werent even in the same ballpark as the MS teams vulnerabilities foisted on us for "security reasons" like this howler they tried to cover up https://www.techradar.com/news/microsoft-may-have-downplayed-a-disastrous-teams-security-issue https://www.techradar.com/news/microsoft-may-have-downplayed...
- JumpCrisscross 5y ago> a rash of anti-zoom propaganda that I'm almost certain was driven by Microsoft Zoom had and continues to have a significant developer presence in China. Those individuals are subject to CCP coercion. There was also a time when they routed American calls through the mainland [1]. That has been fixed. But it remains excessive to cast all past criticism of Zoom as Microsoft's work. [1] https://techcrunch.com/2020/04/03/zoom-calls-routed-china/ https://techcrunch.com/2020/04/03/zoom-calls-routed-china/
- drcongo 5y agoDon't forget the directory traversal vulnerability too!
- bitexploder 5y agoWhat’s remarkable, to me, is how publicized these issues in Zoom became vs other software. Google also seems to have pointed their vulnerability researchers at it. I remember thinking at the time they were getting a lot more scrutiny than most software in that realm, which has the same types of issues. Maybe it just entered the public Zeitgeist and it’s all a coincidence, but as a long time infosec consultant that does vulnerability research I found it curious at least.
- IiydAbITMvJkqKf 5y agoMS Teams is the worst software I've ever used. This is not hyperbole. A room full of monkeys on a typewriter would never create something as bad as teams.
- danuker 5y ago> A room full of monkeys on a typewriter would never create something as bad as teams. Monkeys could barely create software if at all. That means you have set a low badness bar for Teams to surpass.
- mypastself 5y agohttps://en.m.wikipedia.org/wiki/Infinite_monkey_theorem https://en.m.wikipedia.org/wiki/Infinite_monkey_theorem
- zeeZ 5y agoWhat if they were using GitHub copilot?
- senectus1 5y agoLync was worse.
- tsimionescu 5y agoOh, I remember how Lync had different maximum message lengths for the first message in a conversation vs subsequent ones. I believe it was using SIP internally and sending your first chat message in a "begin call" workflow, but it was always unpredictable when a new "call" would start or not. Horrible kludgey solutions...
- bluGill 5y agoI want lync back. I'm no longer 20, my eyes demand that I zoom everything in and then features disappear
- Philip-J-Fry 5y ago
- dmix 5y agoI just noticed hat GitHub offers a security tab and CVE handling, showing which releases are affected and when it was patched (plus a security policy): https://github.com/wireapp/wire-desktop/security/advisories/GHSA-5gpx-9976-ggpm https://github.com/wireapp/wire-desktop/security/advisories/... Design wise I’d much prefer the vulnerabilities listed upon clicking security, instead of a page that basically has 2 links.
- clavicat 5y ago
- fock 5y agoThe IP adress leak is also very common in a lot of "flashy" opensource projects trying to "solve" communications. Because apparently everyone wants his computer to visit a url to parse some data, so that one can decide whether the link is safe to click or not... A private discourse forum (actually any forum software, sometimes spam bots post gifs for usercounting!) does this to great effect with media too - it just allows embedding everything it seems. And then there is a university rocket-chat instance - with a big general-channel: And link-previews (enabled by default) somehow don't cache the images serverside, but let every client get them, because that's probably what works easiest with k8s, because who has a harddisk.
- kevincox 5y agoIn most cases "leaking your IP" isn't considered a problem. I leak my IP to hundreds of websites a day. Of course there are concerns, especially on mobile where you may be able to do some location tracking. Really the biggest place where IP leaking is a problem is gaming communities where people like to hammer IP addresses yo DoS people.
- fock 5y agoWell, you can basically do user-tracking on people viewing a specific internal chatroom that way. Which is definitely different to more or less consciously getting abused in the public net every minute. Also funny: if people bookmark your website in iOS safari and you don't have a favicon, safari will regularly visit your page :). Found out that my father had bookmarked my empty blog that way, because suddenly an IP from his workplace showed up in the log... Yes, in the face of the other abuse this is minor, but I think it illustrates the total disregard for privacy nicely.
- kro 5y agoI remember a few months ago I got a bug-report from a customer that "their site didn't show in link-previews in MS-Teams". The URL includes a German "Umlaut": ü After tracing the HTTP requests received from the link-preview generation on the server (logging the network packets) I found that the "Host" header wasn't the expected/configured xn--test--ova.de (IDNA to ASCII). To "work around it" I needed to add an extra VHost in Nginx with the server_name "test-\xFC.de" (that just redirected to a non-Umlaut domain). I didn't bother or even know where to report it (to MS). But apparently not using proper tooling for URL handling / HTTP requests makes one wonder about the quality of the product or even possible security implications.
- jonpalmisc 5y agoGoogle Meet isn’t my favorite and browsers obviously aren’t immune to exploits, but things like this make me glad Meet is fully-featured and usable in the browser.
- cebert 5y agoThis preview link vulnerability appears to be an easily implemented mistake. I wonder if having vertical development teams (client, api, etc) vs horizontal teams for a particular product makes this type of defect more likely. I could see how a client team would be likely to consume the preview link API without considering its internal implementation or that it could probe internal cloud infrastructure. The API mistake could have been easily made by any developer, particularly more green developers. Lack of a larger number of people involved with the entire horizontal stack could make this type of issue more likely to not be found. My organization is considering restructuring teams from 1-3 horizontal teams (full stack) for a given product to 1-3 teams that focus only on one slice of the product. Seeing articles like this makes me contemplate if there’s more security risk with this approach.
- deleted 5y ago[deleted]
- clavicat 5y agoMicrosoft watched Silicon Valley and thought, wow, Hooli Chat looks like a great idea!
- blahblah12 5y agoReading 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://www.theverge.com/2018/1/18/16904774/ios-iphone-bug-crash-chaios-link https://www.theverge.com/2018/1/18/16904774/ios-iphone-bug-c.... That type of issue should be fixed, but it’s not a vulnerability that’s meaningfully exploitable for either remote code execution, stealing client credentials, or stealing client data.
- watwut 5y agoI did not seen micropenis nor Gates jokes on HN.
- blahblah12 5y agoComments were deleted.
- jdmichal 5y agoThe 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?
- cjbprime 5y agoYes, these are the tradeoffs between client side and server side link previews. (If the sending client does it, they could lie; if the receiving client does it it's a privacy leak and attack surface increase; if the server does it then it sees private data.)
- isodev 5y agoI 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 generally doesn't feel "right". Microsoft is good at channeling security topics for their PR, but at the end of the day they make software, just like everybody else (and this software is subject to bugs, just like everybody else). It's really disappointing that the vulnerabilities have not yet been addressed...
- watwut 5y agoThat is exactly how it went where I work. Higher management decided for teams and office and it is just bad solution.
- 542458 5y agoAnecdotally (as a counterpoint), we also went with teams, and it’s been… fine. There are bugs, but they’re mostly in the category of “irritating” rather than “massively disruptive”. It’s nice that teams is integrated with the rest of Microsoft’s 365 and outlook stuff, and service uptime has been good enough. From my POV, the differences vs Slack have been pretty minor (although I recognize that my experience isn’t universal). That said, yeah, leaving vulns and/or the irritating bugs open for as long as they have is silly.
- mellavora 5y agolike not being able to delete a chat? I had a chat with an outside org, and now it is forever in my Teams history, and I cannot get rid of it. which has the potential to be pretty embarrassing (if the chat was not work-related) or a violation (if the chat was under i.e. an NDA and the relationship ended thus "you have to delete all notes etc"). I'm sure the creative can think of additional ways this could be awkward.
- artificialLimbs 5y ago
- markus_zhang 5y agoTeams has a bunch of anti-features that I have to click off, including this one. The micro update also tend to break something. For example a November patch broke list in chat, a futher one broke list in general. I have to enter the edit mode every time I want to enter a list. I think the ability to use ''' to enter code snippets was also broken a while ago, and in another patch the indentation of such code block was gone as well. I think they are trying to force us to use the editor mode.
- waschl 5y agoAh and I thought it was my fault that lists stopped working all of a sudden.
- markus_zhang 5y agoNo it wasn't haha. I really wish Teams is not force updated bit I guess it's not a choice.
- jrogan993 5y agoawful product.They have improved the search functionality in the last few months by adding more filtering options so it isn't as bad as it used to be for finding stuff.
- technion 5y agoWait until you have apply a security update for teams in environments where users aren't local admins and get a desktop-wide install. Microsoft wrote a not officially supported Powershell script to hack this in, noting this might be needed "perhaps for a critical security release". https://github.com/microsoft/TeamsMsiOverride https://github.com/microsoft/TeamsMsiOverride
- kgeist 5y agoWe have an integration with Teams and it feels like a beta in my opinion. Random 500's from the API, hundreds of JS errors in the console are not uncommon. We've had fewer problems with Zoom.
- klhugo 5y agoI hope somebody at Microsoft read this. It goes far beyond security vulnerabilities. The Teams Linux client is barely usable. Chromebooks don't even have a client. Could Microsoft expose an API and allow third party clients to be developed?
- thrower123 5y agoYou'd think, but alas, no. At least with the old Lync/Skype clients, you could flip them into UI-suppression mode and drive them with COM, to replace their UI with a custom application, if you wanted to make that investment. Potentially you could cobble together enough Graph API calls to make a lackluster restricted-feature client, but it would be a mess.
- nullymcnull 5y agoNo 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 that they can focus mostly on aggressively marketing it, making it seem crazy to use a separate third-party chat platform instead of Teams if you're using Azure.. even if does happen to be a buggy bloated beast, with almost unusably wretched mobile apps. If there's just one area I wish we hadn't switched to MS-brand dogfood after making the move to Azure, it's chat/calling. It's a deceptively tricky domain to get it right in, and one where you really want as little friction as possible for all users. "We should have stuck with Slack." - every team that ever switched to MS Teams.
- hnthrowaway0315 5y agoI think starting from maybe 5-6 years ago MS got into the mindset of "pushing early and let users be beta testers and do micro patches along the way". Power BI was CLEARLY only barely useable back in 2017 but gradually climbed out of the hole after 2019. 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.
- perryizgr8 5y agoIt is unbelievable the difference in development velocity and quality of the final product if you compare Teams and VS code, both from Microsoft. Both apps are built on electron. Teams is dog slow, VS code is probably the fastest electron app in existence. Teams is full of bugs, and it seems they are unwilling to fix even security vulns (from TFA). VS code is free of bugs, even though I use it way more than Teams. Teams is not fixing even security bugs, and VS code's update cycle is so frequent that it is annoying. I am surprised how long their version notes are. Really strange.
- tuan 5y agoTeams at MS have their own hiring practices, no shared code base, .. I feel like they operate as different companies under the MSFT umbrella.
- raspyberr 5y agoIf 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?
- hnthrowaway0315 5y agoDifferent teams (and skill levels probably). I'm actually thinking MS leaves unimportant work (like Teams because it's bundled) to newbies or new PMs. Good developers are expensive.
- contravariant 5y agoAnd if we're just complaining about Microsoft anyway, who on earth decide it was a good idea to step away from 'every keystroke will be handle eventually, in order'?. 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.
- stevesimmons 5y agoTeams is sometimes comically bad... For instance, 4 people in a video chat, not an uncommon use case. The simples and most logical screen layout would be 1/4 of the screen each. No: one person gets 1/2 the screen, with a tall vertical slice. Two people get 1/4 of the screen, normal aspect ratio. And you get a tiny window in the top corner.
- nullwarp 5y agoTo add to this, why is there a giant bar still at the top when someone screen shares that you can't really get rid of. Even if you toggle it and set "focus", which you need to _every time_, there's still a (smaller) bar. Absolutely worthless piece of software.
- grvdrm 5y agoI feel so validated by this comment. Cannot understand how Teams lays out participant video windows. I keep looking for a magic “arrange by” context option that obviously does not exist.
- hnthrowaway0315 5y agoDoes anyone know why they have to do weekly micro patch? I mean who is the PM and does he/she really believe it's enough to do tests for weekly releases? The last patch on MacOS was released on the 16th and today I see anew patch. BTW the picture issue is still there.
- hocker_news 5y ago> BTW the picture issue is still there. What do you mean by that exactly?
- hnthrowaway0315 5y agoYou see a picture in a chat, you click it, it shows up fine. You click it again, it shows a white screen. Has been going on for a while on MacOS.