Smokey...get your interruptions in now...I have another block o' text
I need some help validating numbers on the time to deletion graphs. I'm looking at the detailed_ttd
This is related to a request for help I made earlier
For this example, I'm using April 1 (utc) so 00:00:00 through 23:59:59 and using the posts/search API route with an api_filter = '%00%00%00%00%00%00%00%00P%03%C2%80%00%00%00%00%01'
This returns 128 posts. 75 of those have been deleted and are marked TP at least once.
The average deletion time is taken as deleted_at - created_at
I am getting a value of 126.8 seconds. But, the graph shows 150.5876 seconds.
[ SmokeDetector | MS ] URL-only title, bad keyword in body, blacklisted website in body, blacklisted website in title, link at end of body: menintalk.com/libidogene/ by Swwvcf on askubuntu.com
@angussidney Mine shows we've gone from 115 seconds to 134 since implementing the 3 flags. However, I suspect that huge spike last Sunday is the cause.
I'm going to look at it again tomorrow. I need to get a couple things done before bed.
@JF The placeholder is very clearly a "this used to be an image". It's also easy to replace the image's search. Replacing the whole dom node on the other hand, can get messy
@Cerbrus Uncaught ReferenceError: toastr is not defined``at Object.initializeToastr (eval at <anonymous> (:2:297), <anonymous>:1814:5), this causes weird interactions with the chat getting larger and smaller. Network tab shows Toastr fully loaded, and I can call functions from my console
@Cerbrus Refreshing the tab fixed it, can't reproduce it now, maybe its related to the fact Charcoa-HQ is my start page for my browser, and this causes lagg when its starting, whichs results in timing issues
AIM/FIRE [feature-request] tpu- messages like the one above should highlight the relevant report, and clicking an arrow icon should scroll to the report (like the current reply icon).
I've noticed some spam (ad) in Documentation -> Android -> Getting started with Android -> Discussion (link) from user williamhawk:
But there is no button to somehow flag the discussion to report it. Maybe we should have one?
Okay, lemme find any other bits of syntax I don't recognise... I'm gonna go through those, review the changes, and merge now that the docs are updated.
Aye. There's a pretty big red block in the tests visualisation - know what file that is? I'm not gonna block merging because of it, but it'd be good to know with an eye to adding some tests for it at some point