I'm still trying to figure out how different this is from their "parameter store" offering in AWS Systems Manager. The main thing I guess is you get more control over key rotation.
This is really unfortunate. I've used the IRC gateway feature over the years to lurk in multiple Slack groups and looks like this will be the end of using (social) Slack groups for me.
Their web interface has just.. not cut it for me. Too resource intensive and not enough control over how/when I am interrupted. This was why I gravitated to the IRC gateway in the first place. Oh well.
The console dump was super useful, thank you for that!
I think it might be because you have third-party cookies disabled [1], and the Google Auth client uses an iframe with cookies to do its thing. I replicated it myself by disabling third-party cookies and the results were similar to what you described.
I'll look into what I can do about this on my end tomorrow. Thank you again for your time!
You are right. Twilio Connect has sadly not been a great user experience and this is something we're reconsidering. We used it initially because it was a low-risk approach to see if people would use a product like this. Thank you for your feedback :)
Two-way messaging and call proxying is likely the next big features we'll be rolling out.
We went with the Twilio Connect route initially as a low-risk approach to see if there's an appetite for a something like this. Sadly it has not been a great user experience and we're definitely going to reconsider it (Twilio Connect).
As you might have guessed, we haven't actually decided on pricing yet but I wanted to put something on that page so that people can get a feel for how much it would cost them.
And yeah, the system we were using for auth (Cognito) did not at that time have an adequate 2FA solution, which was why we went with Google. Now that they do, we'll likely use that which would allow people to also signup with a username/password (in addition to Google, etc).