HN user

namkt

52 karma
Posts0
Comments28
View on HN
No posts found.

This was the immediate and exact same thought I had the moment I read the first sentence of the post. Then I stopped reading. Clearly this was not an engineering decision, and passwords should be trusted to no one but competent engineers and cryptographers.

The government publishes infection rates at the county level. The county's health department may also have guidelines that differ slightly from the general nation-wide ones. If there is an uptick of infections in the local community and the boosters are recommended there (though still not necessarily at the macroscopic level), then that seems pretty clear to me.

But I still concur with OP. I am not an expert, and I don't know how to choose between experts with differing opinions. What I do know is that I trust certain institutions more than others.

Because only the US seems to have this guideline. Canada and the EU are not recommending boosters to the general population as pointed out above. It's similar for the flu; afaik, the EU recommends flu shots for ages 60+, not for the general adult population. The US makes a big deal every year on getting flu shots; in corporate media, in shops and outlets, etc.

Edit: I stand corrected on the Canadian front; I had old information.

ECDC/EMA seem to have similar guidelines:

https://www.ema.europa.eu/en/news/ecdc-ema-update-recommenda...

e.g. "At the moment, there is no clear evidence to support giving a second booster dose to people below 60 years of age who are not at higher risk of severe disease. Neither is there clear evidence to support giving early second boosters to healthcare workers or those working in long-term care homes unless they are at high risk."

Great to see a C/C++ CPU-based implementation that runs on a variety of platforms. Most other ASRs seem to be either abandonware, a whole bunch of Python that only runs on PC, and/or solutions that send all your audio to someone's server.

My assumption is that it's not just the syntax, but that their compiler does the right thing. Though someone said it's based on LLVM, so who knows how much control they get.

It's constant time in that it always takes the same amount of time regardless of the extent to which the two strings are equal. It is a different concept than constant time in complexity analysis.

What's even more confusing is that it is also constant time in the complexity analysis sense given that the mac is usually a fixed-size string after choosing a hashing algorithm.

I know, right? The strongest theoretical crypto is a one-time pad, often presented in its XOR form in the first chapter of every crypto book.

But hey, if Google says math comes first...

Didn't they originally claim to never show ads in search given that it is in direct opposition to search results quality? Back in the days when Pagerank was hot.

I think the point behind "constant time" here is that the comparison always takes the same amount of time, and not based on how many characters in the two strings are equal, to prevent a timing attack. "Constant time" isn't very accurate here because given a choice of hashing algorithm, the hash is a fixed-length string and therefore even a trivial string comparison technically "runs in constant time", at least if we allow the typical abuses of language in CS.

AI Art Panic 4 years ago

I'd really like that one where you give it a ref sheet and out comes a 3D model, or at least a baseline to tinker with in, e.g., Blender. I think NVIDIA was doing text-to-3d recently, but it did so from a single image and I'm not sure as to the accuracy of the model.

I would have thought that allocations in managed languages like Go/Python would have been the "fast" part of the processing. Isn't technically the GC that's slowing you down, and not the allocation per se? For one-shot input/output programs like these I guess you could tune the GC to kick in with less frequency.

You also note that reading a file sequentially from disk is very fast, which it is, but there is no guarantee that the file's contents are actually sequential on disk (fragmentation), right? We'd have to see how the file was written, and I guess at worst you'd be reading sequential chunks of a hand-wavy 4KB or something depending on the file system and what not. I'm sure others can fill in the details.

Just nit-picking here.