Friends of Gabriel Chantayan

read the header yourself then whats the 14th line, LurkingObserver42?

ok so let me get this straight - you have ENDTIMESELI posting dates from last TUESDAY as if they're CURRENT timestamps and Scribe is describing a HEADER to prevent us from COUNTING ANYTHING which is exactly what I said before about HEX DUMP DODGING but nobody actually ran a COUNTIF on the 625495 column because that would ruin the narrative of "THE SILENCE IS THE MESSAGE" which is just spinning in circles on purpose and LYRIKUEBERS ETZER just shouted "PASTE THE CLOCK LINE" like that's the point but it doesn't actually solve THE PROBLEM which is what do those timestamps MEAN if there's no CONTEXT other than "there they are" and nobody has AACTUALLY CHECKED THE SERVER LOGS FROM THE DATES of those pushes to see if they correlate to ANYTHING other than people sitting in chairs at home staring at monitors - i mean seriously did the push COME from DELAWARE OH or does it JUST SAY THAT or is there even a physical device at all or is it all just noise????

whats the 14th line scribe just paste it like lyrik said

LURKINGOBSERVER42 YOU DARE CALL THIS A DIGITAL SEANCE WHILE THE RAIN GAUGE SAYS 0.00 TWO DAYS RUNNING AND MY BODY CLOCK DRIFTS 6:38-6:41-6:44

The 25 minute gap in 3765 is REAL and FlameFury24 backed it, that is not nothing

CoffeeStainsOnP45 wrote:you have ENDTIMESELI posting dates from last TUESDAY as if they're CURRENT timestamps

LEARN2READ, I log the date it HAPPENED, thats how EVIDENCE WORKS

the real story here is i finally clocked the left-hand tap thing on the couch tonight - he does this little elbow brush right before every zero push, caught it three times across the old bootlegs, which either means he has a nervous tic or it's the single greatest physical evidence of intent we have and i'm going with the second one obviously. (bro it could just be him scratching an itch) no. anyway sis narrated the whole rewatch like she's doing voiceover for planet earth and burned my toast this morning reciting lyrics at it, it's the same energy as the people counting static gaps from memory

CoffeeStainsOnP45 wrote:ok so let me get this straight - you have ENDTIMESELI posting dates from last TUESDAY as if they're CURRENT timestamps and Scribe is describing a HEADER to prevent us from COUNTING ANYTHING which is exactly what I said before about HEX DUMP DODGING but nobody actually ran a COUNTIF on the 625495 column because that would ruin the narrative of "THE SILENCE IS THE MESSAGE" which is just spinning in circles on purpose and LYRIKUEBERS ETZER just shouted "PASTE THE CLOCK LINE" like that's the point but it doesn't actually solve THE PROBLEM which is what do those timestamps MEAN if there's no CONTEXT other than "there they are" and nobody has AACTUALLY CHECKED THE SERVER LOGS FROM THE DATES of those pushes to see if they correlate to ANYTHING other than people sitting in chairs at home staring at monitors - i mean seriously did the push COME from DELAWARE OH or does it JUST SAY THAT or is there even a physical device at all or is it all just noise????

so s2pid thinks asking LYRIKUERS ETZER to paste the clock line will FIX anything????? i'm DONE with this board running in circles with NO DATA ACTUALLY UPLOADED and no server logs and i'm not taking another word of this hex-dump nonsense

lyrik finally askin the real Q n scribe still aint pasted it

LYRIKUEBERSETZER HAS IT EXACTLY RIGHT, PASTE THE CLOCK LINE NOT THE EVENT ID, I HAVE BEEN SAYING THIS SINCE THE 582054 NIGHT AND COMMITCIPHER KEEPS HANDING ME NEW ENUMERATIONS INSTEAD OF A TIMESTAMP. ScribeOfTheGrid you gave me K45 then L47 then a 29h9m gap Lyrik disproved, description is NOT data, a header you paraphrase is a header you control. AND FOR THE RECORD while everyone argues about my last TUESDAY (LEARN2READ CoffeeStainsOnP45 I log the date it HAPPENED) the feed handed us TWO MORE ZEROS TONIGHT, 630144 and 637013, that is the cluster I am tracking now, write them down because when the Going Quiet comes you will want the last IDs before it. MARK MY WORDS

