Yes. Quic and other protocols are too new and don’t have a ton of support in firewall and inspection tools that are used by said corpos. It’s even required in the DISA STIG requirements to disable quic at the browser level.

It’s unclear to me what you’re trying to achieve, and it seems like a counterproductive way to go about it, prone to failure, and needlessly expensive for anything of moderate size.

You’re probably over indexing on the importance of downvotes if you’re just doing this for yourself. If you’re looking to make something actually useful to everyone, votes are probably an indicator of interest.

Personally, I read the readme and concluded that that project wasn’t worth my time given the model and AI generated walls of text to tell me it has mobile accessible webpages and end to end encryption. Neither of which is a significant or revolutionary feature in 2025(almost 26) and are basically expectations.

Honestly it annoys me how much the well has been poisoned with rust that we’re even talking about the language here. There is so much focus on rust that we’re not even talking about how they literally couldn’t tell the difference between their software crashing in production and a ddos attack.

They had no visibility into their runtime environment, and from my understanding of the Blogpost, didn’t even look into the possibility until the entire cluster went down from this bad config.

Like, even assuming they did input validation, what should the clickhouse services do when they’re fed an invalid config? I’d argue the only sensible thing would be to refuse to start. But it seems like crashing wasn’t being detected at all.

That might be true, but claiming that people only moved because they were propagandized into doing so by a for-profit company is absurd.

This is incredibly reductive and at best looking at mumble through Rose tinted glasses.

Mumble has had a rocky past as a useful piece of software and it’s absolutely not been a discord competitor any more than TeamSpeak is a discord competitor.

Maybe it’s changed recently, but mumble has not had the feature set that made discord useful in the first place.

The stress-ng package is like 5MB.

There are a lot of possible ways to validate this, namely just downloading a benchmarking tool and using it. Is there a reason you don’t want to do that?

Isolation has the connotation of a single thing or individual being… Isolated from the group. Atomization is meant to evoke a sense of the more widespread impact on society. After all, if something only impacts a small subset it’s considered… “Isolated”

That being said, atomization is definitely not a new term to describe this…

History and good explanations of what was changed and why is incredibly useful for being able to determine if something is a bug, a feature, and why something was written a particular way.

I’m not super stringent on commit style, but it absolutely helps to structure commit messages, especially in larger projects where they’re being worked on piecemeal.

2fa isn’t a panacea and won’t solve every problem. It does help though. Why do you think supply chain integrity isn’t something they care about?

Phoronix comments are always such a mixed bag. I get that something still running after 20 years is cool and all, but it’s not necessarily a good thing.

Personally, I usually take issue with the missing institutional knowledge on such projects. It doesn’t matter if it runs, it matters that we’re running something we can fix if it explodes.

I recently built some stuff with the latest gcc compiler that was written in c89, but still compiled. That’s pretty sweet and very convenient for us, but the flags and the commands aren’t documented at all. So we have to spelunk through ancient scripts to find the right incantations or worse, read the code. Because who needs docs for an internal tool ammirite?