It had one @&_+ing job...

And they managed to instead product design something with 2 (3?) different chat models, limitations around every corner, an incomplete API for basic use cases (e.g. getting notified of @'s), and an embedded ability to build entire apps inside Teams.

Example of how it looks:

https://hacks.mozilla.org/files/2021/02/Screenshot-2021-02-0...

https://en.m.wikipedia.org/wiki/Domain_name

So for example:

a.foo.com sets cookie X (Set-Cookie: X=value;)

a.foo.com sets a cookie Y on foo.com (Set-Cookie: Y=value; domain=foo.com)

b.foo.com can read Y, but can not read X

I think the answer is more banal in that some of their oauth flow runs in a different domain from the main application. I think this is tied to wanting to reuse part of oauth flow in the desktop application.

Remember "DOS Isn’t Done Until Lotus Won’t Run"?

That large companies do self-serving underhanded tricks is not a conspiracy, just yet another Monday in the office.