With today's announcement, I'm super happy you did this 4 days ago. Time to make a few clones myself.

Also appears to break Wi-Fi.

Qobuz is unfortunately the only HiFi service worth anything ever since Tidal went with the MQA sham.

But yeah, purchasing music is overly complicated by the use of 2 distinct applications one to stream, the other to buy.

Not to mention that I'm outright insulted by how little care they put into organizing their library so that duplicate artist names don't result in a single chimera artist where you need to sift through the non-related artist stuff yourself.

What they did to VAST is a damn shame... Tried reporting it multiple times now via email and support tickets, but those assholes don't care.

You missed one:

ISP - Internet Service Provider

And I apologize in return for the rather harsh way I came across. The common (and frutrating) nature of your comment didn't deserve the terseness of my response.

That is exactly what we do. The problem is that as a managed service offering. It is on us to scale in response to these alerts.

I think people are misunderstanding my original post. When I say that customer cluster will go into stop writes, that does not mean it is not functional. It is an entirely intended function of the database so that no important data is lost or overwritten.

The problem is more organizational. It's that we have a 5 minute SLA to respond to these types of events and that they can happen at any random customer impulse.

I don't have a problem with customers that can correctly project their load and let us know in advance. Those are my favorite customers. But they're not most of our customers.

As for automation. As I had exhaustedly detailed in another response, we do have another product that does this a lot better. And it's the one that we are mass marketing a lot more. The one where I'm feeling all the pain is actually our enterprise level managed service offering. Which goes to customers that have "special requirements" and usually mean that they will never get as robust automation as the other product line.

Our database is actually pretty graceful. It just goes into stop writes status. You can still read any data and resolving the situation is as easy as scaling the cluster or removing old records. By no means is the database down or inoperable.

Essentially our database is working as designed. If we rate limited it further then we have less of a product to sell. The main feature we sell of our database technology is its IOPS and resiliency.

Further, this is just for a specific customer, it has no impact to any other customers or any sort of central orchestration. Generally speaking the stop writes status only ever impacts a single customer and their associated applications.

Also, customers can be very stingy with the clusters they are willing to buy. We actually are on poor terms of the couple of our customers who just refuse to scale and just expect us to magic their cluster into accepting more data than its sized for.

I knew from the thumbnail that this is Virtue by Overwerk. Excellent track!

Kind of a trip seeing a TucsonSentinel article in the broader Fediverse! Lol.

This article is an oldie but a goodie.

I forget, do the pathfinder games use v1 or v2? V1 was basically D&D 3.5 in most ways.

Either way, if you haven't played it, you should put Pathfinder Kingmaker on deck for after BG3

Mid-air 2 Is inching towards release.

https://store.steampowered.com/app/1231210/Midair_2/

I've got alpha access and can assure you it does a great job of bringing the good ol' days of Tribes 2 back. Though there is a ways to go.

Yeah that's definitely an option for me, I love cloudflare. I just know many who prefer to host from home or not using a cloud firewall solution.

Fun fact, the OWASP managed rules break a bunch of things too. I've managed to carve out enough exceptions in the rule to be useful just now, but it took some trial and error.

Then I'll have to change that again in the new version if it ships the new API and removes websockets. As it stands websockets largely bypasses a lot of what Cloudflare does - so an API is likely to cause more issues not less as we figure out that "Hey, the POST action here causes OWASP to trip because it's not as sanitized of an input as it could be".

Another poster said this would be trivial. I mean, it is for static stuff. But doing all the federation, allowing API interactions, and being somewhat resilient to malicious actors is a hard balance to find when changes move at a quick pace.