Things will be very very spotty for a few days.
We have introduced a blocking/performance issue related to our caching backend (we believe) with recent code changes. When the perfect combinations of routines hit it literally stops all processing. We have to manually remove this block and then things work fine again (until the next perfect storm). It takes all of a few seconds to address but we have to be watching to catch it.
We have a temporary work around in place but you may run across the "site disabled" screen more often than you'd like (apologies to dark theme users).
This issue is our #1 priority, so it will be fixed as soon as possible.
I may be a bit stressed and thus a tad bit emotional but I really appreciate the encouragement from you goats. It goes a long way. Thanks.
It increasingly appears that this issue is being exploited. Voat has experienced malicious requests the last few days but we have not considered these two situations connected. We will attempt more drastic measures to work around this issue shortly. Many apologies.
I have redirected Voat to use a Memory Cache instead of Redis and shut down the API for now.
The issue is still present and we will be working solely on solving this issue. Again, sorry for the inconveniences associated with the work around. API was turned back on earlier today.
This might be fixed now, but don't get mad if it returns even angrier than before.