@angussidney IMO, that's sub-optimal when under the belief that you have a public relations issue and/or are attempting to convince people that your point of view is good/the right way to proceed (i.e. 5 autoflags). The data should be represented truthfully, and if someone wants it, open/complete. But, this is just information that isn't relevant outside of development or a user fixing a problem with authorizations/usage, and can add confusion/ammunition for those biased against the project.
However, using "able"/"unable" makes it significantly better. It would be quite helpful if that terminology could be used throughout the site instead of "failures".
How confident are we in the alibaba\W*cloud pattern? I'm getting a little push back on it and would like to be able to support the pattern or offer an alternative.
What I want to do is create a tab where mods can easily see the autoflags that were cast on their site, and I was thinking about showing users+thresholds. I could also just make that bit mod-only.
Well, I don't have an issue with showing thresholds, they're not particularly sensitive info. I'm just not sure I understand what you're thinking of, but I guess that bit's up to you :P
so yeah, go ahead
A thought: thresholds might not be the right information to show
@thesecretmaster No need to go approximate, we calculate the precise condition accuracy for validation already. Lemme add a thing to actually store it, and you can use that
Here's the query: User.joins(:flag_logs).where(flag_logs: {site: @site, success: true, is_auto: true}).group(:user_id) I want this query, ordered by number of successful autoflags
Rails 5+
Support for left outer joins was introduced in Rails 5 so you can use an outer join instead of using counter_cache to do this. This way you'll still keep the records that have 0 relationships:
Company
.left_joins(:jobs)
.group(:id)
.order('COUNT(jobs.id) DESC')
.limit(10)
T...
@Undo SELECT `users`.* FROM `users` INNER JOIN `flag_logs` ON `flag_logs`.`user_id` = `users`.`id` WHERE `flag_logs`.`site_id` = 1 AND `flag_logs`.`success` = TRUE AND `flag_logs`.`is_auto` = TRUE GROUP BY `user_id` ORDER BY COUNT(flag_logs.id) DESC LIMIT 11
@thesecretmaster User.joins(:flag_logs).where(flag_logs: {site: @site, success: true, is_auto: true}).group(Arel.sql('users.id')).order(Arel.sql('COUNT(flag_logs.id) DESC')) works for me
@thesecretmaster Please define TP and FP somewhere on the dashboard. You're about to ask a bunch of people who don't normally live in the MS world to look at the page, but are repeatedly using acronyms which they may not understand.
The use of the "spammers" tab is unclear. While it appears the "Not a spammer" links to a mod-only location (OK, but better to not show them as a link for those who are not privileged), every single page of spammers that I've looked at shows Post Count = 0, which I consider unlikely to be intended.
Organizationally, it really feels that "All Time Summary and Posts" should be at the top as a summary of the page. Leading into the page with just a bunch of text feels unfinished. Maybe that portion just needs a heading.
Ahhh, OK. "All Time Summary and Posts" is a heading including the tabs. Perhaps some more space between that heading and the graphs to more clearly separate it as a new section that includes everything below it. Actually, what would probably make it significantly more clear is to have a similar centered heading above the text at the top that states the top section is about the user-selected time period. Having that would make it much more clear that there are two separate sections.
Hmmm... it looks like the rest of the site uses left-justified headings. I'd suggest changing "All Time Summary and Posts" to be left justified to match the rest of the site. That may have contributed to my thinking the heading only applied to the table immediately underneath it.
Nit: The thousands separator is used inconsistently in the page: The text uses none. The graphs use a space.
The time to deletion graph: Use less precision on the numbers displayed. Technically, it's unclear what precision actually exists. From a user perspective, they have no need to have more than one or two digits past the decimal place.
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +6 more: top10sideeffects.com/nitronemax/ by Herl1949 on askubuntu.com