ArtOfCode
ArtOfCode
This is probably the same old JS bug that's existed forever, probably related to Turbolinks
Final decision will be @teward's, but I doubt we're going to be able to run stuff on a second box - we're already heavy on hardware as it is.
"Good luck" is all I can say...
cc @Undo1 on restoring 32346. I'll look at making AS tags more pliable - they were originally meant as a system-only thing, so preventing users deleting them was by-design, but...
I'm... not even sure if this is possible. @Undo1, happen to know if you can terminate a Rails request manually?
Needs some console poking from @Undo1 - prod log doesn't show anything, because the error gets caught.
This is just a function of the lifecycle of objects in the MS database. Websocket messages are sent based on certain events, but they can't necessarily be taken to mean...
*Maybe* [status-bydesign], it's done by % certainty not by weight. Need to look into it in more detail, might have some time this week.
[This is the scatter plot of weight/flag count.](https://metasmoke.erwaysoftware.com/data/sql/queries/166-weight-flag-count-scatter-plot). There certainly _are_ instances of 4-flag posts in the 1000+ range, but they do seem less common than I'd expect.
and [this](https://metasmoke.erwaysoftware.com/data/sql/queries/167-high-weight-posts-without-4-autoflags) is the list of instances of 1000+ weight posts without 4 autoflags on them - 297 instances.