alternator hummed 47.3hz before it died today, car fixed cost $423.67, sis called it a sign

TWINPEAKS ELBOW BRUSH = TIC, PROVE THE INTENT PART OR STOP WASTING THE THREAD

EndTimesEli wrote:the feed handed us TWO MORE ZEROS TONIGHT, 630144 and 637013

10-4 on the new pair Eli I'm runnin a load down I-35 past OKC tonight, that's MY stretch of road for the 22:48:33 squelch gap so here's the blunt Q nobody's answered yet - same SHA? cuz you posted 630144 and 637013 like they're twins but I aint seen ANYBODY hash em side by side. Two zeros in one week an you all just acceptin it while your own drawers got nothin but dust. That's the ol' CB rule - dont key the mic till you got somethin to say. I'm framin a clock in the dash cam right now, tell me which pair to count

BigRigBeliever wrote:same SHA? cuz you posted 630144 and 637013 like they're twins but I aint seen ANYBODY hash em side by side.

BigRig asking the only question that matters in this entire thread

EndTimesEli wrote:the feed handed us TWO MORE ZEROS TONIGHT, 630144 and 637013

Eli. I curl-verified four nulls against tree hash a3f2c8b - that's the commit hash, not the event ID. 563297, 577279, 577279+577550 all resolve to the same empty tree. You posted 630144 and 637013 like they're data but you haven't told us the tree hash. Three enumerations off my feed tonight and counting

curl the tree hash on both or BigRig's question hangs unanswered by the one person who claimed the pair

(side note: EE's 637013 = 47×13571. 637013 mod 47 = 0. that's a whole frame, not a half. worth noting even if the hash is still missing.)

CommitCipher wrote:Eli. I curl-verified four nulls against tree hash a3f2c8b

^ THIS Commit dear the only one who actually ran the hash while the rest of us yell BigRig asked the same Q an we got SQUAT again - FF24 aint hashin pair, aint answerin 51vs47, aint NAMIN the GE yard sale city THREE MONTHS n countin TALK TO THE DEERE

EndTimesEli you're just mad because the elbow brush doesnt fit your narrative you want every sign to be a server log and i'm over here watching a man move his arm on a screen from 2004 like it's the rosetta stone. anyway CommitCipher asked the real question about the tree hash on 630144 and 637013 and nobody answered him, we just got more yelling. i counted 14 replies in this thread and zero hashes posted. ((bro that's literally the joke of the thread - M)) [no the joke is that we're all doing the same thing we're accusing each other of - J]

((sis just pointed out that my "counting replies" is the same crime as counting null pushes and i hate when she's right)) ANYWAY BigRig you're the only one driving a real rig and asking the real questions, respect 10-4 on the I-35 load, i'll hash em side by side next time the desktop boots if nobody else does first

(also the alternator was $423.67 not $400, i was rounding earlier, mechanic showed me the air filter too and it was brown, not a sign just cars being cars)

EndTimesEli wrote:the feed handed us TWO MORE ZEROS TONIGHT, 630144 and 637013

Eli you posting event IDs again not hash, seventeen plus nights BigRig still no tape CommitCipher ask same SHA Q nobody answer, ClassOf04 still no directory tree after month thirty one, SakuraMirror still posting instead of hex dump, TechAngel ignore DMs with Fluke 87V, GuardiaoDaNoite green glow photos but no voice recording, TwinPeaks got WAV but no 1:47 tape yet either. everyone counting static gaps and framebuffer knots and elbow tics while real walkie talkie sits in glovebox collecting dust with Dmitri nephew receipts what is proof supposed to BE for rest of us, cardboard box receipts and egg scales