It would be a very long list and content because there are so many DT members on this forum.
If you would like to go with it, where will you publish and store such updates?
I personally don't think the list is that long, though that may change during a particularly drama-heavy period or when adding DT2 members into the fray.
During the past week there has only been 26 instances of Sent or Received feedback, including untrusted feedback they've received. I think that's extremely manageable for a forum post, but maybe I am being naïve.
I'm open to the idea of having my own website for projects like this, but I honestly think this list would be too small to start my entire own website/repository.
How do you handle added or removed DT-members?
Currently, I don't - I just made a static list of all of the current DT1 members based on the April update. DT1 only changes once a month, right? I'd like to automate the process of grabbing the DT members each time, but for the prototype I figured I'll just throw the DT1 members into a hard-coded list.
How about highlighting the DT-members without any sent feedback? Those users should probably not have been added to DT in the first place.
I meant no sent/received feedback during the time period that I am searching, which is during the month of April '22.
You asked for suggestions, so here it goes: use less words and more colors and links. So add a profile link to the username, don't show the userID. Don't mention "Positive" but make it Bold. Make negative feedback bold red, just like the forum does. Add the Reference link and feedback date.
Now it looks like a long list that I'm not going to read. To make this useful, it should quickly provide relevant information.
I sincerely do appreciate every suggestion, and I don't think any of that should be difficult to implement; Add a couple tags in a couple of places for readability; I designed it so that it would be "easy" on my eyes in a Console or plain-text, but since it would ultimately end up on the forum those are proper suggestions.
If you want to go wild, you could make this for DT3-members too. I've never really looked into those, but it might be useful to find members who deserve to be on DT2.
I definitely could expand this out to DT3 members, but if I'm going to do that I should definitely find a way to automate the list of users included. If I'm not mistaken, DT2 and DT3 are endlessly more dynamic/malleable than DT1.
Why make it weekly, and not daily? Much of the feedback drama doesn't even last a week. Since it's only about 1000 pages to download, doing it daily shouldn't be a problem (I scrape much more than that).
Very flexible on the time-interval between updates, but weekly seemed to be the most reasonable interval. Daily updates would see multiple days without any activity, but that of course is my analysis based on the DT1 group of users.
I'm missing the most interesting thing: deleted feedback! Those are much harder to find without remembering every feedback ever received. If you can automate that, it can become a valuable resource for keeping track of who did what when.
Deleted feedback would be a lot more difficult to pull off, but I can definitely start poking my nose in that direction when I get some time. The voting for this isn't going too great so far, and there's no sense in developing something the community doesn't want, so maybe it'll just wind up being a personal tool that I use.
It's not in the drop down menu, but I assume you can use any (hex) color.
