std::unordered_map is one of the worst ones
It should be noted that the benchmark focused on the std::unordered_map implementation from GCC 13.2.0. I'm not sure if/how this conclusion can be extended to other implementations such as msvc or clang.
I think a common misconception is that there’s a “right way to do git” - for example: “we must use Gitflow, that’s the way to do it”.
I don't think this is a valid take. Conventions or standardizations are adopted voluntarily by each team, and they are certainly not a trait of a tool. Complaining about gitflow as if it's a trait of Git is like complaining that Java is hard because you need to use camelCase.
Also, there is nothing particularly complex or hard with gitflow. You branch out, and you merge.
This shape certainly beats a triangle (...)
Nature loves triangles.
appears to be a weak patch.
It's not a patch. It's eliminating an attack vector, and the one which is more pervasive and easier to exploit.
Security-minded people pay far more attention to what software you run than what hardware you have.
For Signal, no.
There is an argument to make about using custom versions of Signal that route their traffic through your own infrastructure.
This would count as France running their own service.
Given that Signal relies on centralized servers to route traffic, and if I'm not mistaken they use AWS in US instances, this means that your Signal traffic is being fed straight into the US security services' infrastructure. France might be a staunch ally of the US, but they do go through great lengths to preserve their independence.
Leaving my 0.02$ here:
Please don't deploy this bot. It's annoying, it contributes nothing to actually create interesting content for the community to engage, and in fact its main output is spam.
It does more harm than good. Please don't.
I'd add that if the idea was any good then instead of spamming people left and right, it would suffice to crosspost stuff on target communities.
Even then, you’ll still want to have in mind instances known for spam, bots, or shady content have been blocked.
Is there a list tracking these instances?
You're absolutely right. Wrong link posted to the wrong community. I apologize for the snafu.
But since then, i came to a revelation, than it takes years of experience to knw which wire to touch
Might be, might not be. A popped capacitor doesn't require a lot of skill to spot.
Not all jobs are rocket surgery.
My experience is the exact opposite. Even though it has its moments, more often than not it just hallucinates and proposes a lot of stuff that neither matches definitions nor could possibly compile. I guess that this might reflect the impact of having classes with similar names in multiple namespaces but it's bad to the point I prefer to rely exclusively on plain old autocorrelation.