If you'd be on DT2, the difference could be changed because I use
https://bitcointalk.org/index.php?action=trust;dtview for DT1 inclusions/exclusions and
https://bitcointalk.org/index.php?action=trust for DT2. The former is updated real-time, while I think the latter has a delay (although I'm not sure, some Trust changes are real-time, others are cached for a while by the forum).
However:
Why would you expect it to change? Me being on DT1 or not has no effect on whether you are.
Foxpup is correct! If you'd be on DT2, Foxpup's exclusion would matter depending on Foxpup being on DT1 or not. But you're on DT1, and inclusions or exclusions from users with net-exclusions on DT1 still count.
This leads to the following (probably unintentional) possibility:
Lauda had (2) net-inclusions on DT1.
Lauda now has 6 net-inclusions on DT2.
Lauda got blacklisted from DT1.
I have 2 scenarios
1: suppose Lauda wasn't blacklisted, but got 3 more exclusions from other DT1 members. That would mean Lauda was removed from DefaultTrust entirely.
2: the current state (Lauda blacklisted from DT1). Now suppose Lauda gets the same 3 exclusions from DT1. That would mean Lauda still has 3 net-inclusions on DT2 and remains on DefaultTrust.
This means it is possible that a DT1-exclusion leads to a member being on DT which wouldn't happen without blacklisting. This is probably caused by the fact that excluded DT1-members can vote against other DT1-members, but they can't vote against DT2-members.
Is that the intended behaviour of the DefaultTrust system?
Given Lauda sunk below DT2 on Thursday your time
http://islaudastillondt.tk/ , how come this still shows negative in yellow in the trust feedback ??
I can't scrape all data at the same time, I usually update the Trust scores (currently 13,755 entries) on Wednesday.
(there is no conspiracy)
~
(there is no conspiracy)
Correct. I don't do conspiracies. Only bugs
2020-03-11_Wed_16.29h: Lauda is on DT2 with 0 inclusions.
2020-03-05_Thu_10.49h: Lauda is on DT2 with 0 inclusions.
2020-03-04_Wed_10.49h: Lauda is on DT2 with 0 inclusions.
This is caused by a scraping failure. I didn't account for it, so it gives unexpected behaviour.
I've manually removed the 2 incorrect entries for the 4 affected users.