To improve DT2 selection,
the topic from DireWolfM14 and his pool suggestion is so far the best discussion I consider.
My personal suggestion is to make wider margin. Net inclusion 2 is better than 1, 3 is better than 2 and so on.
#3I will periodically (maybe every month) be reconstructing the default trust list to include everyone who matches these criteria:
- If rank was determined solely using earned merit, then you must be of at least Member rank.
- You must have been online sometime within the last 3 days.
- Your trust list must include at least 10 users, not including ~distrust entries.
- You must not be banned or manually blacklisted from selection.
- You must have posted sometime within the last 30 days.
- You must have at least 10 people directly trusting you each with an earned merit of at least 10, not including merit you yourself sent. These "votes" are
limited.
- You must have at least 2 people directly trusting you with an earned merit of at least 250, not including merit you yourself sent. These "votes" are
limited.
I plan to instead choose a random subset of about 100 eligible users each time.
In current DT system these random subset of 100 eligible users become the DT1.
My proposal is to
add another layer with the current DT system for DT1
Election which is to allow these 100 eligible users to
update their trust setting every month.
So the random selection makes the users
eligible for DT1 but each of them
are not DT1 until they do not update their own trust list with the selected remaining 99 users. One must add or tilde (~) others in their trust setting to become DT1 for the remaining days until the next random subset selection.
The current DT1 system became a lazy achievement for some, some are easily manipulating it, some do not involve because they do not either add or tilde (~) a user to avoid DT drama. If someone wants to be in the DT1 network then
let them fully involved.
I do not know how hard it will be to reprogram but I wanted the work for Theymos as less as possible.
Choosing random subset of 100 users are already done but instead of making them DT1 from the selection write a set of code that will check if the individual user added/tilded(~) remaining 99 users.
Current user cu = logged in user;
Array cua = Current user's trust list;
Save the random subset in an array rsa (random subset array);
Have another array dta (defaultTrust array) to store DT1 users;
Check cua have everyone from rsa excluding himself
YES, cu will be added to dta;
return dta;
A loop will be needed but depending on the programming skill the loop can be optimized (mainly in array processing) for the code to take less resources.
Instead of running it on onLoad of the index page you can set a corn job which will execute after every x hours or x day.
The benefits:
Elect only users who have strong desire to be in the DT1 list.
Since it requires a must vote for all selected users, no elected DT1 user can stay in the border line where they skip it by not adding or tildeding(~) others.
Every month after the selection, users will need to add/tilde(~) new selected users to their trust list again, this eliminates lazy DT1.
Since elected to be in DT1 become harder it should eliminate easy manipulation.
The disadvantages:
Selected users will need to update their trust setting every month to be elected for DT1
It could create more drama since no one can stay in the border line. You tilded user A, be ready to be tilded by user A.
May use additional resources from the hosting if it allows to run in onLoad of the index page.
Update: Considering response from users so far, a proposal to reduce difficulty.
https://bitcointalk.org/index.php?topic=5409697.msg60748710#msg60748710
