System updates seem to have borked the server running kitty.social a little more than usual. In the coming days, I'm going to be rearchitecting the server so that it can hopefully be a bit more stable. There'll probably be a couple of hours of downtime somewhere in the mix.
I'll be doing everything that I can to ensure data integrity and uptime (including backups and moving the service temporarily to another host), but if you don't have your data personally backed up, now would be a good time to do so.
We're not shutting down, no rumors please :))
Questions can be directed to this thread, on Matrix at #general:kitty.social, or on the
kitty.social Discord.
If you want to stay in touch with updates while things are down, the kitty.social Discord would be the best place to do so, since it's not going to explode because of something I did.
Join the kitty.social Discord Server!
Check out the kitty.social community on Discord - hang out with 16 other members and enjoy free voice and text chat.
DiscordCloudflare borked atm. May affect asset/attachment loading on kitty.social as our object storage is piped through them. Their status page is at
https://www.cloudflarestatus.comCloudflare Status
Welcome to Cloudflare's home for real-time and historical data on system performance.
from inspirobot.me, ever relevant today
boost this cat when they least expect it
I have done cursed things. I'm not sure if I should be sorry for this or not.
I'm aware there's a cherrypick update available that kitty.social hasn't moved to yet, waiting to see where this issue goes before I push it:
https://github.com/kokonect-link/cherrypick/issues/602
not working: "Account Settings Migration" fails after update · Issue #602 · kokonect-link/cherrypick
💡 Summary After updating CherryPick, the account settings are migrated, but the migration never finishes and the settings are reset when reloading. When checking the status from developer mode, it ...
GitHubhi all :3 server went splodey but i fixed it i think
cause: server ran out of storage due to an application unexpectedly caching large amounts of data so fast that an alert wasn't fired for it. server hardlocked and had to be rebooted, and docker networking was completely toasted to the point that the daemon wouldn't even start when the machine came back up.
resolution: application reconfigured to limit cache size. docker automated networking disabled as much as possible. investigating whether switching to podman would provide a more stable experience.
sidenote: lmao some of y'all cookin up rumors 👀 if kitty.social goes away for good, i'd at least leave a static page explaining why, but I still have no intention of taking it down.
Lost somewhere between allergies, Benadryl, and Pepsi

guess I'm gay now ¯\_(ツ)_/¯