Hey folks, I want to give you all an update on what's been going on with me lately. I haven't been around as much as I should be, which is a generous way of saying that I've been dropping the ball quite a bit over the last few months. It would be easy to just say that I've been busy and move on, but that's not the whole story.
Since I started this instance I have tried to be very transparent about my limited technical ability so that everyone understands that this is very much a process of me figuring things out as I go along. What's been harder for me to be transparent about are my mental health limitations. I've told myself that I'm just having some anxiety or a mental block when it comes to administering this instance, but at some point, sitting on the couch, looking at my phone, knowing I should pick it up and check on the instance, but feeling completely paralyzed about it, I had to admit to myself that perhaps this is what depression feels like.
The fact of the matter is that I've been feeling pretty overwhelmed lately. It's not anybody's fault and it doesn't only have to do with Beige Party. It's a confluence of factors in my life and in the world in general that have settled on my chest like a heavy weight and made me feel powerless to do anything. I've compensated by trying to avoid any kind of conflict and that has included administering this instance.
I get it. People are angry, and they have a right to be. I'm angry too, and I don't always know how to process it. I'm frightened about what's going to happen in the next four, ten, and twenty years. There was a time when I held onto the fiction that we'd all wake up from this nightmare and things would go back to normal. Now I have to admit that the normal I'm pining for has been dead for at least twenty years, and it wasn't all that great to begin with. However we get through this, it's not going to be by looking backwards, but by looking forwards, and finding people we can trust and work with to make the world that we want to live in. It's going to be a long and painful process, and I'm afraid we're just at the beginning of it. But the only way going to make it through is together.
None of this is intended as an excuse, just an explanation of where I am mentally these days. I am going try to make a concerted effort to do better and not let things get away from me as much as I have in the last few months. I can't promise I will always succeed but I can promise that I will continue to try.
One thing I want to be clear about is that I am not abandoning this instance. When I registered this domain I did it for ten years and I intend to be here for at least that long. This is a great community that we've built over the last three years. That has everything to do with all of you and very little to do with me, but I will continue to do my part to keep it going because it's worth preserving the good things in a world that is becomingevet more dismal.
I want to thank you all for continuing to bear with me and placing your trust in me. I will do my best to continue to earn that trust. For the most part my my interactions here have been positive and it's something that I really value. I feel honered to be a member of this community.
As always, if anyone has any questions or concerns, please feel free to reach out to me directly. If I haven't responded in a timely fashion, please don't hesitate to poke me about it. Yes, I might get overwhelmed at times, but I still take my administrative duties seriously and I always want to do what's best for this community. I hope that I can continue to live up to that standard.
And we are back! I have completed my database maintenance and we are now on the latest version of Mastodon. I still have some more work to do on the database, but I can do that at a later date. I think that was plenty of downtime for one evening.
I've been experimenting with enabling translation on my instance and since I've seen zero documentation about how to configure LibreTranslate with a purchased api key, I'm going to share my findings here.
Pretty much every guide out there for enabling translation on a Mastodon instance using LibreTranslate assumes that you are going to be setting up the LibreTranslate server yourself. That's admirable, but translation is pretty resource-intensive. When I tested this on my instance, it was taking about 2 seconds to translate a post, and even longer for longer posts. Plus there were some languages that weren't working at all. That was probably on me for not setting up the language packs correctly. Maybe I'll give it another try, but somewhere in the middle of wrestling with the translation server, I realized that I'm here to run a Mastodon instance, not a LibreTranslate instance, so I went and purchased an api key from LibreTranslate for their lower tier of $29 a month (good for 80 translations per minute). Based on the average donations we get each month, that seemed a reasonable cost that we could afford. The trouble was, configuring the instance to use the api key didn't seem to be working at all.
Now if you go to https://libretranslate.com it lets you play around with the api and shows what the post request and the subsequent response looks like. In the post request and in the api documentation, the endpoint for the translation service is:
but if you set LIBRE_TRANSLATE_ENDPOINT to that value in your .env.production file, it won't work. After a bunch of googling and experimentation, I finally went and looked at the pull request for this feature on GitHub. And that's where I saw that in the code for the post request it takes the configured LIBRE_TRANSLATE_ENDPOINT value and then adds the "/translate" at the end of it.
Even though I was sure I had tried this before, I set LIBRE_TRANSLATE_ENDPOINT to:
Oh hi! I was Just thinking about what part of the country I should move to based on which coalition nation I'd rather be occupied by when this shitshow inevitably reaches its logical conclusion.
In the past month there have been two incidents that I'm aware of where the web server was hanging and the site was unresponsive for several minutes. One of those seemed to resolve on its own eventually; the other I happened to notice as it was occurring and resolved once I gave the web server a hard reboot. It's possible that this has happened more than twice and I just haven't noticed it.
Looking at the logs I'm not seeing anything specifically failing, so I think what's happening is that occasionally traffic spikes are overwhelming the system resources. If left alone, the server can eventually recover but it will remain unresponsive until it does.
We have grown a lot in the last two years so this isn't totally surprising. I have scaled up the web server from time to time in order to account for the processing demands of increased traffic, but I'm reaching the limits of what I can do with a single server.
So, what I'm planning to do is spin up an additional web server and put them both behind a load balancer. This has a few advantages. If one server is overtaxed then traffic can be shifted to the other. It also means that for simple server updates (ones that don't involve database schema changes), I can take one down to run the update while the other stays up. In other words, in most cases I won't have to take the entire site down to do server maintenance.
This all sounds great, but as usual I have no idea what I'm doing. So I'm going to move slowly to set things up in the background and make sure I'm 100% certain everything is going to work before I push it live. Until I have this new solution in place it's possible things could be a little bumpy. So far the server hanging has been an intermittent issue, which is why I want to take care of it now, before it becomes a bigger problem.
Wait, so you're telling me the powerful elites got behind some nutjob that they thought they could control only to find out that they in fact can't? If only there were some kind of historical precedent that could have warned them of this possibility.
The trees are acting falsely demure today, blushing daintily here and there. They have plans but are in no hurry to get to them. They stand on the side of the road, waving coyly. Oh hello, I didn't see you there. Nothing really, just taking my air. It is really a lovely day isn't it? Don't you just love the sun beating relentlessly upon your person? Doesn't it make you feel sticky and alive? Oh, this old thing? I just found it lying around the underbrush and threw it on for a splash of color. Oh really, you're too kind. Don't mind her, she doesn't say much. She's a cell phone tower.
@SymTrkl@Alice@RickiTarr This is beautiful and it's the exact reason I started this instance. Humor is not superfluous or unserious. It's how we process the inherent absurdity of the world around us. It's even more important when things are bad and there's no way to make it better by trying to rationalize it. Even from an evolutionary perspective the theory is that it developed as a way to process cognitive dissonance in a way that was non-threatening and reinforced social bonds. We all need a place to get real weird with it sometimes.
I have to complete my self evaluation today and I really just want to write, "This year I did work and you compensated me for it, as per our agreement."
Them: We're forcing you to go back into the office because we believe work is more meaningful when employees are together and have a shared sense of comradery.
In the middle like a bird without a beak 🐓 Admin of this here instance 🦖 I have no idea what I'm doing 🦣 he/him 🙆♂️Alt Text: Avi is the head of a rooster with a velociraptor's face instead of a beak, seen in profile and looking majestic af. The header is a hilariously inaccurate 19th-century woodcut depicting an iguanodon and a megalosaurus as big lumbering quadrapedal lizards biting each other. Neither of them seems bothered by this, in fact they both are sporting big goofy toothy grins.