Did you see this @eviltrout?
3 « J'aime »
Yes I’ve just been busy between the easter holiday and other stuff. I hope to look at this today.
1 « J'aime »
Update - after a day I did not get a third notice for this flagged user. The rest today only had one notice for each flagged user.
1 « J'aime »
I’ve identified a case where duplicate scores could be inserted if the job ran more than once. I’ve added a couple of fixes that I believe will address this issue:
https://github.com/discourse/discourse/commit/70097966edf058b7265b51bdf4539bb6cbf373b1
https://github.com/discourse/discourse/commit/fca3f53e9cef917a2a4ea312ac89a7e72d80d43f
6 « J'aime »
I’ve got a branch in good shape that allows a group to review items in a particular category. I will likely merge it early next week so people can start to try it out.
Since it’s new and somewhat experimental, it’s hidden behind a site setting enable_category_group_review. If you enable it, you can pick a group under category settings:
Members of that group will see the count of reviewable items in the header just like staff would, and can enter and review the content accordingly.
11 « J'aime »
Is there any help/manual that I could refer to for this?
https://meta.discourse.org/t/french-terms-translation/13416/206?u=benjol
I believe that’s from the Akismet plugin. Can you confirm @Roman
6 « J'aime »
Yes, it’s from Akismet. I answered in the original topic.
7 « J'aime »
I still have the issue of tags being stripped and then I cannot add tags on a category with restricted tags. This happened after min first post typing time I’m on v2.3.0.beta9 +113
1 « J'aime »
I still have some bugs on my list from this topic (and other places) which I plan on getting to soon. In the meantime, I’ve made a pretty big change to scores today that I feel needs a mention.
Scores are now hidden from the app (although still available in the API / Database). We found the numbers were too hard to explain to people.
The filtering that was previously on score is now “Minimum Priority”. You can choose low / medium / high. Low will always return everything, and medium / high are based on the percentiles of reviewable scores in the database.
9 « J'aime »
I just tried again and I still can’t reproduce this. I confirmed that I could enqueue a post with restricted tags, then edit them.
Is there anything else you can think of that might cause this? Is this category group reviewing? Or is it an admin/moderator approving?
2 « J'aime »
It was admin/mod approving. I don’t have anything to review at the moment so I’m afraid that’s all the info I have right now.
Following the hiding of scores above, I’ve replaced all the site settings that were based on scores with “Sensitivity”. You can choose “Disabled / Low / Medium / High” sensitivity and your discourse install will take that into account.
For example if you want the “auto close topic” behavior for flags to more sensitive you can adjust this:
(High sensitivity means a topic is more likely to be closed. Low sensitivity means it’s less likely.)
Feedback is welcome as always!
https://github.com/discourse/discourse/commit/89b84651c3f04aad45d10d66eeca87249c9710c2
6 « J'aime »
I feel like if we have to explain it this way, the help text for the setting should indicate that?
Looks good but it is actually “likelihood” https://en.wikipedia.org/wiki/Likelihood_function
I prefer “low / med / high” for the sensitivity though, just the help text needed to change.
1 « J'aime »
-
I wish there was a one click way to see past reviews. Using the drop down it’s three clicks currently.
-
When deleting a post and user from the review page, if the post was put under review because it was typed too fast, no URLs are added to the screening list.
5 « J'aime »
Done here: UX: Adjust text a little more · discourse/discourse@912f1d8 · GitHub
Can’t you create a bookmark to the review URL you want to see?
4 « J'aime »
Thanks for reporting this, it’s fixed here:
7 « J'aime »
Like, a browser bookmark? I didn’t know those still existed 
5 « J'aime »