# Today:

- Consume a consumable (the ticket gets used in the Bigscreen app).
    - PROBLEM: Tickets as consumables are currently stored in stripe.  Is this actually a good solution?  Probably not, because it makes it hard to issue free tickets.
- Nail down the API flow for setting up an account (including documentation).
- Get all user's orders for a specific product code.
- Get all available consumables of a specific type.

# Bugs and refactoring.

- Decide on the right HTTP code to return when a user attempts to register with another user's email address?  422 is not right, 409 maybe gives too much info.  500 might be the right approach?
- bcrypt password hashing should be asynchronous, and NOT be part of the user schema.

# UI

- When purchase is successful, redirect to a "success" page.
- Improve receipts UI so it's not dumping out json.
- Form for the steam-only user to verify with username and password.

# Changes?

1. Use ISO region and currency codes for products in stripe.  Use this to match up the user's IP region to the products they can purchase.
2. Receipts are not tickets either.  Need to worry about this now?

# Future stuff to think about (this week!):

- Discord "Rich Presence" (https://discordapp.com/developers/docs/rich-presence/how-to)
- Instrumenting the c# product.
    - Automatically detecting frame rate drops and poor performance and automatically sending support notifications.
- Implement APIs in C#.
- Come up with a solution to handle env keys.
- Analytics (convert js to c#).