Hacker Newsnew | past | comments | ask | show | jobs | submit | akarve's commentslogin

there has to be some missing information on how he found the area of water that fully consumed exactly that amount of oil as it simply doesn’t make sense without that. for instance one can spread a teaspoon of oil over 1, 2, n square meters and at some point the oil goes from m later thick to one to less than one.


Such an experiment was described in a science book I read as a kid. They dissolved oil in alcohol so as to measure a very small quantity of oil, and then a a knitting needle was used to stretch the oil film across a plastic container filled to the edge with water (until the film breaks).


> more popular than i expected

we know what's important here on hn


This is one of those “so cool yet so silly” brainstorms that I’m grateful someone was audacious enough to entertain. I’m both relieved and saddened that it never came to fruition.

There’s a word, chindogu, to describe things that are less than useless. In some sense this project engendered more problems than it solved. Like so many other attractive brainstorms.


Most SO answers were non-answers or word salads. Thankfully one of you added an answer explaining that the cursor is already straight given that it must be visible from the graphics coordinate origin (upper left) and is 45 degrees wide.

https://ux.stackexchange.com/a/149837/45927


Bart Gijssens's answer is neither of those things, and gives an explanation, including the historical rationale, and links to citations.


...this is using wordplay to avoid answering the question. It doesn't explain anything.

Also:

> Thankfully one of you

We can see your name.


I was sure to read “the forces of vim have invaded our headquarters and now hold our CEO hostage.”


Hard agree. Civil & mechanical engineering have a culture and history of blameless analysis of failure. Software engineering could learn from them.

See the excellent To Engineer is Human in just this topic of analyzed failures in civil engineering.


> If you just make up a number claim it’s prime and nobody disputes it

You can test if a number is prime in polynomial time, much faster than a sieve. There’s no need to test every divisor to know whether a number is prime or not.

Algos like RSA generate large primes millions of times every day—-there’s nothing to take on faith.


Doesn't RSA typically settle for numbers that are probably prime?


Technically I think so, so there’s a tiny bit of faith for RSA but absolutely none for primality in general https://en.wikipedia.org/wiki/AKS_primality_test


I’d argue that you’re just misunderstanding what makes a number prime. You can literally never be 100% sure a randomly generated number is or isn’t prime, it’s just the way numbers work.


I think you have some confusion about RSA cryptography - it relies on numbers that are deliberately generated using very large (known) primes, so these numbers are definitely not "randomly generated".

It takes a short time to generate such a number but a very long time to decompose it, but this is a different problem than telling whether a number is prime.


The primes used in RSA are definitely randomly generated for each new key, unless I’m misunderstanding what you’re trying to say. And afaik determining that the random number is prime is a mixture of “generate a random number using a formula that has a high probability of generating primes” and various probabilistic primality tests. It’s possible AKS has been incorporated to prove the numbers are prime in modern implementations, not sure. But historically RSA traditionally (definitely before 2006) determined primality probabilistically.

ECC doesn’t require primes and so is safer in that respect although I’ve been hearing that ECC might have structural deficiencies that causes a swing back to RSA for the most secure applications.


deterministic tests generally aren't used because the brobibalistic ones can easily get you to a guaranteed chance of 2^-100 of not having a false positive which is enough that it is dramatically more likely that 6 cosmic rays came and flipped the answer than a false positive.


Yeah I didn’t think anyone used deterministic ones because speed, but I don’t know how much faster probabilistic variants are because if the deterministic ones aren’t too much slower I could imagine the added safety margin would be more useful assuming that key generation isn’t a critical path in an application (which it shouldn’t be because typically you don’t generate many many RSA keys dynamically)


A lot of the problem is that the types of people who care about deterministic results care more about asymptotic runtime than wall clock runtime. The other problem is that the asymptotics of AKS are still pretty bad (log(n)^7.5 vs log(n)^2 for Miller Rabin).


Counterexample, roll a dice. That gives you a randomly generated number. You can then test whether said random number is prime by enumeration.


There is literally an entirely deterministic algorithm for checking primality, so you can be 100% sure that a randomly-generated number is prime: https://en.wikipedia.org/wiki/AKS_primality_test


you absolutely can. aks is a polynomial time deterministic primality check.


Ok then break all cryptography with that. It just proves my point you can SAY you can do it but in practice you can’t.


Cryptography is about finding large prime factors of a large number. That's a much harder problem than just determining whether a specific number is prime or not.


I don’t understand you just say it was about finding factors, okay yeah that determines whether a number is prime. You’re not telling me anything I don’t know, I just disagree with your stance.


I don't understand your stance.

You seem to be claiming that the ability to determine whether a number is prime or not is extremely difficult and that it would break (some) cryptography if it were no so. My stance is that (some) cryptography would not be broken unless factorisation of large numbers into two large primes becomes easy.

Can you clarify how you think that some cryptography is broken by a relatively simple test of whether a large number is prime or not?


primality checking is much easier that factoring. it's somewhat unintuitive, but there are deterministic methods of primality testing that don't tell you the factors.


AKS is an example of a deterministic algorithm which works out whether a number is prime or composite and runs in polynomial time in the number of bits in the number.

https://en.wikipedia.org/wiki/AKS_primality_test

I'm not sure why you would expect this to break all (or any) cryptographic protocols.


prime testing is much easier than factoring. you need to factor to break rsa


Some cryptography depends on hardness of factoring, not hardness of checking primality.


How would that work?


He's probably a *-sulfide or copper-* expert. Or maybe just a physical chemist that the press is ginning up. Actually, the latter. His page doesn't even mention copper or sulfide; and makes only one mention of conductors.

https://chemistry.illinois.edu/jain


Jack Dorsey is corroborating it on nostr npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m


Mobilecoin, where he is CTO, confirmed it

> Joshua Goldbard, the CEO of MobileCoin sent the following statement to ABC7 News: "Bob was a force of nature. Helped to birth Android and CashApp into our world. Moby was his dream: a privacy protecting wallet for the 21st Century. I will miss him every day."

The shameless plug for "Moby" does bother me.

Sad day for the community.


Jesus that plug. Have some class.


That is terrible, how tasteless



How does one navigate this? And why is Jack not posting this on Twtr?


Jack is posting it on nostr.


No. The backups have their own secrets and no relationship to one another. You register them as distinct keys with each app.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: