Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bring Your Agent to Teams

microsoft.github.io

Post reply on HN
Print view View original

81–89 of 89 posts

Re: Bring Your Agent to Teams

#81

Post by willio58 »

GorsyGentle wrote: post #12

> Your users live in Teams. No, I assure you, we do not. Nobody wants to live in hell. Even at my current company, we are mandated solely to use Teams for meetings. But nobody uses it for chat. Thankfully we have Slack to save us from that hell. Even if giphy is disabled because it might have R rated content whatever the hell that means.

Same at my company. Moved to teams for the lovely “cost savings”. It’s a hog, nobody likes it. So then a portion of the company went to get on Gather which is cool. And the rest of the company never gave up slack so it’s this fun thing where nobody knows where any meeting is and it can be in 1 of 3 apps because why would it be simple?

Re: Bring Your Agent to Teams

#82

Post by gerdesj »

_carbyau_ wrote: post #26
gerdesj wrote: post #3

Earlier quoted context omitted.

When I were a nipper lag/latency over 30ms was considered a bit crap for voice unless satellite links were involved. That's for circuit switched networks. Human conversation works best with a sub 25ms latency and you will start to notice lag at 30ms. Nowadays with all our massively more powerful links (Gb vs Kb) but packet switched, we often end up resorting to a form of half duplex radio protocol. That's just voice,…

How much did a phone call cost per minute from UK to Australia in the 70's and 80's ? The modern experience is not perfect but audio is usually far better than the 70's and 80's, video is often an option, and in general the experience is orders of magnitude cheaper.

"How much did a phone call cost per minute from UK to Australia in the 70's and 80's ?"

I think around £5 per minute or more. A quick search found this: https://www.austehc.unimelb.edu.au/tia/576_image.html#Table%... so my memory is not too far off and that is the other way. Bear in mind that a squid (£1) was worth rather more in the '70s, than now.

A circuit switched call in the '70s - '90s (at least) within the UK was nigh on perfect. There was no noticeable latency. Call quality was way better than a modern Teams or Zoom call (with no video). Your £500 laptop has shit microphones and speakers but you do insist on not using them like a "dog and bone" but instead as a "comms solution".

Re: Bring Your Agent to Teams

#83

Post by gerdesj »

simfree wrote: post #10
gerdesj wrote: post #3

Earlier quoted context omitted.

When I were a nipper lag/latency over 30ms was considered a bit crap for voice unless satellite links were involved. That's for circuit switched networks. Human conversation works best with a sub 25ms latency and you will start to notice lag at 30ms. Nowadays with all our massively more powerful links (Gb vs Kb) but packet switched, we often end up resorting to a form of half duplex radio protocol. That's just voice,…

PCMU and PCMA voice frames are 20ms or 40ms, and no one is running with no jitter buffer, so your 30ms number doesn't make sense. Even circuit switched networks are not often below 30ms, to hit that you'd need to make a local phone call on a fully analog circuit.

Standards such as G.711 and co don't "enforce" a latency because they can't. Latency is a property of the network, not the traffic.

You cannot use terms such as "PCMU and PCMA voice frames are 20ms or 40ms" because that makes no sense whatsoever. PCMU and PCMA are protocols that traverse a network - they do not define it.

I'm old enough to have used circuit switched telephony for some years and perhaps you are too. I recall it as being largely latency free, in that a call never sounded weird unless a satellite was involved, in which case the call costs were horrific and you ended up doing a sort of informal form of radio protocol to talk, which generally ended up in a rather scrambled mess of a conversation.

I can remember amassing a stack of 20 10p coins and calling my mum from the UK to West Germany in the '80s and having to feed the coins faster than I could talk. I sent an aerogram later.

Re: Bring Your Agent to Teams

#84

Post by vladvasiliu »

mexicocitinluez wrote: post #69
bob1029 wrote: post #51

Earlier quoted context omitted.

I have 3 accounts in teams. Two are in client tenants and one is my personal. I haven't had any issues because I can't work on more than one customer at a time. I still get notifications from the other clients when I'm not actively staring at things. I could leave teams off all day and still be fine. The business requirements don't change that quickly in my part of the world. If you are doing 1099 for multiple custom…

You're arguing with someone who thinks clicking a dropdown and selecting a different tenant is the worst thing in the world.

Because it then restarts the whole app, so you have to wait again for ages so it does whatever it is that it does.

And since you can actually have a chat window open from a different tenant, there’s no reason why they should have you do this ridiculous dance.

If teams wasn’t so god-awful slow, and with an interface jumping around all the time, people would probably complain much less of having to select something in a dropdown.

Re: Bring Your Agent to Teams

#85

Post by vladvasiliu »

theshrike79 wrote: post #78
mexicocitinluez wrote: post #68

Earlier quoted context omitted.

So you think I didn't read your comment because you said "Nope, nope, nope" and I quite literally provided you with instructions on how to do it? That feels incoherent. > To check messages in a client Teams I just have to RELOAD THE WHOLE APPLICATION lol Where are you reading "reload the whole application"? It's literally a dropdown menu in the Teams application. It switches the tenant. > That's a weee bit harder tha…

”Teams will reload in that environment.” It cannot connect to two environments at the same time, it basically has to restart from scratch to swap environments. Whether it’s a drop down or not is irrelevant. Their official instructions say “just use multiple browser profiles”. Not very multi-tenant of them.

Actually you can detach a chat to a separate window and switch tenants in the main one. The separate window will keep working. Tried this a week or two ago with the heavy windows client.

Which is actually all the more infuriating to my eyes: this whole reload the app crap is obviously not necessary!

Re: Bring Your Agent to Teams

#86

Post by vladvasiliu »

lifescarcity wrote: post #62
Jedd wrote: post #16

Earlier quoted context omitted.

Do you mean the way that Microsoft hijacked open-parenthesis, and you can't choose a different character to trigger an emoji call?

https://youtu.be/2PYBj_VhvXg?si=eQogTv825zSyeBvX You can use :

Which is extremely practical for French, where the colon comes after a space. So if you want to write an actual colon to introduce a list on the following line, you’ll just input whatever the default smiley is.

Re: Bring Your Agent to Teams

#87

Post by earleybird »

fuzzzerd wrote: post #18
GorsyGentle wrote: post #12

> Your users live in Teams. No, I assure you, we do not. Nobody wants to live in hell. Even at my current company, we are mandated solely to use Teams for meetings. But nobody uses it for chat. Thankfully we have Slack to save us from that hell. Even if giphy is disabled because it might have R rated content whatever the hell that means.

Sounds nice. I've seen places that have essentially given up email in favor of teams for all communication.

Now add a retention policy of 30 days. Business memory lived in those emails and now it's 50 First Dates

Re: Bring Your Agent to Teams

#89

Post by crote »

mexicocitinluez wrote: post #60
crote wrote: post #37

I just want Teams to have a proper webhook API! Why do I have to create a weird "workflow" to receive webhooks in a chat channel? Why does it have such complicated ownership permissions? Why is it automatically deleted if it doesn't see "enough" use? Why do I need to send the message in some weird "adaptive card" format - for which there are barely any ready-made libraries? Heck, why can't I create a new chat channel…

> Why do I have to create a weird "workflow" to receive webhooks in a chat channel? Create the webhook in Microsoft Flow and connect it to Teams. You get observability and monitoring out-of-the-box.

Yes, that is exactly the problem. I just want a webhook to deliver some messages - you know, like all the other chat platforms? I don't want to read a dozen pages about "Microsoft Flow".
Post reply on HN