sebpuetz / voices Goto Github PK

• API endpoint to login / refresh token
• present token when:
  • establishing voice connection
  • using other APIs
• oauth?

• Gateway REST API

Currently messes up internal state

• use session ids and allow this?
• return error?
• kick first joiner?

• register users
• api for users to join servers

Diesel doesn't seem to support multiple DB backends with a single implementation

1. duplicate DB code for SQLite?
2. Rewrite DB module with sqlx

SQLite schema will have to differ from the postgres schema (e.g. different types) and should probably differ in terms of structure (registering voice servers doesn't make much sense), so giving 1. a shot before tearing it out might make sense

• Send wav file to make testing nicer

voice server and gateway pull in lots of unnecessary dependencies in distributed setup

• client sends voice server failure
• backend checks health of voice server
  • if bad:
    • reassign voice server (tricky wrt. races)
    • announce all sessions
    • broadcast new host
  • if good:
    • too bad

"Closing" a local channel is probably broken - another client can be joining the "closed" channel and be stuck in it