Someone thought it’d be an optimisation to send meta tags outside of the initial request response? For real? The frontend universe is so unhinged.

Victoriametrics for metrics (7x ram reduction vs prom), Loki for logs but evaluating Victorialogs. Then grafana for ui. Cannot recommend vm enough, it’s fantastic.

VictoriaMetrics CTO here.

If you hit some issues with VictoriaLogs or if you have ideas on how VictoriaLogs usability could be improved, then please file issues at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/ . We appreciate users' input and always try making our products easier to use.

There’s a good 5 part series on this from 2014: https://news.ycombinator.com/item?id=7636066. Fascinating how slow and brittle the system is. Even more so that it’s not been upgraded to something real-time (see:Europe).

Sounds like we should adopt this (the homebrew and apparently superior) system to the whole country and dump PLTRs spy stack.

I’m done with iOS, apples endless anti user/developer bullshit has pushed me over the edge. For my next phone I’ll be moving back to Android-ish something sans google components.

The same process is happening to macOS too, but at least Linux is an easy switch there.

https://github.com/sickcodes/Docker-OSX can do it

Moved to wasabi from their s3-like b2 product because it was so utterly unreliable. Pretty wild list of things if true.

I use b2 and never had any issues. What problems did you have?

Anyone play Mindustry? Confused for a second there.

You might like pyinfra.

Just about every time someone complains about ansible, there's a comment to plug this project but pyinfra seems to opt-out of the cloud provisioning part, instead delegating to its terraform connector, which drags in all the nonsense that entails. That makes it not only less useful but (IMHO) a horrible name for a project that only does "remote execution" and not infrastructure. The fact that it's even missing @aws @azure @gcp connectors further solidifies "who is the audience for this thing?"

Not everyone runs cloud servers. pyinfra seems to fit my needs like a glove, so I guess I am the intended audience.

I never liked the provisioning overlap Ansible has with Terraform, so it makes sense to me: provisioning servers with tf, configure them with another tool, whether it’s ansible or pyinfra. Well, at least in theory

There’s a lot more to infra than the cloud, pyinfra is designed to work in any of these environments not just the over-abstracted, over-hyped cloud. There’s plenty of good tools for setting up the infra, any pyinfra can easily be integrated.

> Just about every time someone complains about ansible, there's a comment to plug this project but pyinfra seems to opt-out of the cloud provisioning part

Which Ansible is absolutely atrocious at, so that makes sense. Use the best tool for the job (so Terraform, maybe Pulumi/tfcdk if you hate your future self/future teammates for infra.

OK it requires access to the pod network. Bad, but not that. Here’s the 9.8: https://github.com/kubernetes/kubernetes/issues/131009