subeta.net/achievements...

We've added more new achievements in the last week than in the last year, probably!

Reworked the trapped minions! Lots more strategy now 👀

subeta.net/news.php?act...

does this work now? 👀

I'm aware that legacy isn't loading right now, taking a look!

This image contains two pictures of a sitting Kumos, a pet from the pet site Subeta. It is a pale blue, dog-type creature with crescent moon shaped markings on its legs & over its left eye. On the left side of the image, an older, cuddly version of the Kumos looks at the viewer with loving eyes. This side is labeled 'DLSS 5 Off.' On the right side of the image, the newer, & normally far more adorable, version of the Kumos has been poorly edited with heavy blue eye makeup, pink blush, tinted hair tips, & glossy red claws. It is a horrible sight to behold. This side is labeled 'DLSS 5 On.' The labels are a reference to a meme.

One yassified kumos, just for you~ ✨🐕

I will be making sure that bathhouse streaks are kept in tact, don't worry about that!

Still just a little bit longer, sorry folks!

Yup, I'll be running a script to make sure they're preserved!

Data transfer is complete 🎉

That means that now it's time to set up our various sites (sapi.subeta.net, kumos.subeta.net and the legacy site) and move over the DNS. It's not much longer from this point

We're at 66% complete, the last really big hurdle is user shops & the logs that come with them!

still climbing! 📈

an extremely weird container to container networking issue

We're looking at another 2-4 hours for this transfer to be complete, and then some amount of time for cleanup and getting the new services all set up.

If we get past Subeta reset time, I'll run that manually (and this should resolve all of the other reset related issues!)

Data is being imported (which means it's been fully backed up, zipped and transferred), and filling up in it's new location. We're up to inventory data, and I'll update as we move along.

gonna yassify some subeta images and call it DLSS 5

that's kind of what i've been doing! but then you need to write a migration tool, make sure that every path to that code in legacy is closed off (there is not a promise that some item or opponent has custom code that calls to it of course lol) and at that point i'm already moving on to another fire

I wishhhhhhhh! But now that I can make modifications to the legacy site (which wasn't a sure thing before!) that makes it much easier to condense things, or remove old old old features that haven't been in use since 2008 but if we just removed the table it'd crash the whole site

muchhhhhhhh smoother than i expected, too! i'm very excited to be able to actually add things to the legacy site, or make tweaks. i knocked out ~10 items from the quality of life improvement thread, hoping to knock more out once the site is back up!

Oh, from the stuff that I'm removing, yes I did say that!

It's all infrastructure code to manage the connection time between the servers and the provider - which were only added over the last week to try to compensate for lag. none of it will be needed now!

Still transferring 🫡

Nothing is getting removed - but I *am* now more able to *add* things to the legacy site, so that means significantly fewer things will need to move to Kumos immediately, and there will be way less pressure to move over.

No need to apologize, and vent away! It's been super, super frustrating - the only option I had at this point was to take it down to do this!

I hear you that it's been an especially frustrating last few weeks and hopefully today I'll be able to ping you with things feeling much better

We'll be ensuring that bathhouse streaks from the last two days are restored (like we did when the site when down earlier this week)

Unfortunately that isn't really how it works, I wish I could!

The upside is I can remove all of the custom code made over the last week to try to offset the network latency issues we've been having, and that will be very nice.

So I'm moving us back to a more traditional setup. The downsides are less able to scale up when there is high traffic (events) and down where there is less (summer), resulting in an overall wasting of resources, but that is a fine tradeoff to make at this point.

We're moving, again! Sorry for the immediate downtime, we've just hit the physical (literally) limits of what is possible on the host that we moved to, which is frustrating.

I don't have someone monitoring this social account outside of when there is downtime (and I'm posting updates here) - best place to get answers is on the forums.

subeta.net/forums.php/r...

Thread on what is going on!

What a journey. Our hosting provider started having issues in the middle of the day while I was pushing a new deployment every 5 minutes trying to solve the problems.

Which pushed Subeta into such a state that it couldn't even serve traffic anymore, and required reaching out to support. We're back!