I get it, Hergé, I got a little too into nuclear reactors once too...
Notices by Velocirooster adminensis :bc: (theropologist@beige.party)
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Friday, 14-Mar-2025 09:49:19 JST Velocirooster adminensis :bc:
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Friday, 14-Mar-2025 05:51:56 JST Velocirooster adminensis :bc:
A stable economy? In this economy??
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Thursday, 20-Feb-2025 09:53:34 JST Velocirooster adminensis :bc:
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:
https://libretranslate.com/translate
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:
Without the "/translate" on the end. I restarted the web service and cleared the cache and it started working perfectly.
It'd be nice if any of this was actually documented somewhere.
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Thursday, 13-Feb-2025 12:38:42 JST Velocirooster adminensis :bc:
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.
How are you doing?
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Thursday, 13-Feb-2025 12:38:41 JST Velocirooster adminensis :bc:
In Oregon I might get lucky and get occupied by Canada, but it could just as easily be China or Russia...
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Sunday, 09-Feb-2025 08:26:46 JST Velocirooster adminensis :bc:
:bc: Attention Beige Party-goers! :bc:
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.
As always, thank you for bearing with me!
Beige-bless 🇧🇧
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Wednesday, 29-Jan-2025 09:05:50 JST Velocirooster adminensis :bc:
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.
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Saturday, 23-Nov-2024 15:31:13 JST Velocirooster adminensis :bc:
FUCK
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Saturday, 23-Nov-2024 15:31:12 JST Velocirooster adminensis :bc:
I was too tired to deal with this shit in 2016. I am way beyond too tired now.
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Saturday, 16-Nov-2024 06:34:53 JST Velocirooster adminensis :bc:
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.
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Wednesday, 13-Nov-2024 02:52:39 JST Velocirooster adminensis :bc:
@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.
Beige-bless 🇧🇧
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Wednesday, 06-Nov-2024 07:02:28 JST Velocirooster adminensis :bc:
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."
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Friday, 25-Oct-2024 06:09:51 JST Velocirooster adminensis :bc:
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.
Me: So, unionize?
Them: No, not like that.
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Friday, 25-Oct-2024 04:04:20 JST Velocirooster adminensis :bc:
I'm in a ridiculous meeting about end-of-year performance evaluations and all the presenters are infected with corporate-speak so they are insisting on calling managers "people leaders" but all I can hear is "people eaters"
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Saturday, 19-Oct-2024 14:32:56 JST Velocirooster adminensis :bc:
Ha but now custom emojis appear to be broken ⁉️
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Saturday, 19-Oct-2024 14:32:55 JST Velocirooster adminensis :bc:
I did a hard reboot of the web server and that seems to have fixed it 🤷
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Saturday, 19-Oct-2024 14:32:53 JST Velocirooster adminensis :bc:
Question for #MastoAdmins. I just did the upgrade to 4.3.0 and everything seems to be working except for notifications. I ran the pre and post deployment database migrations, and the old notifications got pulled over, but no new notifications are showing up. Anyone else have this problem?
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Thursday, 17-Oct-2024 03:25:09 JST Velocirooster adminensis :bc:
:bc: Attention Beige Party-goers! :bc:
I have reviewed the upgrade procedure for Mastodon version 4.3.0 and I will be performing the server upgrade this Friday/Saturday, depending on where you live.
This is a major change that will require a database migration, so I will be taking the servers offline to take full snapshots prior to starting the upgrade. You should expect the site to be down for approximately 30 minutes while I take these snapshots.
The maintenance window will begin at 3 AM UTC on 10/19 and continue until 6 AM. If you are in the Western Hemisphere, that's from 11 PM EDT on 10/18 until 2 AM on 10/19.
The only downtime I'm anticipating is the 30 minutes it will take to make the server snapshots, but as always, please be prepared for the site to go down at any time during the maintenance window.
Thanks, and Beige-Bless 🇧🇧
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Wednesday, 09-Oct-2024 21:42:45 JST Velocirooster adminensis :bc:
At an airport bar and briefly saw a news chyron asking "What's up with Gen Z?" Idk, they slap? What else do you need to know Mr news man?
-
Embed this notice
Velocirooster adminensis :bc: (theropologist@beige.party)'s status on Wednesday, 04-Sep-2024 03:44:21 JST Velocirooster adminensis :bc:
If you ever find yourself biking through Vernonia, OR, be sure to steer clear of this fascist shithole.