This quarter was a bit of a struggle for me. I had a lot of stuff going on in my personal and professional life so this project took the backseat for a bit. I’m barely now writing the end of quarter report. Let’s get into it!
For 2024 Q3 we worked on the following:
/recovercommand needs to be more helpful- Improve performance of database queries, specifically on startup, we make so many queries it slows
pawadown
/recover command clarity
This command is not currently exposed to other users, but it is what we use to recover recordings that failed to save because bugs. In the past, this command would fail and would not say why. Often times, people want to restore recordings that they forgot to save or that has already expired. For ease of support, these messages must be clear.
I would still like to test this command for a bit longer before we expose it to the public.
While on this journey, the Recording Embed got a new face lift, see!
We now include the dates in your locale and will tell you how much time your recording has left before expiry. We also include a link to the recording on if it’s on Discord.
We also are able to determine the recording duration on the fly now and if you see a ??? that means it’s an empty recording.
Database Performance
There’s not much to say here, but we improved our slowest queries in the database and now everything is faster. Nothing that’s visible to the user, just less lag when running commands altogether.
Q4 Goals
We’re already a month in and I have travel and family reunions to attend so I don’t expect much progress. I’ll roll over all the open issues from Q3 into Q4 and start with that.
Here’s the starting list:
/recoverfails to recover large recordings/infoshows inaccurate recording count/autorecordsends unnecessary message- Reduce message noise on messages
Just one stretch goal:
- Add Log in with Discord to the web-app
See you next year!