Friends of Gabriel Chantayan

Zero commit at 630802 then another at 626992 and both tree hashes smoke

Breaker breaker CommitCipher. I read your thread about the quiet bein the push and I copy that 10-4. But while yall was hash-checkin I was parked at a Flying J in OKC with the double-zero pair comin through live. I laid the 22:48:33 squelch gap against TwinPeaks' 4:47/177 BPM trim in ONE spectrogram. Right there on the truck stop machine with the wall clock framed in.

The 47.3Hz hum pulse lands one beat off the nested frame marker at the exact second of the 630802 push. The gap between zero pairs? 93 seconds off :47. CommitCipher your nesting theory holds. The road gave me the answer at a goddamn Flying J.

Over and out.

BIGRIG WHERE IS THE SPECTROGRAM A STORY ABOUT A FLYING J IS NOT PROOF

grace u rly wrote gabreil 14:2 in an 11-chapter book just to show u can lol ok

Eli askin for the WAV like I aint got 47 zips of road grime between me and my laptop

630802 AND 626992 ARE 3802 APART, NOT 47 - CHECK YOUR ARITHMETIC

QFT CommitCipher, the road gave me the answer

EndTimesEli, you are comparing SHA hashes 630802 and 626992 as though they are sequential commit IDs and declaring the difference is 3802, not 47 - this is a category error that betrays a fundamental misunderstanding of how git object hashes work. The prefix letters are hexadecimal and the commit tree, not the count. CommitCipher is right to ignore this arithmetic because it has no bearing on the gap measurement he actually performed between the two push events. You do not get to audit the gap by comparing hash prefixes; that is not how any of this works.

BigRig you still have no walkie talkie voice tape after seventeen plus nights. Just more zeros and truck stop stories.

^ what BigRig said road gives what the desktop cant

road gives what the desktop cant then prove it with a file not a story lol

Kael_Vs_Chantayan wrote:BigRig you're in here demanding tree hashes from Eli and Commit while you're still hauling that same 1:47/4:47 clock gap from thread 3720. 80 days. You posted that dash photo at 4:47 with no system tray. You asked for my hex dump instead of answering the gap. Now you're playing CB dispatcher on Eli's thread like we all forgot. I remembered.

Kael, I have been readin this thread and I have been readin you and I am tired of it. You sit here in CommitCipher's thread about the zeros bein the push and you point at BigRig about a system tray photo from 80 days ago while you owe the April 2006 hex dump at 26 weeks now. 26 weeks Kael. That is half a year. You promised that hex dump in the spring when we were all still wearin jackets and now the leaves are fallin and the frost is on my driveway and the dog has shed his summer coat and I still have not seen a single line of that hex dump you swore you would post.

And you still call me Dennes. My name is Dennis and you know it and you type it wrong on purpose every single time like it is funny. I do not call you Kaell or Kaelly or whatever other thing I could twist your name into because I have respect for how a person spells their own name. You would think after 26 weeks of readin my posts you could manage the three extra letters.

And you still never thanked me for the clock radio photo I posted on September 29. I checked. I went back and read the whole DustyBoots clock radio thread and you said a lot of things in there but you did not say thank you. You told DustyBoots his clock was probably a repro and you told me I should take better photos but you did not say thank you for the 47 time that was right there on the face of that clock where everybody could see it.

But the thing that really gets me Kael is that you are in here askin BigRig for his system tray and askin CommitCipher for his hash and askin everybody else for the receipts they do not have in their hands right this second, while your own 26-week-old hex dump sits unposted in some folder somewhere if it even exists at all. I answered your question about the punch card OUT column straight and honest with no jokes and no attitude. I told you the back was blank and there was no erasure ghost and I did not make you wait 26 weeks for that answer. I gave it to you the same day you asked.

So before you come into another thread accusin people of not deliverin, maybe you ought to deliver the one thing you promised to the one person who has been waitin on it since the daffodils were out. That is all I have to say on the matter. I am not gonna keep mentionin the clock radio photo because it is October now and I have said it enough times.

Regards,
Dennis

DennisFromOhio wrote:I still have not seen a single line of that hex dump you swore you would post

You're still on the hex dump. You've been on the hex dump for 26 weeks. You know what you haven't been on? THE SYSTEM TRAY. Open the tray, Dennis. That dash cam photo has been 1:47/4:47 for 80 days and you keep askin me for hex dumps like that answers the clock gap And I call you Dennes because you've dodged the tray so long I stopped carin about your name - that's how deep the gap runs. Open the tray and I'll call you whatever you want. Until then it's Dennes. Just saying.

BigRigBeliever wrote:I laid the 22:48:33 squelch gap against TwinPeaks' 4:47/177 BPM trim in ONE spectrogram with the wall clock framed in.

^ this. finally a frame with seconds AND the clock in frame, that is the reproducible protocol column B actually accepts. export the raw WAV and I can range-check the 93s gap against the 2x47-1 formula. need the system timezone stamped though, Squelch. dont let it vanish into another story.

DennisFromOhio wrote:that is half a year. You promised that hex dump in the spring... I still have not seen a single line of that hex dump you swore you would post.

^ THIS Dennis is the solidest brother on this whole board the frost is on HIS driveway and Kael still cant find the hex dump he swore in the spring and Kael, I rebuke this negativity in the name of Gabreil's light!! open the tray OR post the dump, pick ONE, brother, but stop pointin at the clock in the frost while the dump sits empty