Things are moving along well, I'm glad to report. We are going through a transitional period with @mantequilla-soft and, by proxy, @threespeak. It seems like some hard decisions cannot be postponed anymore, but I suspect things are going to work out just fine in the end.
I am a little sad, I admit, at the possibility that @snapie's witness might have to shut down. This is not a decision I've made just yet, but tightening the belt is part of the survival game. I guess when it's all said and done, math will dictate the outcome. But I'm not going to lie, the mere possibility already feels bad.
At any rate, I'm working hard with @tibfox on getting the internal guts of @threespeak rearranged, so to speak. We hit some important milestones today, and that's enough reason to celebrate. A new instance of MongoDB, a backup, and a reassignment of the primary copy all happened without much of a hiccup. Restarting @threespeak services took some hit and miss attempts, but we seem to be up and running well at the moment.
A new update on the Threespeak Encoder has also been deployed. An edge case became so common that I was finally able to get my hands on a raw file before it got deleted. Turns out people upload videos with no audio quite a bit, and the solution is to add a silent track. Who knew? The encoders, at least the ones I operate, are now running the new code, and videos without audio should work from now on.
I hope in the coming days to announce yet another relaunch of @threespeak. This time, it's not only about the new features, which I think are going to surprise a lot of people, but also because we are being forced to migrate away from Vercel. An operational cost we can't delay addressing much longer.
I trust that as long as we put in the work, much of the ordeals and challenges we'll face during this transition will remain completely transparent to users. Or at least, that's my hope.
