Deep Cuts Before Deployment

The team at @mantequilla-soft and I are getting ready to move away from the legacy way of handling videos on @threespeak. While this change won't radically alter the user experience on the surface, under the hood it requires some serious reworking of our codebase. Lots of careful cuts.

If you've used shorts on either @snapie or @threespeak, you already know the direction we're heading in. The swap, however, isn't quite ready yet.

The best way I can describe the current issue without leaning too hard into nerdistics — a language I've been told is incredibly boring — is that upload performance on the new system is still rough. The uploads work, but patience is not exactly a universal virtue, and it may be wise not to test the limits of people's tolerance in that department.

For the past few days I've been reworking the upload process, changing not only my own logic, but even the libraries the system depends on. Deep cuts, to be clear.

As I type this, I'm preparing to press the button while also keeping a rollback plan close by.

No matter how much one tests a system, you never really know until you know. At least in my experience, no amount of testing can make software truly bulletproof. That doesn't mean we shouldn't try our best anyway.

With that said, since I won't be touching the legacy uploads for @threespeak just yet, and these changes are currently focused on shorts, I want to apologize beforehand for any issues that might appear along the way.

I also want to encourage people not to be shy about reporting bugs or strange behavior. A reply on Hive will do just fine, but if necessary, you can also reach me on Discord.

It's time to pour another hot cup of joe and see what happens.

MenO