The aggregator sites take a Q post, which are found and isolated by name (Q) and tripcode. If the Qpost refers backward to another post, the aggregator recognizes and isolates that previous one (or more) too.
Applying that algorithm to the three posts ...
Q post No.1762761 is the first post recognized by the aggregator algorithm. It refers to previous post No.1762748. Post No.1762748 is by an anon, as far as the aggregator knows. The name is not (Q), and the aggregator algorithm is not looking at UID. Post No.1762748 is of the Google Guest Pass, and is picked up by the aggregator algorithm.
Post No.1762748 refers to an earlier post (1762746).
The reason that Post No.1762746 is not picked up by the aggregator algorithm is that is is not referred to by a post that is "signed, 'Q'." Post 1762746 is referred to by a post that is signed "Anonymous."
-- Did that post get pulled or something or is my site just not picking it up? --
None of the posts is pulled. I screen shotted all three of them this morning to facilitate responding to your question, and explaining why the aggregator sites are missing this info.
The humans at 8ch.net recognize all of these posts as being by Q, and have them logged in "Q's latest posts"
I get it now. I think. Well at least better than I did. :)
Bagster
“...JC email
...GOOG guest badge
...Access kills”
Those three combined... Does this suggest that white hats have access to JC emails (by inference, all GOOG emails possibly including the shared email used for draft only com’s?), because white hats have access to GOOG data and that this access will kill DS ops?