Hell yeah man.

Agents appear to have mislead FNTV by suggesting this was part of a chase when in fact the homeowner stated that the individuals targeted were performing repairs on the roof.

My understanding is that it’s like a bin width issue like histograms. I’m guessing the time assigned to the *36 searches* is the middle of the bin and the bin includes searches that happened after the event. Bin width is likely multiple hours since google wouldn’t aggregate counts in minute scale.

Well handled my man 😁…thanks for the technical context…it’s a pain to dig this stuff up…the effort is appreciated.

Be nice if someone FINALLY brought up this fake Dugin account again. He's a dude in Brazil, many have pointed that out for a couple years now but afaik outlets like WAPO still haven't corrected their quotes of him as *actually* Dugin.

Yep 😁 😇

lol...O'Hanlon, P. Pretty sure someone found his Discord....

Yep, that’s the table I’m using to map actor/target to canonical. Saving to columns in rdf_triples just gets the lookup processing out of the way up front so I can try a few different graph build approaches without redoing lookups (time intensive in MATLAB👍) Your db structure is def great. 😁

re "moderation"...that does make sense. I've saved each of the db files locally so can build graphs mixing info from each. The only *time bottleneck* is adding columns (to rdf_triples) for canonical names of actors and targets. 75 min yesterday...today file prob 2.5 hr. Only gotta do it once tho.