Yeah, exactly. I was about to say flatpak exists and isn’t proprietary.
Also, the snap for docker/compose is hot garbage.
Yeah, exactly. I was about to say flatpak exists and isn’t proprietary.
Also, the snap for docker/compose is hot garbage.
That’s the “getting better at not screwing up” part.
Y’all need high availability in your lives.
Website is amazingly responsive as well, seems to be working.
They’re impressive. And operating systems have come a long way. I think software has to catch up before this can happen.
I really want to see servers running more efficient architecture.
This failure essentially means there’s an issue at either the DNS or TLS layers. I’d start looking at TLS, namely trusted root certs and OpenSSL.
As an operator, this who thread reads like a bunch of devs who don’t understand networking and refuse to learn.
Sure, for smaller applications or small dev teams it doesn’t make sense. But for so many other things it does.
I guarantee there is a Zabka very close.
If I had to guess after managing enterprise WAF across hundreds of domains…
It’s either a crowler or vulnerability scanner, and may be scanning by IP address. I don’t think you configured anything wrong.
You may want to add some form of captcha or user agent based filter to get rid of it. Good news is that it’s not necessarily something to worry about.
I’d avoid IP based blocking. It’s only temporarily effective.
It’s a trade off between puncture resistance and handling. I personally don’t want to ride these tires or gatorskins. I’ll stick with my continental gp 5000s, and just deal with punctures sometimes. The ride and grip are so much better they’re worth it.
Stuff like this has the potential to be game changing for things like home automation… Looking forward to the results!
I see 803 forks currently, keep up the good work!
Mint with cinnamon desktop is where it’s at for ease of use.