The first (and personally the only) requirement I have with any chat system is that it should _not_ modify the text I enter in any way - especially if I am pasting something.
Sometimes I have to paste a line or two of code, or a few lines of a stack trace. Sometimes I have to paste a string which contains some particular set of characters. Microsoft Lync absolutely destroys the pasted text. It subtly converts the double quotes into some unicode nonsense. Then it converts some common character sets into smilies. When you copy text from Lync it is almost always guaranteed to be different from what what entered originally. God, I hate Lync with a passion.
Thank you! I really appreciate the clarity as I haven't seen this "Edit -> Substitutions" menu before. I have shared this learning with my friends.
If I were a developer of Slack, I would be very tempted to disable that OS functionality (similar to how Sublime Text does not seem to utilize this OS feature).
Ugh, please don't. The fact that Chrome ignores the fact that I have certain OS specific keyboard settings is infuriating.
Turn it off at the OS level if you don't want it. Don't make a decision that makes everyone else who uses the OS frustrated because functionality only exists in a subset of applications.
Agreed. I want more apps adhering to local conventions and generally being good citizens of the platform they run on, not less. It's so annoying when an application decides it knows better than my global system settings, especially when there's no way to change the behavior in question.
Also, this is in the Keyboard pane of System Preferences (where you probably want to make some system-wide changes to defaults so you don’t have to fiddle with the Edit menu in every application).
I'm with you with the Lync-hate. I've had problems with getting simple chat to work - in the middle of a chat session that seems to go well, Lync suddenly informs me some message wasn't delivered. And this happens often enough to be annoying. The web-integration (if you ping someone who is logged into Outlook web, the ping shows up in a popup window) is bad - if someone pings you within a gap of a few minutes, the original pop-up isn't re-used. There is a new pop-up, with no history. After using gmail chat, this feels regressive. And yes, there is the copy paste issue you mention. The screen-sharing is not robust - we've had so many sessions crash that we've moved to WebEx.
That the simple chat use-cases don't work well is, frankly, confounding to me.
Few years ago I've used few lines of code that I've copied from Skype. There was a hidden invisible chracter that was breaking everything, I've lost about 2 hours until I found it through a hex editor (I rewrote the pasted code and wasn't expecting for that character to be there). That character was not a part of the original message, but it was added by Skype.
I'm not sure about Lync but we got into the habit of pasting into a text file and attaching that when using Skype to send code / log snippets. Agreed that it is a major inconvenience at times.
I liked the part about Chime calling you at the scheduled start of meeting. So simple yet I had never thought of this since my org uses WebEx.
With a smart phone that would pretty well via a push notification or an actual call, but not sure how that would work when you want a join a meeting from a physical meeting room with its own AV system. I'm sure there is a way to get that set up.
Seemed like it was just a mobile join notification in the video similar to Skype for business or WebEx if you are using VoIP. No?
My company used WebEx and I could make it dial me and start up my conference line without having to go through all the regular pin entry stuff. Now we're using Lync (Skype for business) which is similar although tragically buggy. That can also dial me and sends notifications if you hook it up.
The key for these kind of apps is cost and reliability. Seems like they're advertising substantial cost reductions and better quality. If either one is true they'll likely make out really well.
I must say I've been really disappointed with how often it crashes outright or has major rendering issues during screen sharing. When it works it's really convenient but 20% of meetings with screen share involved seem to have an issue. I really think quality is life or death for these products. If my company weren't a tight Microsoft partner I really doubt we'd be using it.
WebEx wasn't as convenient but at least it worked correctly the vast majority of the time.
Anecdotal, but I use Skype for Business every day without any bugs/issues, as does the rest of my company (~50 people, lots of remote workers + liberal WFH policy).
When there's a rare issue, its usually a headset not working, which is probably more a user or windows problem.
I don't see a lot of audio issues, but tons of problems with screen sharing and video.
My company has about 4000 users in 100+ countries so maybe it's bandwidth/scale in part. i see a lot of stuff like skypefb crashes or doesn't render correctly when you try to screen share, etc especially internationally.
Not 100% certain part of it isn't due to us cheaping out on infrastructure to run it.
Absolutely aggreed with this. We still have to pay a 5 to 10% task to get the conference call going.
Chime is the absolute good step in the right direction, however we will need need a layer on top to solve for all conference call systems.
There are three pieces that needs to be figured out to make this work well:
1. How do you deal with (non?) presence? Are you joining from the AV hardware?
2. How do you deal with PSTN?
3. How do you deal with other VoIP solutions out there.
I wonder how Chime callback will work with back-back meetings.
ie, I'm in someone's Chime/webex, and I need to join a different one. Also does it seamlessly join multiple connections - one benefit of Webex is that I can start my meeting on the iPhone while leaving a meeting room so that others can hop on, and then have my laptop join later so I can share my screen when I hit my desk.
It can/should tell everyone at the start and tell you specifically when it's time to say bye. Depending on the time of the next meeting you could opt to join that one late... obviously triple booked will never work.
This is one of my favorite features. Using computer audio is awful especially on the go and GotoMeeting fails to recognize correctly the code I enter some 20% of the time it seems.
If there is anybody who happens to read this who is responsible for implementing the code that reads the meeting codes, please implement the following changes:
1. Make it so meeting codes are strictly forbidden from having repeating digits, by construction.
2. Make it so that when entering meeting codes, if you think you see repeated digits, consider it just one instance of that digit.
The cell system does not use literal DMTF tones to dial calls; those are played by the phone itself for the user's benefit. If the cell system used DMTF for numeric signalling, we'd all be dialing a lot more wrong numbers. (And we'd all groan when we got a new line with a number with repeated digits in it....) Heck, even on VOIP systems very well connected to the internet, I've had trouble entering 9-12 digit codes without the remote system becoming convinced I'd actually entered a 11-15 digit code. I've gotten a few strange looks before for the way I push the buttons for the codes as rapidly as possible, because, ironically, the human intuition here is exactly backwards; you intuitively think that if the remote system isn't understanding your numbers you should press the number "longer" and harder, but that actually increases the chances of the system hearing multiple instances of that number. You actually want to pound the number buttons as quickly as possible. You still can't deal with the entire number being dropped, but it's still your best chance sometimes.
....
'course, there's probably some patent out that this is in violation of. In which case you are authorized and even encouraged to use this post as part of a defense that this technique is Obvious to One Skilled in the Art. I'm not a telecom engineer.
> not sure how that would work when you want a join a meeting from a physical meeting room with its own AV system. I'm sure there is a way to get that set up.
As someone who works in video conferencing, this is often very broken. The are all kinds of compatibility issues and crappy UX. One of our core selling points is getting room systems into online meetings.
Enterprise conferencing software is so bad and so expensive I'm astonished it took this long for a decent competitor to come in. I'm really surprised Google didn't go all in with making Hangouts a decent competitor. I have a feeling this will make a lot of money.
Most place I've worked, we'd waste anywhere from 5-10 minutes at the beginning of every meeting just trying to get A/V systems and voice conferencing to work.
"Anyone there? Hello? Crap, someone needs to dial in as the host. OK Is everyone dialed in? Good. Oh, wait, Roger can't hear us. Roger, dial back in. OK. Hey, whoever is at the cocktail party, can you go on mute?? Thank you. All right. Who's projecting? The projector is VGA, does anyone have a laptop with VGA? How about a dongle? Great, we can see it now. Can everyone who's remote see the screen sharing? No? OK let's restart the screen sharing program. How about now? Shit, we lost Roger again! Why is the screen 640x480? Damnit, can we just use a different laptop? E-mail the presentation to Diane, we can use her laptop. Did Roger dial back in yet??"
I worked for over a year writing software for video conferencing systems. It turns out the market has a lot of very strong solutions, but no one is willing to pay for them. The cost of building great video conferencing solutions begins to sky rocket as you reach the higher echelons of quality. The first 75% of good video conferencing is super cheap and easy to make and as you approach the 100% mark things go up exponentially. We found that most people want quality in the 95th percentile but want to pay for the 70th percentile... There will need to be some serious cost reductions, integrations, and improvements on the hardware and video encoding side before enterprise video conferencing meets the quality and price expectations that customers want.
Also important, most video conferencing solutions suffer from the same problems because they all use the same hardware just with a different software layer written on top of it. There are very few providers of video encoding and processing hardware.
If you are only looking for UX vidyo has a decent product, Microsoft's latest enterprise offering is good, HPs halo now owned by polycom is good, polycom has some cutting edge stuff that is good but very expensive.
If the UX is so bad that people can't make it work and have to resort to putting someone's laptop at one end of the conference table instead of using the conference room AV, then it doesn't matter how good the other three quarters of your system is.
I simply don't believe this. The cost to develop a system that isn't a horribly complex, unintuitive UX disaster is that much more expensive? We aren't talking about amazing AV quality with lag, we're talking about a system that doesn't take 15 minutes out of a meeting to get working.
There are a lot of reasons for horrible complexity.... 1. There are many ways to roll out a video conferencing system because the hardware is all commodity. Many companies will have their IT department buy all the hardware and try to deploy it using the built in methodologies for connecting conference rooms. This is usually when everyone is given a 16 digit pin number to dial into a room, this causes the dial in nightmares. There are also 3rd parties that will basically sell the same solution as the "custom IT solution" as a service. 2. If you want a decent UI experience you move from snapping commodity hardware together to building a software engineering team, software release pipeline, software updates, and all the stuff that comes along with it. This is usually done by a third party but it still costs more than the commodity solution which it is priced against 3. Once you get a software engineering team involved they have to support the different types of hardware out in production. Most companies have generations of conferencing hardware installed with different configurations throughout the company and do not want to pay for all new hardware. Now your software has to be able to implement screen sharing with 5 different codecs and all those codecs have different bugs and different communication protocols. 4. HP tried to solve this by building their own codecs and forcing all rooms to deploy with the same configurations, but this ended up being the most expensive video conferencing system in the world. It also had the best quality and best reliability.
So yes the cost to building a good ui and less complex system can be way more expensive.
What you need there then (if you are a Windows shop - unlikely), is Lync or Skype for Business.
Despite it being Microsoft, I've found it to be the most reliable and seamless system for multi-party Audio, Video, and Screen-sharing based meetings - and I've used at some time or another in my career almost all the other big hitters in the corporate virtual-conferencing space.
Combine Lync/SfB with one of those nice multi-camera units[1] that sit in the middle of the meeting table and provide audio tracking of the speaker (the active camera switches to the person speaking) along with always-on 360 degree video as well - and it's the closest you can get to being there.
Our company has used 3 generations of polycom devices and they have all been terrible/unusable. Those units are just an IT nightmare because of how they are set up. The newer ones require two ethernet ports if you want them wired (because reasons?), and then also act as a weird computer joining the meeting. If you are in a room with a device, the room has to be invited and join the meeting, then you have to make sure that polycom device is set up with sound but that everything else in the room is muted or else the electronic Harpies will be unleashed. Then if you want screen sharing and video, since the video is regulated by the polycom but screen is shared on a laptop, you can potentially get the video in video in video recursive fun time which will result in fun buffering.
We have "quick" instructions on how to use these devices and they take up a whole page. Most of the devices are abandoned or just left there gathering dust while we use a simple Jabra speaker puck.
PS - Most of these experiences are with SfB. These devices are somehow worse with Webex.
> What you need there then (if you are a Windows shop - unlikely), is Lync or Skype for Business.
I've used that, and experienced comparable delays of at least 5 minutes of futzing on average to get everything working, with occasional bursts to 10 minutes.
Anecdotal, but our company uses SfB and it has been anything but good. We always have problems in voice calls (which forms the majority of use) - doesn't matter if we're all sitting on the same LAN with wired connections or on very good Internet connections away from the office. The number of disconnects, breaking audio, unable to hear someone, and of course, SfB deciding to crash sometimes after some updates - it's been terrible for people using it. The company has "saved" money by moving to it from using phone lines. Who cares about individual productivity anyway?
Having been on the other side of a Skype for Business installation I can tell you that it is extremely variable and can scale anywhere from a self-contained single server set-up[1] to a multi-region, multi-fail-over-cluster, highly available, extremely complicated set-up[2]. We had a few issues post initial install but spent the time to track them down to the point where our system was reliable and more usable than web ex and it's ilk. This is the crux of Lync, so much depends on your required set up and how well that was done.
Well, we're on MS Office 365 and all that it provides, including Skype. I have no idea how things could be so bad even with that (it used to be bad before with an on-premise installation too).
Most of my customers are located in a different city than the one I live and work in. You'd think videoconferencing would be perfect for someone like me.
But no, once or twice a month I rent a car and drive ~225km to meet with them personally. I supplement these in-person meetings with phone calls.
I'm not sure I've ever had a videoconference call go perfectly smoothly, and I found that these kinds of calls added all sorts of invisible friction to the customer relationship. My goal as a service provider is to take problems away from my customer, not to add new ones or make them feel technically inept.
My travel days are long and tiring, but most of my customers actually forget that I'm not local, which is exactly how I like it.
This product looks interesting, and purports to solve some of the issues, but color me skeptical.
Do you think a video wall would help? I often wonder if it is the size of the screen that makes people feel 'distant' when using video conferencing.
Super high def full wall screen, so they can see every hair on your head with minimal lag -- I think this would work, the only thing they'd miss was a handshake.
Why do members of an online conference need to be seen at all? What is the benefit of adding video instead of just using audio -- y'know, the medium by which actually information is exchanged?
Human beings happen to be tuned for face to face communication. They exchange a relatively low bandwidth but high importance information through facial gestures, eyebrows, eye contact, etcetera. As long as businesses relationships are still happening between such human beings, there will be a value placed on seeing each other's faces.
Yeah, I get that. I'm sure there are benefits for a purely business-oriented meeting where people are guarding their cards and trying to make deals.
But I've had to be on conferences with purely technical topics where people use cameras. There's barely even a reason for the call to begin with when specs and questions can just be sent via e-mail, so why do we need to see each other?
I completely agree. Out of all the places I've worked at and all of the developers I've talked to, not being able to work AV with TVs for presenting or conference calls is the common, almost 100% of the time an issue.
One place I worked at spent about $25,000 to get an AV system setup complete with conference calling that was supposed to make it "easy". Every single meeting without fail we'd waste 10 minutes trying to figure it out then have to bring someone from IT support who would then spend 10 minutes themselves fiddling with it.
Perhaps if expectations were set before rolling out a new system, that IT Support would attend every meeting ten minutes early to get things working, conference system decision-makers would have priorities better aligned with the rest of the organization. Of course you could plan for a "Phase 2" in which mandatory attendance would cease, but that would be based on performance rather than timing.
That's the point: they shouldn't be. A situation like that would be seen as an intolerable waste in the C-suite (with the exception of their IT support guy). However, if the status quo were for the support to be there every time, that sets up a different conversation in the executive meeting:
CEO: "Why does everything take so long to get done?"
Everyone: "We can only have 15 meetings starting at the same time, and any additional meetings must be delayed 20 minutes, because there are only 15 IT support techs."
CEO: "What?!? Is this something to do with that teleconference project? That was like a year ago!"
CIO: "That's why I've suggested to the stakeholders, most of whom are here in this meeting, that they sign off on moving to Phase 2. That way we'll have more capacity to fix the ongoing issues with desktops and printers..."
Everyone: "Absolutely not! Your techs get there ten minutes ahead of time, and usually they're still struggling to get everything working five minutes after we should have started! The system you bought is crap!"
CIO: "We've always had a great relationship with that vendor, but unfortunately their product has had a few issues..."
CEO: "I know what 'great relationship' means... I don't care if the salesmen for competing products don't have comparable expense accounts, just get something in here that works!"
Its been several months, but I recall it is really tied to Skype for Business (Lync), and having a windows domain. The office that had one of these didn't use skype for business nor had an Windows domain. It can be switched into a dumb display mode though, but performance in that mode is iffy.
Hangouts is so strange to me (like many Google products I guess). They got a ton of traction; first release immediately was super solid and then nothing. Nothing has changed in ages. No obvious features get implemented. I would love so much to have s tile view of all participants. Ideally we would get a codec that's actually supported by hardware instead of this battery draining mess. I'd love to have an option for the video not to be cropped. I can't count the confusion that has caused over the years with people in meeting wondering why someone is only showing their forehead out why everybody but them can see multiple people on camera but they only see someone in the center. All the hard work seems to be done, but Google refuses to polish and properly maintain it. It's bizarre.
Google desperately needs an "Executive Vice President of People Actually Using Shit". Someone who's entire job is to go to demos of products that are about to ship and cancel them until they at least work well enough to pass the laugh test.
Nearly everything Google makes is just some version or another of Google Home telling your Android phone not to handle that voice prompt to add a calendar entry (which your phone can do) because Google Home is there, so that Google Home can tell you that Google Home can't add calendar entries yet.
Hey, here's Allo. We think you're going to love it. I mean, it doesn't have SMS support, so no one is actually going to use it, but other than being pointless, ain't it great?
My EVP there would have walked in, saw the first slide about a new messenger, and said, "Let me stop you here. Does it transparently bridge IP chat and SMS into one conversation like iMessage? No? OK, I'm going to lunch. I'm sure your stickers are cool and all, but pass."
Why all the hate for Hangouts? I have used it for five years to build and run my company. There is never an issue with Hangouts unless someone in the meeting has a hardware problem (meanwhile everyone else can handle the meeting). It's fast and easy for anyone to use screenshots or video. If you use YouTube Live Events, you can even have a company meeting with every person joining. We have done these once a week for years for fifteen minutes prior to lunch.
Hangouts was (is?) pretty good. But it hasn't been immune to Google's inability to figure out how to make a thing people want.
Initially it was IP only. Then it added SMS support. Then it added merged conversations between SMS and IP. Then it unmerged those conversations. All the while only really working well on the desktop inside a weird Chrome extension that burned through battery like kindling because there was no hardware support for encoding and decoding the video.
I still use it on my phone, but again, the only actual feature anyone really wants from a text/chat/IM program is the one that enables "I just want to send a message to Alice. You figure out how to get it to her appropriately" -- a.k.a. iMessage. If you put stickers and crap in there, sure, people will use them I guess, but the one absolute core feature anyone should expect for at least five years now is still the one Google can't figure out how to do.
And they were actually close with Hangouts at one point. Close enough, in my opinion. It lacked the automatic routing of iMessage, but just showing any message I've received from my wife in one conversation and giving me the ability to toggle how I send a reply right there in the conversation view was fine.
At one time this was a function of how Google did promotions/pay raises. I'm not sure if Hangouts got caught in that catch 22 or not but it did kill a lot of decent projects.
Had that team remained relevant they could have conceivably done a "Chromebox" Hub like the Surface Hub and given Microsoft some competition in that space.
EDIT: Ok so as is pointed out there is a chromebox for meetings. Pretty nice. Seems to be out of the Enterprise group though, is that still part of Google or is it an 'Other Bet' now?
We had it at my old company and it was garbage. Super frustrating to join meetings (type your automatically generated, super long meeting name on a tiny keyboard), random crashes freezes and relatively poor video quality. Another super annoying thing was screensharing had an extremely low bitrate. It was so bad that it was pretty pretty useless to demo any nice UI features or animations. The framerate was 2-5 fps.
Completely opposite experience. Where Skype and Gotomeeting would lag, Hangouts was 99% smooth. Perhaps you've got terrible firewall?
The only problem I used to have is audio would die whenever I mess with browser plugins (disabling that WebRTC feature that leaks your internal IP for privacy, and some other Googlyeish feature).
We use Hangouts pretty extensively (2300 employees) but for anything involving more than 4 people we've switched to Zoom; all of the OP's problems creep up quickly and intermittently in Hangouts.
Also we keep WebEx around for screen control, it seems still best bang/buck for that.
we use it at work. it hooks into meeting rooms' calendars and you just have to use the chromebox remote to select the right hangout in the agenda. no typing involved (unless you were doing an ad-hoc meeting, then you'd just type one of our names as the hangout name). It works quite well.
Yeah we have the same experience, I'm surprised hangouts works so badly for others. As long as you invite the chromeboxes to the same meetings as everyone else, it's super simple to operate and for everyone to join.
Most everything you're describing is a part of the new beta hangouts.
If you're a part of a large Google Cloud account, have your IT person contact your gCloud account manager and get on the beta. Actually, if you're a part of a large account and your IT team is risk tolerant.
You're right in that 99% of them are complete garbage. However I was pleasantly surprised when my company switched to Zoom[1]. A company I had never heard of before. In terms of call quality I've never experienced anything better. Beyond that their mobile experience is almost better in terms of raw features than their desktop app (which is still very good in its own right).
I'm based in the EU (until Brexit anyway) and often do calls with mainland Europe. Never had that problem. Seen a high CPU warning a couple of times but it goes away. Overall I'm a fan. I have friends who use it for virtual conferences even.
I use the free version out of the box to onboard new people (mostly independent coaches/consultants from around the world) as partners - see https://www.agendashift.com/partners to get a feel of geographic coverage
I guess like every option mentioned here they all suck for someone. We have used Uberconference and the audio quality is terrible. And it's not uniformly terrible either which is even more frustrating. Some of the attendees won't be able to understand some people and other attendees everything sounds fine (although it always sounds like a poor quality cellphone conversation).
With Google Hangouts we have poor quality audio as well and at least once per day we have someone that their audio won't come thorough unless they restart their Mac.
I'm secretary for an org. We're trying to use uberconference for our executive board meetings. I like that remotes can call into conference bridge via phone.
I bought a SABRA bluetooth thingie for the room. Seems to work well.
Our results are mixed. We test out the conf room before the meeting starts. Good to go. Then weird stuff happens. People being muted. Their icon shows them talking, but no sound. People being dropped.
I don't mind the unreliability so much. 7 laws of networking and so forth.
I frikkin hate that I don't know what's broken, so can't hope to fix it. Especially DURING the frikkin meeting.
I've used Uberconference (pro) over fiber for a couple of years, and it's been rock solid. In cases where one caller is bad, the web interface will show you who is killing the call quality and lets you mute them.
Except in rare cases, I find the problems you're describing are usually a problem with the end-user, their equipment, or their network. Cheap phones, bad cell connection, bad voip, etc. An unmuted speakerphone with a noisy background can bring most calls to their knees.
We too have used Uberconference, I forget why we ditched that as well, might have been down to the cost of the thing. I actually quite liked it, the web application was solid and it encourages ad-hoc meetings.
The answer I received when I asked about linux support for SH may be helpful here: Instead of porting screen hero, they are (were? 6 mos ago) working on integrating the features into Slack.
The power drain from Hangouts/Chrome is astounding. I admit it's convienent but native does have its benefits it you need a lot of video conferencing (like all day pairing)
Adobe connect allows participants on desktop to enter in the browser without software downloads aswell (http://www.adobe.com/products/adobeconnect/meetings.html).It's expensive though. Anyone know any more inexpensive options that work natively in the browser? Would be nice to get a little list going.
Hangouts requires a proprietary plugin in Firefox on Linux. I'll use it for work, on my work computer, but I'll never use it on my personal computers for that reason.
The plugin is dummy, required by chrome and just gives permission to share screen. Appear.in has been whitelisted on firefox and requires no plugins there.
We're across 24 hours of time zones and conduct a majority of internal and external meetings over video conference. We've pretty much tried them all and Zoom has been the best.
That said, there are still things to improve, so will be interesting to compare.
Yes, agreed. It is great — use it where I work (10k employees) and it was such a relief over all the conferencing solutions we tried (my team was a guinea pig for several).
The coolest thing is that the company rolled out hangouts in a weekend to 100% of the conference rooms, replacing all projectors in the process. It completely democratized remote work and remote offices since people are using Hangout by default.
I've seen almost every solution used internally at Amazon to one degree or another. It's really telling that you get a bunch of highly competent technical people in the room and they still end up fighting with the conferencing software and waste a bunch of time in the meeting trying to get everyone connected.
I'm really not surprised they built their own in the end. It's a clear pain point for companies.
That said, my current employers (not Amazon) have been using Zoom (zoom.us) and it seems to be really quite good. I've had almost no problems with it at all.
At a company of 12 people, our GoToMeeting bill was $15,000/yr.
But uhh, call-in rates of 1c/min/participant? That's going to add up. We would regularly have meetings of two hour duration (programming, planning) with up to six-eight attending is a $10 meeting in itself. Chicken feed compared to salaries but I could easily see pricing of up to $1k/mo with this.
Compare the 1c per minute to the staff cost of meetings and it's not even pocket change. It's like a 1% tax on meetings.
To get a $1k meeting bill with $100k fully loaded avg participant cost or about $50/hr (way too low in metros, but let's be conservative), that's 1600+ meeting hours or about $80k/mo in staff costs.
(I see you do mention this but I wanted to call it out).
I think an interesting way to look at it is, if it can make your meetings one minute shorter than what you do now, you'll actually save.
Actually, I appreciate the heads up... I wonder if we're still on "older" plans that are more expensive (I don't run the billing but I do get to listen to the complaints about the cost). Because yeah, at the current plans we should be seeing a max of $7k/yr.
We've tried loads of them. Skype, hangouts, appear.in, zoom, ... They all sucked with voice and video all cutting out and getting regularly garbled etc. And finally Slack added video, and is amazing. No problems since then, Slack has solved the problem for us.
I'm not sure where the optimism comes from. I too have been surprised at how mediocre most conferencing software is, and concluded that it's probably harder than it seems.
What would great videoconferencing software look like, and what are the odds that this is it?
realtime protocols depend a lot on where are you and where are the participants, and even if you cover everything else you have random things that you have no influence on. like what route does your traffic go, how is the buffer set up on this route and so on.
i had to debug voip and outside of some simple things like not enough resources/bandwidth it can be really frustrating.
Google did and I think they do make a lot of money from it. They've just chosen to target the business sector. We have the Asus Chromebox for Large Meeting Rooms[0] in every meeting room here and it works flawlessly 99% of the time. I'm amazed how well it works. Automatically integrated with Google Calendar, so walking into a meeting room has the upcoming meetings for that room displayed on the screen. Single tap and away you go. If you need to join another meeting, simply type in the name using the remote. So easy.
Everyone has tried. If you're in SF and a BART user you will have seen at least three different ones being advertised. I believe the BlueJeans ones are still up.
I don't know Google even today comes across as a company that does technology very well but not solutions. It's a shame that no startup took this on till now.
Best thing about Hangouts: it was rock solid and bulletproof at first, despite the clunky UI (and weird plugin system). Somewhere along the road, they removed all the crap UI, and in the process:
- it became more unreliable (F5 to get sound working)
- it introduced crazy bugs (says your muted, but not really!)
- it remained software accelerated on mac so it kills the batt
Have you tried Cisco's offerings? Maybe I just have a really excellent IT department, but whether joining audio only, from a tablet, desk, desk phone or telepresence room it just works. It's impressive as hell.
Amazon acquired Biba[0], this is that product with the backend swapped out. It's currently being beta'd internally and they haven't yet added anything over Biba the product. There are some great features planned, from what I've heard.
I really do not like conference systems which do not work on Linux. Not everybody is using a Mac or Windows. Microsoft is also ignoring Skype and Skype for Business on Linux. This is all crap.
We are mostly Mac and Linux at my company.. give Zoom a shot, it's worked out well for video, audio, and sharing... (Europeans in this post have had latency issues though)
We (resin.io) are a totally remote company, with 50 people across 25 cities on 5 continents, and we use Zoom for pretty much everything every day, it's amazing.
I've never seen any latency problems personally - we even do a call with everybody in the company in one room every week, mostly on video, and it doesn't even blink. Drastically better than anything else I've ever tried.
I can vouch for this, used it daily for most of last year.. And we didn't have much of any latency issues with our team in Canada and 2 others in Turkey.
For our needs, https://talky.io does the trick. It "just works" for our Linux machines (along with Mac and Windows). Never tried to use it on mobile (however apparently there's an iPhone app for it). It's peer-to-peer low-latency video chatting via WebRTC, the video quality is far better for us than our previous attempts with Google Hangouts.
I didn't try it out. The old client still works. The only missing feature is screen sharing in multiple parties video calls. I'm using TeamViewer for that. Desktop sharing is much smoother with TeamViewer anyway.
The real plus of Skype over Hangout or Webex is the chat: the history is stored forever locally and I can search every message I sent. We're using a Skype group chat even when we're using TeamViewer.
It's a problem because it seems that the new client is far from being fully functional.
Another update: The Linux client v4.3 seems to be safe. In a post on page 2 of that thread the community manager states
> At this time we are not retiring any of the existing working Linux Clients.
What they are retiring are old Windows and Mac clients
> beginning March 1, users running older versions of Skype for Windows desktop (7.16 and below) or Skype for Mac (7.0 to 7.18) will no longer be able to sign in.
> That would be a big problem. Any link to that announcement?
No problem. I am using the new Alpha Client since three months and it is very stable and usable. The only major missing feature are video conference calls with more but one opposite, but that is actively being worked on. Looks like MS is heading for feature parity with the Windows client.
At my current gig, it's WebEx. The Linux client supposedly does work on 32-bit FireFox using 32-bit Java. I've tried some docker containers that supposedly support this configuration, but so far I can't get anything to work.
WebEx is literally the only reason I even start up a Windows VM at work.
They tout security but I don't think it's open source and it looks like everything is stored on Amazon servers.
Minimally it is centralized, and you can't verify that there's no backdoor. In this day and age, that means we're both trusting their core intentions, and also trusting that some government won't step in and silently force their hand. I don't personally feel that is good enough to be considered secure anymore.
That is exactly what I thought when I read the words "secure" and "trust". If it is not open source it is neither secure nor should anybody trust it. The word used in Britain to describe a statement like that is bollocks.
"With Amazon Chime, you can feel confident you’re communicating securely."
This wording has always struck me as being awful. People felt confident investing with Bernie Madoff as well. I'd rather have confidence from proven security instead of just feeling confident.
I'd word it something along the lines of: "Communicate securely with your team, confident that we've taken care of your online security via [list of reasons]". Yes, confidence is a feeling but for me it sounds better this way. Saying "you can feel confident" reads to me like "with MtGox, your funds can be secure".
Great product idea. At work we use Skype for business and it's a disaster - especially bad is it seemingly randomly says 'your device is causing poor audio quality' and mutes you. The only way to recover is to dial out and in. Before that it was the AT&T solution - such an ugly application with poor usability. If Amazon really polish this product and provide a great user experience and quality they could pick up a lot of business.
Edit: there's a problem here. Skype for business allows up to 250 participants. The AT&T solution (webex maybe) allows, I think, an unlimited number. Amazon Chime has a limit of 250 people. This wouldn't cut it for presentations in large companies e.g. announcement of annual results or divisional virtual 'town hall'
All conferenincing systems have a limit on the number of first-class participants (people who can listen and speak). Broadcast is a different problem and there are a ton of really good solutions when you have less than 250 speakers but many listeners.
There are no conferencing products, to my knowledge, that support more than 250 first-class participants over the internet in a reliable way.
If you have an example, I'd be very curious to play with that product.
Haven't looked but probably no Windows Mobile support either. I know I'm a infinitesimal user base, but the lack of support from services makes me not use them. This is one place Slack really excels and why I hate Hangouts.
I'm definitely going to try this (even though unusable for us because of missing Linux support). We have currently settled on Zoom and it's okay, they do have Linux support.
One problem I have with all video conferencing solutions we've tried (same for my colleagues, all Mac or Linux users, sadly no Windows users to compare) is high CPU usage. I have a 2015 MacBook Pro and when I share my screen CPU usage skyrockets to 150-200% basically pegging the whole CPU. Without sharing my screen CPU usage is at 80-100%.
I have similar problems with certain videos on the web (e.g. Ted.com and others).
Is this something everyone else here sees as well? I always assumed they must because we see it across devices and products.
I wonder if it's a function of what you're sharing? I use zoom with PowerPoint and Keynote all the time and have never had my fans spin up when sharing. Haven't noticed it sharing Safari or my whole desktop either...
As a test I'm currently on a video+computer audio+full screen sharing zoom, and my overall CPU load is at <20%, with Zoom accounting for about half of that.
Their claim of "a third of the cost of traditional solutions" is an apples and oranges comparison.
The basic and plus pricing options, while cheap, are practically useless with only 2 maximum attendees and the $15/user/month pro plan is hardly "a third of the cost...".
Looks like a great product with an average price point.
Skype for Business is available in all Office 365 Business plans except the software-only one (ProPlus). That includes the $5/6 plan (https://products.office.com/en-us/business/office-365-busine...) as well as the $8.25/10 plan that includes all of Office.
This is really cool but I wish they had more details on the Chat part of the solution. What does it look like? Can you theme it? Does it have any integrations (ala Slack)? Can you have inline pictures? Does it have a rich message API?
>"Amazon never participated in the NSA’s PRISM program." - Stephen Schmidt, CISO @ AWS
As true as this may be, the only acceptable form of privacy guarantee is through cryptographic algorithms and open source software. Anything else is a fantasy tale.
And I wouldn't say standard of excellence--just the possibility of excellence. With closed source you can't have even that. You pretty much have to assume the worst.
I suspect they do a good job at a technical level, but they have interests in advertising that are at odds with my privacy interests. I also have no way to know if they are doing Dark Nefarious Things.
From your initial comment, I got the impression that you were claiming that closed source software could not be excellent..meaning secure.
By the way, I'm a big GPL/free software nut. However, I understand the place of closed source software, and under the right circumstances, it can indeed be excellent.
This is where I've come around to appreciating the FSF's moral argument for Free software a bit more than the instrumental-utility argument of the Open Source movement.
Open Source can be bad, in terms of quality. Closed source can be good, in terms of quality.
Security is an interesting case where I don't believe that you can be trustworthy and closed. Could the code be good? Yes. Can I validate in any meaningful sense that it doesn't violate my expectations? No.
Of course it's possible to have obfuscated malicious behavior in Free/Open Source software. But, there is at least the possibility of descovery of such defects. With closed source, there isn't.
We'll have to diverge a little, then, but not too much.
In some cases, such as the security sensitive code written at Google, there are far more eyes on the code than there are with all too much of the critical, security sensitive open source code.
In my mind, it's a matter of alignment of interests.
For the cases of 'run of the mill' security questions, such as buffer overflows, password leaks and the like, Google, Facebook and I have fully aligned interests. None of us want those things in anybody's code.
Things get harder for other security questions, such as data collection, and cooperation with surveillance, legal and otherwise.
In the latter case, state surveillance, Google (and other like entities) have interests that are mostly aligned with mine, but not entirely. They're pushing back on warrant-less, Patriot Act type crap, while efficiently complying with traditional directed warrant disclosures. (As far as we know!)
Fully open source and free software will almost always have full alignment with my interests, and so is better in that regard.
As far as code-level bugs, I think the general rule is that closed source code is pretty poor at companies, with a few notable exceptions, where I think things are a heck of a lot better.
Finally: Wow, I just reminded myself that this thread talking about a new Amazon product. Crazy. (:
Having done a lot of work with financial firms in the past, I found that they're incredibly wary of any agency having access to any of their data.
As a consequence any telephony or messaging product we built had to have a self hosted deployment as part and parcel of our product offering. This meant we usually went for a Java backend which gave us great packaging and install tools. It also meant we had .deb and .rpm packages for all our products.
I can't tell you how much those packages helped. Once you start bundling up your software deployments as proper versioned installation packages you become quite spoilt in the DevOps department - it's hard to use Chef/Puppet or Vagrantfiles for software installations now!
Has this been substantiated? To my knowledge Amazon denies being a part of PRISM and the only thing a quick search reveals is that denial and Snowden criticizing Amazon for not being HTTPS by default on some of their endpoints.
Have you read Snowden's Leaks? All of the major tech companies have been on board for a long time (and that was years ago). How can you believe that a giant like Amazon will somehow magically not be part of it? It's time for the country to sharpen its critical thinking skills.
All of the major tech companies have been on board for a long time (and that was years ago).
I have read the Snowden leaks.
This is one of those times when details matter, and in those details you are wrong.
I wrote this previously[1] about Apple, but it applies here too:
The problem is that PRISM has conflated two separate things, and it is unclear how much of that conflation occurred at the NSA and how much outside.
Apple was (and is) compliant in the "release customer details with a court order" thing, which it seems is part of the PRISM data.
However, there was a second part, where the NSA got bulk access to communications without a court order. It is unclear which companies were complicit in this part. We know Google wasn't (because the NSA slide decks show how they had to intercept Google's inter and intra-data center links which were unencrypted at the time - and Google undertook a crash program to fix that).
Apple's statements are pretty clear: they say they only release information with a court order. That means they weren't complicit in bulk collection - but they may have been hacked at the time like Google was.
Yes, this is a crucial distinction and matches my understanding from what I've read of these public documents: PRISM is a program in which the NSA intercepted Internet and other communications, and then reconstructed the meaning of those communications at a higher level -- that is, interpreting HTTP requests to Google as searches, email views, and whatever else.
I did not see any evidence in the leaked documentation nor the reporting on those primary sources that the companies involved were complicit. If this evidence exists I would be very interested to know, but from Google's actions subsequent to the leaks it did not seem they agreed with the program or were complying with it, and instead took actions to oppose the program by encrypting their communications links internally, and indirectly by advocating encryption in public Internet protocols such as HTTP and SMTP.
I was under the impression that Google gave bulk access to the NSA, and the NSA wiretapped them regardless. I don't have a source to substantiate that claim though.
The US demands - through law - that any company, US and doing business in the US, give access to all it's user data upon simple subpaena by a secret court without notification to anyone, in a situation that can last for years. They're not even allowed to let you delete your data. There is no justification needed and most users are never informed this has happened, not even in the future. If you're a US citizen the time limit is measured in years (and can be extended by said secret court), if you're not a US citizen (or merely suspected not to be one), there is no time limit.
Doing "just" this to their users is what is understood in this discussion under the misnomer "not cooperating" with US spying. One can only assume that the OP has a funny sense of humor.
Given that this is noncooperation, why are we discussing who is cooperating and who is not ? This is WAY over the line, and of course means that no foreign company of any size should trust ANY US company with any amount of data.
And, frankly, it means that given the slightest disagreement in court, you should assume that all your data is public. Famously this facebook/instagram/whatsapp private messages in divorce cases, but not just that. Outlook messages of non-US citizens being picked apart by competitors because of a small non-payment vs non-delivery civil case in a non-US court has happened.
Note that the US government is famous for exploiting private sector relationships for spying and the reverse (exploiting government spying to give advantages to favored US companies).
So you should assume the worst and immediately implement basic security mechanisms (that are standard procedure at most companies now):
1) anything sent to you for any reason gets automatically deleted, especially email, unless specifically and individually prevented
2) any backup system is encrypted and the keys are subject to (1).
3) NOTHING can be put on any cloud system, for any reason without (1) implemented, and you should refuse to cooperate with external parties that insist on such a system.]
4) more strict measures are needed for director level and upward (note: legal definition of director, not just because it's used in company directories). Protocols negotiated beforehand dictate what can only be discussed over secure channels. First item on that list: anything related to any one specific employee.
But the thrust of that article is more suspicion that Amazon is not mentioned in the leaks and questioning the reliability of the company's word. It does cite one source, described in the article as non-mainstream, which asserts that Amazon was a part of PRISM, but that source fails to cite any leak.
Edit: I should mention that the first article casting doubt on Amazon's reliability is published by an independent publishing company, historically an industry that has been at odds with Amazon and harmed by its business practices.
Everything else aside, I am surprised/impressed to see that Amazon has the '.aws' top level domain! Does that mean they will be now branding all their AWS infrastructure under this domain?
This pisses me off to no end. I hate how ICANN approved these product name, (mostly) single company TLDs! I think allowing this is terrible. I know it's just a DNS entry, but it's a fundamental change in the way we think of DNS and the Internet.
I don't know. I agree with you on one hand. On the other hand, though, the second-level domain name that is typically up for purchase is all about branding. I have a hard time justifying treating TLD as special and distinct from the rest of the domain name.
After all, TLD is just the widest level of the hierarchy that DNS names allow. Why limit TLDs to countries if a particular organization has grown large enough to benefit from it, and wants to pay for it?
Amazon paid a lot for that .AWS TLD ($185,000 ICANN application fee alone plus other expenses). I would imagine that this is one of the first sites of many that they'll launch on their .AWS TLD.
Are they competing with WebEx, Skype, or Slack? Looks like a compelling B2B offering from Amazon. I bet they'll have an accompanying hardware to go with this in the coming months.
We use Zoom at Userify and love it. Fantastic Linux client, too. However, it automatically calling me (and saving me time auto-dialing auth codes) would be a pretty nice feature.
So, no video conferencing in basic/plus plan (1:1 doesn't count). It's funny how many attempts there are at making conferencing software that just have audio and some basic chat.
Entry level needs video, since you can get it for free elsewhere (i.e. hangouts).
Don't overlook that a team might keep using something else because they need to make a conf call between 3 Macs, 1 Windows and 1 Linux (a case with a customer of mine).
I am speculating that they are probably using some Electron app. So they could have probably done Linux. I am just guessing that it's a support issue since Linux comes in so many different ways.
I absolutely love the startupish way aws launches new services. They have the whole "landing page" and marketing pitch class A, but the product is alpha if being nice.
There's long, long way to go for this thing to compete with hangout, zoom, or anything else out there.
Source: I've just tried it out, chatting with myself on native app + 2 browsers.
I don't believe so. If you look under the FAQs and the "Security and Control" heading of the Features page, there is no mention of encryption beyond AES-256. Companies offering E2E typically like to highlight that somewhere, even in a non-technical way.
Furthermore, the security is apparently "fully managed", which to me translates to "keys securely stored on our servers, not client-side."
Speaking of.. can Slack hurry up and buy Zoom? Aren't they pretty flush with cash? It seems crazy that they are letting this huge market (where they have a foothold) slip away to new competitors.
I'm not sure I see the utility in this, as Amazon resources and group chat don't really have a lot of overlap, at least for me. What would you need "integrated" into the new AWS Chat that couldn't be accomplished with a chatbot and Slack?
I clicked through, and was accosted with a gigantic video. I wanted to close the tab right there, but I've seen this before, so I scrolled down to make the giant video go away. No dice, every single page element dances and animates and moves, and there don't seem to be any static images on the whole page. I can't scroll to a single position to read the actual text without some large part of my monitor animating in a suitably distracting fashion.
This looks awesome; I'm regularly told that Amazon is a horrendous place to work yet they seem to be producing great software and interesting startup type concepts all the while. Not sure how they do it? AWS is a bit of a mess, maybe it's just there that is problematic...
There are good people everywhere. There are also terrible people in every business. The best people tend to not care about money and leave to go work as paramedics or line cooks or attempt a startup .. and then end up back in software after a year or two. One day we'll get out of here.
How do they authenticate who they are when they call you? I've gotten bogus calls before from "the credit card company", so there needs to be a way to be certain you're talking to the right people.
If it's anything like Slack, the call can only originate from within the application (which is isolated to the single business), so there is no chance for outside calls.
Someone please do what you say and make one that's clearly better than all the other shitty dwarves out there today so the industry can standardize.
"Should we call, or Go to Meeting, or Google Hangout, or Skype, or Lifesize, or Slack, or Adobe Connect, or Zoom, or WebEx, or Chime, or..." It's getting ridiculous.
For new services: Please don't be based in the US or willing to cooperate with the US Government. Remember, "We don't snitch!" is an excellent marketing line -- I'll give you money for that. I don't trust Amazon or any of these at present.
This is the first time that I've heard Amazon really call out AWS as a name brand in a non aws-dashboard oriented product (maybe they have already in the past?) Are Chime user identities AWS IAM users under the hood?
AWS as a more consumer-facing platform probably has a long climb ahead of it but it could be quite helpful for Amazon to differentiate from their many product misses released under the Amazon name.
I don't know how any of these could compete with Zoom, in terms of their offerings. Perhaps Zoom just doesn't have enough of a big name branding push, otherwise, it is hands down a product one should use over any other. I am a free-user of Zoom and I have explored many others out there; there's just no one who come close to Zoom's offerings.
For those who tried screensharing, does it have a pointing-feature (i.e. viewer can point to something)? There's so many products out there like Skype and Hangout that don't support it and I don't understand why not, it seems pretty basic to me (just only show the arrow on platforms that support it, i.e. OSX, Windows and Linux).
Wondering if you have a Plus account and setup a call if you then have remote access, group chat etc - a little unclear what happens between Plus and Basic user. if all users need to be Plus then can see this being a problem.
I'm really curious how this all-in-one concept will compare to the Slack approach of chat as the central functionality augmented by a bunch of integrations with external services.
My Amazon login doesn't work. Is anyone else experiencing this issue? I just logged in on Amazon.com just fine using the same credentials (I use a PW manager). Thanks in advance.
Screen sharing not being available for free is going to make us skip the free trial. We have plenty of options for voice and chat. And video just isn't that important to my teams. Screen sharing, however, is vital. And we are willing to pay, but as long as hangouts works for free, why pay?
I know everyone says hangouts is dead and Google isn't putting much work into it. But it does work. And unless they actually shut it down, it gives us what we need. Free. We don't use it for large webinars or anything, and it has its flaws, but... free. That is a really hard point to beat.
I'm so sick of proprietary walled garden messaging systems. So now I need slack, chime, skype, hangouts, imessage, allo, facebook, etc depending on who I want to talk to.
With most (all?) of these conferencing, the host is the one that has to have an account and pay - otherwise nobody would be able to use them for support, sales calls, etc.
No, "user" means someone who can initiate meetings.
The Pro Plan ($15/m) allows up to 100 attendees per meeting.
So twice the limit and 30% cheaper :-)
From my own experience lifesize voice and video quality is so awful that anything from an egineering company should be superior. Also the stability of the lifesize appliance is horrible. Often enough we've to reboot them before every meeting, because the microphone went dead again.
The only positive point is that it works with Chromium on Linux including the window sharing extension. I hope it's of slightly better quality then webex. But I fear that is overly optimistic at least.
On the other hand Google Hangouts is for free, has from my experience a better quality and all of them ship your data to the US. If amazon offers something similar they and can offer an option that keeps your data in Europe that would be an interesting option.
Agree it's great for small meetings (2-3 people). P2P without any server in between, works as good as your connection.
One thing that bugs me though is using it in Chrome in Mac. 50% of the times the microphone doesn't work and I have to kill coreaudiod and restart the session. I came to a point where I do it before I start a meeting just in case.
It's not appear.in problem though, it happens in Hangouts in Chrome as well
"Meetings call you" is a good idea, as is the reconnecting stuff. Who knows if anyone will use this, but even with all the supply in this market, there is still space for something that actually works well. As someone who works remotely I can't wait until this gets figured out.
Sometimes I have to paste a line or two of code, or a few lines of a stack trace. Sometimes I have to paste a string which contains some particular set of characters. Microsoft Lync absolutely destroys the pasted text. It subtly converts the double quotes into some unicode nonsense. Then it converts some common character sets into smilies. When you copy text from Lync it is almost always guaranteed to be different from what what entered originally. God, I hate Lync with a passion.