Jon Harmon

Hmmm, the `base_bins` example doesn't EXACTLY work with that. Sorting out a solution for that one, too.

An interesting tip: This works, and displays as the original: ```r get_x

The description of "Superseded" might make this difficult (see https://github.com/rstudio/shiny/issues/3627#issuecomment-1370178724 ).

To officially log it: someone mentioned they saw the same behavior on mac, so it isn't a windows-only thing. Could be related to mocking and/or snapshots.

The same warning shows up in [2.2.7](https://mastering-shiny.org/basic-ui.html#action-buttons), and probably other places where icon() is used.

I wrote a [package to deal with this sort of situation](https://cran.r-project.org/package=dlr), I could implement that solution pretty easily. Good call!

I *think* Slack fixed this! Need to test further to make sure.

It's only fixed if you're already signed into the proper Slack. If you aren't, but you're signed into a different slack, it still shows that one. Grr.

I think I'd want to pass it in a header. Probably still a good idea to encrypt these tokens, even in the cookies. Of course if the app decrypts them......

The beginning of the login is the same regardless, with a "Sign in with Slack" button. When they return from Slack with a code in the URL, ask if it's...