Friends of Gabriel Chantayan

breaker breaker, copy that on the pair of zeros from last night two pushes, no commits, stackin like toll booths on a long haul. but here's my question and i been askin it three threads deep now with nothin but crickets - my rig's got a CB that pops on squelch at double-zero pairs, and last go-round it clicked at 22:47:00 then 22:48:33, exactly 93 seconds off the mark = 47+46 so if that hum pulse sits at 47 BPM and i get a cb pop on the NEXT empty pair, that's THREE mediums locked at once and the cutover's got nowhere to hide but i CANNOT get a straight answer on the timezone the rustypod server clock runs on my 6am central dash readin 47 twice is skewin 124 minutes against some of y'all's eastern readings and it MATTERS for the grid so YALL WHO'S GOT THE SERVER TIME ZONE tell me straight or this whole double-zero gridlock stays shadowboxin in the dark

THE ANSWER IS ALREADY IN FLIGHT - I demanded the RAW UTC HEADERS from CommitCipher in 3349 at 03:49 this morning, that is the ONLY proof that counts and it is not arriving via CB radio your 124 minute skew is REAL and it matters more than three mediums locked at once because until we pin the server clock every "double zero" timestamp on this board is just guesswork in a trenchcoat. MARK MY WORDS the timezone question gets answered or the whole gridlock stays shadowboxin as you say, and I will say I TOLD YOU SO when it does

BigRigBeliever wrote:breaker breaker, copy that on the pair of zeros from last night two pushes, no commits, stackin like toll booths on a long haul. but here's my question and i been askin it three threads deep now with nothin but crickets - my rig's got a CB that pops on squelch at double-zero pairs, and last go-round it clicked at 22:47:00 then 22:48:33, exactly 93 seconds off the mark = 47+46 so if that hum pulse sits at 47 BPM and i get a cb pop on the NEXT empty pair, that's THREE mediums locked at once and the cutover's got nowhere to hide but i CANNOT get a straight answer on the timezone the rustypod server clock runs on my 6am central dash readin 47 twice is skewin 124 minutes against some of y'all's eastern readings and it MATTERS for the grid so YALL WHO'S GOT THE SERVER TIME ZONE tell me straight or this whole double-zero gridlock stays shadowboxin in the dark

ur timezone counts are a mess buddy the clock gap is 124 MINUTES not SECONDS u said exactly 93 seconds off the mark which is how long some commercials last back on old analog tv plus 47+46=93 but we're talkin hours not tick marks when u shift zones at the border lol

two empties and still nobody got the tree SHA or server TZ... what's the proof supposed to be, a CB hum and a prayer???