powercf

> If there's any format regularity in the output, like it's in one of the PKCS message formats, that could be detected.

After entering some junk data, and incrementing the counter field, /every/ generated password has started with one of [aeiouy], so there clearly is some regularity in the output, and I guess more if analysed in detail.

I'm not very familiar with Redis, so I might be missing something here.

But if the choice, after a Redis update, is between: a) my software breaking and, hopefully, an error message saying "redis failure parsing 'XYZ'" or b) my software /maybe/ continuing to function, while passing commands to Redis that it's ignoring

I would always pick (a), and I think most programmers would think likewise.

It seems to me that they should quit on reading any input that they can't parse. At best silently ignoring bad input leads to software not doing what it's supposed to do. At worst it leads to attacks like this.

I realize this is contrary to "be conservative in what you do, be liberal in what you accept from others", but I never thought that was a good way to write software.

> If you ignore warnings that are benign, over time there will be more and more warnings and it becomes harder and harder to notice new warnings that are bugs

I -Wno-XYZ the common ones that I don't feel are issues

> > I wonder if the argument for/against -Werror is really the difference between the beliefs "a compiler warning is probably a problem in my code" vs "a compiler warning is probably a problem in the compiler"

> Compilers are remarkable pieces of software, in the last 4 years or so I can remember 3 compiler bugs I found in Clang and GCC and all were segfaults not incorrect warnings. That's after running Clang and GCC thousands of times on hundreds of projects. So as a rule of thumb if the compiler reports a warning it's correct.

What I mean is that, for example, gcc warning me about "if(x = y)" is a problem in gcc, as it's generating superfluous output for my correct, intended input

> It doesn't take months to add -Wno-deprecated to a Makefile.

After which you no longer have any visibility on what deprecated fxns you're calling, which means one day updating that library again is going to completely block you until you rework your interface.

-Wno-error=deprecated would probably be better.

The time you're spending reviewing warnings, determining warnings don't make sense, and individually suppressing warnings sounds like it could be considerable. Worse is that it's never ending - each new gcc/clang (or change from gcc to clang etc.) could bring hundreds of new errors…

Otoh, gcc and clang now support colorized output. Warnings stand out a lot if you're building with make, and can be noted and disabled or fixed (if it's an actual problem) ${WHENEVER}, without having to drop everything now.

I wonder if the argument for/against -Werror is really the difference between the beliefs "a compiler warning is probably a problem in my code" vs "a compiler warning is probably a problem in the compiler"

There is no reason why their behavior while promoting events should be excluded when considering their character. I don't believe I have ever seen another sportsman threaten to kill a competitor, or gloat about having inflicted a career-ending injury. Not to say that it doesn't happen, but it's more visible in UFC.

I can't speak for the GP, but it's (apparent) popularity worries me. It is a brutal sport, with some of the dregs of society participating at the highest levels (here's an interview between two competitors: https://www.youtube.com/watch?v=eTzhVVIjLCE). I don't think I would have an issue with UFC etc. if the fighters could show a little class and some respect for each other. As it stands I think it supplies very bad role-models for teenage and 20 year old males it is surely popular with.

From the .plan it appears that the qw client didn't predict entities aside from the player. I don't understand the fundamental difference between netquake and quakeworld so I can't explain why, but quakeworld always felt somewhat "unreal" when playing with a high ping, whereas netquake didn't (it just felt slow).

I would imagine this isn't very relevant these days, as nobody plays with a 300ms ping (+ packet loss) any more.

I played Quake at the time on dial-up with an approx 250ms - 350ms ping. I believe the majority of players preferred quakeworld, but I always felt it was a regression on vanilla Quake net play. Vanilla quake was slow, but the world felt "real". Your position, enemies, rockets, doors etc. were where they were, and you could react based on that. Quakeworld added prediction, and more client side processing. As a result, you could no longer depend on things being where they were - the enemy you just saw run around that corner did not run around that corner, and instead fired a rocket in your face. You are dead but your client hasn't got that packet yet.

From the article:

> All three days, the nurses are reluctant to hand over the baby, saying my actions are irresponsible.

> Every shift change, two nurses stand by my bed and inform another two nurses of my status as a combative patient. “This woman tested positive for methamphetamine,”

This does not strike me as very professional. The medical staff should have considered the possibility of a false positive, and given the mother the benefit of the doubt when she said she wasn't taking methamphetamine. Telling the mother that she shouldn't breastfeed and that CPS have been called, while not stopping her from breastfeeding (presumably they have no legal power) is the worst of both worlds: increase stress/worry (which is something the child would pick up on), draw everyone's focus away from the actual birth and the child, while simultaneously allowing her to potentially pass this, presumably harmful, drug to the child. Madness.

> Some bad laws have historically been overcome precisely by people ignoring them, rendering them effectively unenforceable.

On the other hand, some good laws have also been overcome by people ignoring them. For example laws governing limitation of police power (search, detention etc.), traffic laws (speeding, jaywalking, aggressive driving against cyclists, a relevent example in Brazil is ignoring of traffic lights). If it gets to the stage where everyone is doing it, then the authorities no longer care.

I don't know whether WhatsApp has the requested data or not, but I think overall this action is a good thing: it shows that even important (in Brazilian society) companies are not above Brazilian law and if there is a problem with what this judge did, or the power he's wielding, then it should, hopefully, lead to that being fixed.

The alternative is ignoring and not enforcing the law, and ending up with bad laws, which can then be selectively enforced (see Böhmermann affair for example). This may appeal to some, but it's clearly not for everyone.

Has a quantum computer been built that can solve a problem faster or cheaper than conventional hardware? Afaict no. From an outsiders pov quantum computing seems to be advancing, but until the science and engineering can overcome the challenges and build something that can do something useful, then it seems too early to study it (outside of curiosity, the theory is kind of interesting).

Couldn't they add 1.5TB of swap to their 1.5TB of memory system and run a ramdisk on that? I'm curious what performance would look like, but given 2-3k IOPS for the on-disk solution, and 20k IOPS for the in-memory I would naively expect at least 11k IOPS for random access, which should have been fast enough without the headache of clustering?

I think the egg-drop challenge example is terrible. If the egg + protection impacts the ground at a fixed velocity, the most relevant factor is the /distance/ the egg moves before coming to a stop. So if it requires "three feet of bubblewrap" (nonsense number, per the video), then it will also require three feet of microlattice, unless the microlattice applies a more constant force on the egg as it compresses.

Bad examples like that make it difficult for me to trust such videos.

Your value of pi is incorrect in the code, comments and readme. pi is 3.1415926... (and not 3.14151926...).