When rushing to adopt new proprietary technology in an emergency like now, be VERY cautious of future liabilities, post crisis.
The danger of treating acute pain with morphine is a long term, destructive, expensive addiction...
Many tech solutions are entirely analogous - by design. Their proprietors are delighted this crisis provides an opportunity to sneak past sensible procurement processes.
@lightweight Yes. But sometimes you *will* need to use morphine or some other proven painkiller - especially when the alternative is a crowd of people trying to "sell" you various strangely-looking ingredients and insist that you just get out of the comfort zone, overcome your laziness and roll your own painkiller just like everyone should do to ensure their independence... 😐
@z428 yup. The point is that each person has a duty to those affected by their decisions to be informed, and aware of their liabilities and other options. Most people don't bother raising the shroud of ignorance. And, remember: marketing (like a casino) never works in your best interest. See https://davelane.nz/marketing
@lightweight ... really much time to compare and evaluate alternatives. The bad thing: Once the crisis has been managed, there *will* eventually be an evaluation of alternatives, and we will much likely notice that there aren't really many if you look at the full feature set - no matter where you move, it always will most likely be about making yourself free from that very addiction and paying for that with more effort for less quality. That really bugs me, and I see no solution for that. 😟
@lightweight ... that. Unfortunately, everything I played with for the last decade (no matter whether XMPP, Matrix/Riot, MatterMost, RocketChat, NextCloud or the Confluence tool chain) was even remotely there. I'm not happy about that. But at this point I don't really need marketing to be honest, I just need a handful of non-technical users (who are pretty pragmatic about the things they work with) in front of a tool for a couple of hours to get a clear idea. 😟
@z428 As I posted last night... Gov't Canada have just decided (by staff feedback) to ramp up their use of Rocket.Chat *over* MS Teams (which they've already paid for with their ridiculously anti-competitive all-of-gov't Microsoft deal)... So that's a fairly compelling data point to the contrary.
@lightweight That's a good thing to start with. Any experiences or insights into what kind of feature set they use there? Especially when it comes to collaborative document editing / sharing, video conferencing, conference recording or written chat notes? We've learnt that Teams does a fairly poor job as a text-based chat system (because in that aspect it looks and feels confusing even compared to Matrix or Slack) but what people actually use is completely different.
@lightweight Ah, of course, *that* is possible, but something quite different. 😟 Yes, I *know* there are open tools for each of the feature aspects provided by Teams. Teams doesn't really provide *new* features, nor does it really do extremely well at any particular feature. What it *does* well however is something the FLOSS community has been struggling with / failed to achieve for quite a while: Link and integrate a plethora of different tools and functions to provide users with an ...
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!