How to remove negged of DTs that left the forum?

[Crypto-DesignService]

https://bitcointalk.org/index.php?topic=2112587.0

What is your judgement about this?
Account recovered after a year but user KWH who tagged the account to warn others leave the forum permanently, now the account has been painted red with no possible way of removing the tagged KWH left.

My idea though It might be very time consuming.
Exclude KWH from DT, re-tagged those accounts(possibly became neutral) that KWH left feedback for breaking the rules.

[qwertyup23]

From the looks of it, the red tag has been removed from the account.

<...>

Not really. The account we should be looking at is the original one, and not the one used to try to get the account back.
The original one is: https://bitcointalk.org/index.php?action=trust;u=326379.

*EDITED
Just saw the post underneath. Thank you for clarifying my misinformation. Will be more careful next time!

[DdmrDdmr]

<...>

Not really. The account we should be looking at is the original one, and not the one used to try to get the account back.
The original one is: https://bitcointalk.org/index.php?action=trust;u=326379.

@Coinlocket$ has countered the negative feedback, but of course the rating algorithm is not that easy to counter even if one wanted to (more weight on negatives, more weight on older feedback, and so on).
  

[Quickseller]

If it is believed someone is not coming back, and there are enough of these types of ratings, the best course of action is to remove the person from the DT network.

[r1s2g3]

Solution is simple, Make DT2 criteria same as DT1, if you are not active in last 3 days and have not posted anything in last 30 days then you cannot be eligible for any type of DT list (DT1 to DT4). Only user who are directly trusting by their custom trust list  will see their feedback as trusted, for others it become untrusted feedback, no matter user is included by multiple DT1's.

[Jet Cash]

I gave you a positive as well with a reference to this thread.

Perhaps someone could let me know if I need to remove this.

[Crypto-DesignService]

Solution is simple, Make DT2 criteria same as DT1, if you are not active in last 3 days and have not posted anything in last 30 days then you cannot be eligible for any type of DT list (DT1 to DT4). Only user who are directly trusting by their custom trust list  will see their feedback as trusted, for others it become untrusted feedback, no matter user is included by multiple DT1's.

Problem with your suggestion.
DT2(200~) has a wider network of users compared to DT1(56). There is a higher chance DT2 users will eventually go inactive and if you remove them from DT with the criteria as DT1, the trust rating they've given to people might turn to untrusted and will make some users' negative to neutral accounts.

[LoyceV]

KWH has many valid tags, so it would be nice if he can stay on DT2. Since his absence has been proven through a signed message, and the recovery went through the forum , maybe Admin can remove the red trust?
Or as a more permanent solution: would it be possible to give the account recovery team the permissions to remove this for similar cases?

[Findingnemo]

Solution is simple, Make DT2 criteria same as DT1, if you are not active in last 3 days and have not posted anything in last 30 days then you cannot be eligible for any type of DT list (DT1 to DT4). Only user who are directly trusting by their custom trust list  will see their feedback as trusted, for others it become untrusted feedback, no matter user is included by multiple DT1's.

This can be a good solution to remove the inactive members from DT network,but I think most of the time there won't be any need for removing the negative trust so if someone negged wrongly they can be countered by other DTs to prove the innocence.

[Crypto-DesignService]

KWH has many valid tags, so it would be nice if he can stay on DT2. Since his absence has been proven through a signed message, and the recovery went through the forum , maybe Admin can remove the red trust?
Or as a more permanent solution: would it be possible to give the account recovery team the permissions to remove this for similar cases?

If admins/recovery team has that power I will take this option too as this seems to be the best and hassle-free.