Blockers for conf #1
Description
- Require validated email links
- Show email visibly/prominently (it's just in the URL but I think it's pretty obvious?)
- Ability to blacklist compromised emails (this can be added later and redeployed)
- Email sending process
- How to actually send and what email address/server to use? (we're using mailgun, for now with shiny.express but after conf we should get sre help us to get access to Posit's mailgun)
- How to trigger the releasing of more invites?
- Do we need to be able to single out emails to invite (jump the line)?
- Google Analytics
- Deploy with chat updates (like markdown formatting of user input). Either merge this branch or point requirements.txt to the commit at the tip of the branch (if we use a branch name, it may get cached) Chat tweaks py-shiny#1607
- Intro guide (blog post?)
- Add padding to chat container
- Incorporate scare disclaimer about lack of privacy/security
- Save BYOK in local storage
Nice to have
- S3 logging
- Disclose logging in the initial message
- BYOK doesn't get logged
- Gracefully handle hitting token limit