Jump to content

Wikipedia:Articles for deletion/Primorial sieve

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by BaSzRafael (talk | contribs) at 10:08, 22 June 2024 (Primorial sieve: Reply). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Primorial sieve (edit | talk | history | protect | delete | links | watch | logs | views) – (View log | edits since nomination)
(Find sources: Google (books · news · scholar · free images · WP refs· FENS · JSTOR · TWL)

Blatant WP:OR: the unique source is not published and consists of vague consideration on a supposed algorithm that is not even described. D.Lazard (talk) 13:23, 20 June 2024 (UTC)[reply]

to D.Lazard
The algorithm IS described!
0. (Ground floor) We divide the number under study by the highest primorial #p — which "fills" no more than 100% of the integer variable used, which has a limited capacity (number of digits).
a) We check the remainder of the division, whether it is a prime number (this is only "on the ground floor"!), but necessarily greater than "p". This case signals that "a" CAN BE a prime number.
b) Otherwise, the number under study "a" is a composite number, and we have one of its divisors (or even two! — at least...)
1. We abandon the use of the primorial function, and from now on in the subsequent floors we use its "nephew": the Van function, choosing its upper argument so that the obtained product of subsequent prime numbers, starting from the lower argument and ending with the upper one — does not exceed the "capacity" of the variable used. The lower argument is the "ceiling" of the previous floor.
2. We check whether the remainder obtained from the division of "a" by #p — is a number relatively prime to "b", and to #p.
a) If so — then "a" CAN BE a prime number
b) If it has common divisors (and THEN there will be at least two of them!) then it is a composite number, and we have its divisors.
3. We loop the procedure from point 2 — that is, we define subsequent values ​​for the lower argument (the "floor" of the Van function) and the upper argument (its "ceiling").
4. Each time we find any divisors of the tested number "a" — we divide it by them, and we only subject the RESULT of this division to further factorization.
5. We proceed in this way until we obtain ALL divisors of the composite number
6. If we do not find any, then they... do not exist! And the number "a" is a prime number, and with 100% CERTAINTY.
What do you not understand? After all, the algorithm is as simple as building a flail... BaSzRafael (talk) 00:23, 21 June 2024 (UTC)[reply]
This page is for the discussion whether the article must be deleted, not for claifying its technical content. If this content may be clarified, this must be done by editing the article, not here.
This being said, the above description is too vague for allowing to verify whether the algorithn is correct and, if it is correct, whether it is more efficient that the existing algorithms. In any case, it seeems to require to know all primes below a given bound, which should made it useless for the number sizes for which factorization is difficult.
Again, this is not to Wikipedia editors to check these things. This is for this reason that reliable WP:secondary sources are required. Up to now, no such sources are available D.Lazard (talk) 11:07, 21 June 2024 (UTC)[reply]
Thank you for your answer:
clear, simple and understandable.
I also thank:
PianoDan
David Eppstein
XOR'easter
Chiswick Chap
Russ Woodroofe
all the participants of the discussion, even though not a single voice was raised in defense of the entry:
- Well, that's a shame, but I understand that Wikipedia is governed by certain indisputable laws, and I have to accept them, even if I don't like them and they act contrary to my expectations.
I also thank you for the fact that even though not a single voice was raised in defense of the entry, it has not been removed yet, but is publicly available and everyone can also express their opinion on it.
You have devoted your time to me, reading the text and then commenting on it - for which I am grateful. And I would be even more grateful if I received a handful of comments on what to do so that the text remains on Wikipedia. What should be improved in it, what should be improved?
Finally, I would like to pass on the optimistic message that I received from both Mikołajeks and the rest of the team:
- according to the new version, still warm like those buns straight from the bakery, they state that RSA is not threatened, because their belief that the algorithm presented here dismantles RSA - was a mistake, and it resulted from the fact that they did not take into account certain things that simply did not exist earlier in the developed theory.
If suddenly, overnight, encryption became ineffective, civilization would suffer irreversible losses. It would be simply a tragedy, no one would be safe, and certainly not the Internet.
BaSzRafael (talk) 07:56, 22 June 2024 (UTC)[reply]
RSA is not threatened because, as this article states, this method (if it is an improvement) improves on trial division by using multiplications instead of divisions, achieving only the speedup one would obtain from the relative timing of those two operations, a constant factor. Other factorization methods are far faster, faster than trial divisions by factors that grow very quickly as the numbers involved get large. Such non-constant speedups, even better than the ones already known, would be needed to threaten RSA. Compared to that, the difference between multiplication and division is trivial. —David Eppstein (talk) 08:02, 22 June 2024 (UTC)[reply]
dziękuję za wyjaśnienia, przydadzą się. BaSzRafael (talk) 10:08, 22 June 2024 (UTC)[reply]