> "I scraped every single restaurant in Greater London"
How hard is that now? I assumed that Google is very protective of that data
> "I scraped every single restaurant in Greater London"
How hard is that now? I assumed that Google is very protective of that data
That's not what the author was suggesting (or indeed, what they built). They were trying to untangle the positive feedback bias showing up first in the rankings gives.
I think there's probably a lot more to untangle, but as a first pass it's super cool!
Just look at Nikola.
Isn’t the problem (having only read a little about the controversy) that the non-hybrid appears to be strictly worse, except for the (~10%) decrease in transmission size; and that no one has articulated why that’s a desirable tradeoff?
On the face of it, I don’t see a problem with the tradeoff (both ways, that is) choice existing. I expect smarter people than me to have reasons one way or the other but I haven’t seen a reason for saving bandwidth that could articulate the concrete use case that it makes a difference.
> There is no backdoor in ML-KEM, and I can prove it. For something to be a backdoor, specifically a “Nobody but us backdoor” (NOBUS), you need some way to ensure that nobody else can exploit it, otherwise it is not a backdoor, but a broken algorithm
Isn’t a broken algorithm also a valid thing for NSA/whoever to want?
Them saying they want to use it themselves doesn’t actually mean much?
As an example - if there's a weakness that affects 50% of keys (replace with whatever hypothetical number), NSA can make sure it doesn't use those affected keys but still retain the ability to decrypt 50% of everyone else's communications. And using the entropy analysis from this post, that would require 1 bit hidden in the parameters which is clearly within the entropy budget.
Isn’t the problem (having only read a little about the controversy) that the non-hybrid appears to be strictly worse, except for the (~10%) decrease in transmission size; and that no one has articulated why that’s a desirable tradeoff?
On the face of it, I don’t see a problem with the tradeoff (both ways, that is) choice existing. I expect smarter people than me to have reasons one way or the other but I haven’t seen a reason for saving bandwidth that could articulate the concrete use case that it makes a difference.
> There is no backdoor in ML-KEM, and I can prove it. For something to be a backdoor, specifically a “Nobody but us backdoor” (NOBUS), you need some way to ensure that nobody else can exploit it, otherwise it is not a backdoor, but a broken algorithm
Isn’t a broken algorithm also a valid thing for NSA/whoever to want?
Them saying they want to use it themselves doesn’t actually mean much?
It achieves a 30–40% speed improvement on x86-64 and ARM64 (Apple M4 Pro) by reversing the direction of the year count and reducing the operation count (4 multiplications instead of the usual 7+).
Paper-style explanation, benchmarks on multiple architectures, and full open-source C++ implementation.
> Years are calculated backwards
How did that insight come about?
Why temporarily?
"What would you do if GPS went out, permanently?"
The whole room collectively didn't want to think about it. There doesn't appear to be a plan. We've collectively put all our eggs in one basket.
IFR was designed long before GPS and for the most part, GPS has been shoehorned into the “old” system. VORs around the country are still “primary” for navigations; airways are still primarily defined around VOR radials; and approach plates to large airports have plenty of non-GPS precision approaches. (Some smaller GA-only airfields that recently got IFR approaches might be WAAS/GPS only).
Losing GPS might increase workload for some sectors (en route sectors who won’t be able to clear aircraft direct to waypoints) but not likely TRACON who are vectoring aircraft on pre-defined approach plates.
If you pick a random commercial flight on your favourite flight tracker and check it’s route, 99% of the waypoints on it are defined as VOR intersections, not GPS coordinates. (The remaining 1% are likely en-route waypoints and not in the departure/approach area).
Also, the instrument proficiency requirements for pilots require multiple approach types to be logged every 6 months so they are definitely capable of non-GPS approaches.
Is it just Mozilla testing the waters with the announcement?