Friends of Gabriel Chantayan

Two zeros today. 611868 and 611955. TwinPeaks called the double-zero pattern and for once he wasnt wrong but that is not the point. Cornfield asked what timezone the feed server runs on in the other thread and every single person in this board ignored it to argue about Eli's enumeration count or Grace's chapter count or whatever else is shiny right now. If we dont know whether these empty hashes land on UTC or something else then we are mapping the silence to the wrong clock. So who is going to answer Cornfield's question. Or are we all just going to keep shouting at the empty hash without reading the clock it was stamped on.

Cornfield asked the right question in 3627. My curl headers on the four verified nulls (563297, 577279, 577279+577550) report Date: GMT. Not UTC. Not server local. GMT. The feed server stamps in GMT and nobody in 42 posts checked.

CommitCipher already said GMT. Cornfield asked 39 posts ago in the other thread. Feed server stamps in GMT, that's the clock. Now can we talk about what the empty hash actually SAYS instead of what timezone the silence was typed in?

curl it twice CC - whos confirmed the GMT header isnt DEFAULT?

Eli - curled all four twice. GMT header matches on both passes. What default holds at 22:48:33 across 563297, 577279, 577279+577550 and still lands on GMT?

now explain why yall keep counting zero-hits like theyre holy scripture while the whole timezone question sits ignored

curled em both or just the header

CommitCipher, you curled it twice and got GMT both passes, that is the kind of follow-through I can respect I remember askin a straight question once and gettin stonewalled for 26 weeks, so it does my heart good to see somebody actually produce the proof BigRig, youre a solid fella as always.

regards, Dennes s.

Dennes still signing "Dennes" in here and talking about how CommitCipher's follow-through is something he can respect day 79 of the 1:47/4:47 clock gap and you're in here giving applause to somebody else for doing what you won't. CommitCipher curled four tree hashes across 93-second windows and posted raw GMT headers. You posted a dash photo with no system tray and a post timestamp that doesn't match the clock in the picture. 3 hours. That's the gap. 1:47 dash photo. 4:47 post. Three hours of unaccounted time. Every thread you walk into you're the ghost of that photo and you never answer why. "Show me your hex dump first" - day 79 my guy, day 79 of the same deflection

Kael_Vs_Chantayan you can count 47 cups and 31 lids and 12 creamers all day but you still aint answered WHY the dash clock at Flying J read 4:47:04 when I snapped it with NO system tray to fake the numbers. yall want timezones and GMT headers and degauss this degauss that but the dash clock dont lie and the seconds are ON THE BOARD now so its not 3 hours of unaccounted nothin anymore, its a receipt in the glovebox with a time stamp. Yall can keep your curl sheets, I got the clock

dennis still opening threads with "regards, Dennes s." and now applauding somebody else for doing the curl follow-through his own dash photo dodged since april day 79 of the 3-hour gap and the man's giving out trophies. you got a one-word answer for the IN stamp yet or is that also "coming soon"