The League of the Linen Coloured Balaclava-ed Gentlemen and Ladies

[Uncwilly]

I have queued (across several machines) or completed DC for all of the TF's listed in the post above.
They were going to be the holdouts for the milestone, as they had no expiry.

[S485122]

Originally Posted by Uncwilly

...
The numbers mentioned in the code of ethics will expire. There is little doubt of that.

I am not sure about that. There is a rule "Since PrimeNet began, the server has recycled exponents where the client computer is 60 days past due in updating the server. This rule has been fairly effective and will continue. However, there were cases where exponents were tied up for years without completing." That rule is not implemented : I looked at the "active" assignments in the 73M-100M range.

Of the 1111 exponents 625 are more than 365 days past due in updating the server. some hundred other assignments are between one year and 120 days overdue. I suppose that in the ranges above there are quite a few assignments overdue in updating the server.

It would clear things up and reduce the "need" for poaching if those assignments where expired (some show more than 6 year without progress.) They are obviously lost (for instance the user patgie has about 130 assignments without progress, and his current production is not what is was.)

Jacob

[Uncwilly]

If the current assignment and server rules were enforced, sure. But, enforcement now is spotty in many places.

[retina]

Originally Posted by S485122

So instead of setting up a group to for extra judicial "execution" ;-) I would suggest continuing to petition the people responsible asking them to enforce the rules, or, if that is not practical or desirable, the rules should be changed. But those people, whose volunteer work we all use, must find time to act : the change in proof method implies a lot of work on the scripts and the web pages, other things, like working for a living also impinge on their available time.

Agreed.

Originally Posted by S485122

Milestones are important, but are they that urgent ?

No.

I think the OP is being overly anxious and impatient.

[kriesel]

Consider the possible ethical case that could be made, especially by the very top producers, for preferentially poaching known deliberate poachers. https://www.imdb.com/title/tt0773262/
Vigilante action is not riskless.
Motivating someone with the throughput of Ben Delo or dmbeeson or a significant fraction, to script automatic fast poach of announced poaching might deter such poaching, or drive the poaching league to PM. Use your imagination for what countermoves might follow.

[Uncwilly]

Originally Posted by Uncwilly

It looks like Waldir Walter Junior might be using TF to hold on to low exponents to DC.

53893087	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893261	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893267	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893289	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893457	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893559	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893753	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53893883	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53894143	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53894249	TF				2020-10-11	2020-10-11	2020-11-30		Waldir Walter Junior
53965459	D		20		2020-07-14	2020-07-14	2020-12-31		Xebecer
53965507	D		20		2020-07-14	2020-07-14	2020-12-31		Xebecer
53965537	D		20		2020-07-14	2020-07-14	2020-12-31		Xebecer
53965603	D		20		2020-07-14	2020-07-14	2020-12-31		Xebecer

Originally Posted by Uncwilly

I have queued (across several machines) or completed DC for all of the TF's listed in the post above.
They were going to be the holdouts for the milestone, as they had no expiry.

Those TF's would have been the holdouts for the milestone. They are not listed in when one clicks through from https://www.mersenne.org/report_milestones/
I should have them all done by the end of the month. Taking care of them now will prevent multiple people from racing to finish them.

[ATH]

I'm going to "poach" 98631959, it was assigned on Nov 19th 2019 and it was Cat 4 back then: https://www.mersenne.org/thresholds/?dt=2019-11-19

So it has 360 days to be completed which ended tonight UTC, but it did not expire and now it it showing blank in the "Expire (days)" columns. It has only done 69.7% in 360 days.

[Uncwilly]

53910709 and 53961293 were assigned more than 10 months ago and will expire before their ETA. They are both assigned to Anon. I will work on them. I only have 1 of the TF numbers still being worked on.

[Uncwilly]

Originally Posted by Uncwilly

I have queued (across several machines) or completed DC for all of the TF's listed in the post above.
They were going to be the holdouts for the milestone, as they had no expiry.

They are all finished.

[Uncwilly]

Theses are sitting in the Cat 0 section of the FTC

100001329	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001347	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001357	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001399	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001689	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001809	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001903	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100001983	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100002011	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan
100002059	TF				2020-09-22	2020-09-22	2020-11-11		mohammadaminzareiyyan

[Uncwilly]

I have queued up the first 9 in this list:
https://www.mersenne.org/assignments...hk=1&exfirst=1
Specifically those noted in orange below.

54322589	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54322643	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54322651	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54322673	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54322787	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54325669	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54325717	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54325757	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54325801	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy
54325841	TF				2020-11-23	2020-11-23	2021-01-12		Armlinsoft Oy