meta: v3

[rumblefrog]

Discussed in #44

^{Originally posted by rumblefrog February 2, 2021}
Before else, I'd like to mention v3 has no definite deadline, it could be months, or it could be years before I find time to work on it. This is purely a manifest of things I'd like to include when v3 releases.

---

New features to be introduced

• Bi-directional voice-support, with audio mixing of bound channels (but note that the Discord bot could only be in one Discord voice channel at a time).
• Real-time audio transcription to text, with TTL of the raw audio file for manual transcribing.
• Improved logging and lookups; Discord message search has proven rather inadequate for more advanced searches, especially cases requiring filter by time, player, and origin.
• Better routing specifiers, including routing by identifiers, type, origin, metadata, and/or combination of any.
• Transmission encryption, it's 2021

Things being removed

• Built-in UI - This feature is heavily underutilized and creates unnecessary complexity inside the codebase; the likely clause will be decoupling UI from the primary binary and offered separately if there's a demand for it.
• Built-in service - While a built-in service manager is handy, it's found that debugging such is much more difficult than a pure system service manager.

Notes

• v3 will not be compatible with v2, but upgrade steps will be provided.
• by default, logging (audio, text), which is separate from the relay component, will be disabled, and it's up to you as the end operator to comply with any legality terms before enabling it.
• I will attempt to provide a Heroku one-click deploy button for non-experienced users.