Comment by therealadyjewel on 02/03/2021 at 19:43 UTC

30 upvotes, 1 direct replies (showing 1)

View submission: Crowd Control and Other Safety Updates

View parent comment

The data processing for "should a comment be flagged by Crowd Control" happens server-side. The client-side impact is time spent waiting for the comments page or "more comments" to load.

Earlier implementations did a lot of processing at run time, so it was slow and heavy on the site's databases. As time has passed, we improved the Crowd Control system to pre-calculate the results, save for later, update as appropriate (e.g. if a moderator marks a comment as "uncollapse for Crowd Control"). These days, pretty much all the "Crowd control examines a comment and context" work is "look at the pre-calculated saved data".

cc u/deviantbono u/Meepster23

Replies

Comment by Meepster23 at 02/03/2021 at 19:45 UTC

16 upvotes, 0 direct replies

So whats up with all the javascript bloat then storing a million reasons for why something was crowd controlled? I haven't seen any reasons for a comment being crowd controlled displayed, is that coming in the future or something?