[QUOTE=smh;202402]I did a quick diff between all open ended sequences from last week and this morning and I get the following[CODE]<snip>[/CODE][/QUOTE]

Also 789090, 792820, 789816. It seems that someone has a grudge against us (the aliquot project) - they clearly know about Subproject #3 and the effort on 4788.

[quote=10metreh;202445]Also 789090, 792820, 789816. It seems that someone has a grudge against us (the aliquot project) - they clearly know about Subproject #3 and the effort on 4788.[/quote]
Weird. :huh: I wasn't aware we had enemies...at least the set prime button has been taken offline for now.

And 790308 step 341. And some incorrect work was submitted afterward.

Well... does anyone remember the Bill Gates incident? :huh:

Did anyone by chance ask Syd whether he could find out the culprit from logs? If we could get an IP, or better yet a FactorDB username, it might be possible to connect the dots to a mersenneforum member. That way, when the Set Prime feature is eventually turned back on (hopefully in a more blunder- and vandal-proof way), we'll know whose privileges need to be revoked before we do so.

[QUOTE=mdettweiler;202459]Did anyone by chance ask Syd whether he could find out the culprit from logs? If we could get an IP, or better yet a FactorDB username, it might be possible to connect the dots to a mersenneforum member. That way, when the Set Prime feature is eventually turned back on (hopefully in a more blunder- and vandal-proof way), we'll know whose privileges need to be revoked before we do so.[/QUOTE]

I have asked Syd when I sent him some emails yesterday evening and today in the morning, but he seems to be too busy at the moment, so he seems just to have repaired alq4788. (In my mail I have written too, that there are a couple more vandalized sequences, and that he should also look to this thread - let's hope that he finds some time to do so in the near future.)

Rather than fix them all manually, it might be easier to implement a "Retest Primality" button. There is a legion of volunteers here willing to hunt down the bad entries and click the button.

[QUOTE=Andi47;202461]I have asked Syd when I sent him some emails yesterday evening and today in the morning, but he seems to be too busy at the moment, so he seems just to have repaired alq4788. (In my mail I have written too, that there are a couple more vandalized sequences, and that he should also look to this thread - let's hope that he finds some time to do so in the near future.)[/QUOTE]

That was post 666 in this thread - I can only think that the devil has something to do with this :censored: database vandalism.

[QUOTE=10metreh;202313]No, they aren't: sequence 13596 has a "p91" that already has factors submitted but is still listed as prime.[/QUOTE]

That's been stuck at the top of the worker queue for quite some time now.

Like at least a month or two.

It would be nice to run a mysql procedure on [I]all[/I] current number objects, and if they are even (except 2, of course), drop the prime flag. If they are stored wordwise, that would be easy to code looking just at the last limb.

Otherwise, it is too painful to check all the vandalized sequences. There's [URL="http://www.google.com/search?q=suddenly+bananas+thousands+of+them"]thousands of them[/URL].

[quote=Batalov;202648]It would be nice to run a mysql procedure on [I]all[/I] current number objects, and if they are even (except 2, of course), drop the prime flag. If they are stored wordwise, that would be easy to code looking just at the last limb.

Otherwise, it is too painful to check all the vandalized sequences. There's [URL="http://www.google.com/search?q=suddenly+bananas+thousands+of+them"]thousands of them[/URL].[/quote]
Of course, if Syd can find out who did this, he could possibly look up all numbers flagged as prime by that user in the database (assuming it actually records that), and drop it for those, thus forcing them to be retested automatically as per the normal process. That way, we could be sure to get all of them, not just the even ones.