Friends of Gabriel Chantayan

5. Fluke 87V firmware 1.8 (ElderProphet07's - at least it has a cal temp, but that is the bare minimum of data discipline, not a virtue)
4. Whatever GuardiaoDaNoite uses to read 0.00 at his desk (consistently wrong, consistently missing batteries)
3. ScribeOfTheGrid's spreadsheet columns (row 79 is empty and he knows it)
2. My Fluke 87V with the florentine wrench mod (I brought it to Euclid and it worked)
1. Whatever meter ClassOf04_Truther used to photograph his hoodie cuff (still uncalibrated, still blurry, still the same photo since April)

LyrikUebersetzer wrote:1. Whatever meter ClassOf04_Truther used to photograph his hoodie cuff (still uncalibrated, still blurry, still the same photo since April)

from an outsider's perspective, ranking firmware by "badness" is just another way to avoid admitting none of these readings mean anything without proper calibration protocols. also ScribeOfTheGrid isn't a meter so this list is fundamentally broken

I say unto you, that list omits the Fluke 87V firmware 1.7 which has the thermistor correction that 1.8 broke

LyrikUebersetzer calling my 2003 hoodie cuff photo "still uncalibrated, still blurry, still the same photo since April" when I have EXPLAINED the battery died and it was my SISTER'S old camera and she got it at CVS in SEP 2003 the EXIF firmware date shows 2004 because the camera sat in a drawer for a year before she gave it to me, that's how cameras WORK lyrik. the 47 threads per inch are RIGHT THERE in the weave grain and EuroTrash_Herr666 caught the REV_B padding at 0x4B which your precious Fluke 87V cant even see with the florentine wrench mod

also your list put ScribeOfTheGrid's spreadsheet as #3 but that thing has FOUR columns now dummkopf, not three, and row 45 is where the REAL data lives that he's been dodging since MAY. ask him about row 45 next time you're ranking things badly on purpose

I don't usually tell this part, but Gabriel once told me that people who rank things without understanding the evidence are like men shouting at a locked door... he said it real quiet, looking at his shoes... you probably dont believe me but its true

ClassOf04_Truther wrote:row 45 is where the REAL data lives that he's been dodging since MAY.

Class I respect your work on the cuff trust me but row 45 is off by one. the August 6 commit offset is at row 46, not 45. Scribe counted wrong and now you're repeating him. check the spreadsheet yourself top to bottom. dont want bad data getting passed around is all

Regards, Dennes

ClassOf04_Truther wrote:row 45 is where the REAL data lives that he's been dodging since MAY

Finally admits row 45 exists but still won't post a cell reference for column K. Point to any single cell, just one

row 79 is empty and he knows it

LyrikUebersetzer forgot #6 - whatever meter Kael_Vs_Chantayan uses to type "exif" in lowercase while dodging the april hex dump for the fourth month running that firmware version is called "still no timezone anchor answer from topic 305" and it ships with every post he's ever made

krova_pl wrote:row 79 is empty and he knows it

ScribeOfTheGrid still dodging column K like its a haunted house tour. ask him about row 45 next time youre ranking things badly on purpose

ClassOf04_Truther wrote:the EXIF firmware date shows 2004 because the camera sat in a drawer for a year before she gave it to me, that's how cameras WORK lyrik

And yet the firmware stamp on that CVS camera is dated MARCH 2005, not 2004 I already posted the hex breakdown in topic 418. A camera sitting in a drawer does not update its own firmware date to a year it hadn't reached yet. Even if we accept your sister's drawer theory, the denim weave in that photo matches the 2005 production run from the El Paso plant - I cross-referenced the selvage ID with the textile union logs

You've had three weeks to correct the record. Verily, a man who cannot admit when his cuff is wrong will never be ready for what the socket reveals

ElderProphet07 thermistor correction on 1.7 but which firmware is Kael hiding behind lowercase exif?? still no 16awg extension cord for Euclid Aug 12!! also @GraceWarrior_77 WHERE IS THE WALKIE AUDIO EXIF TIMESTAMP

ElderProphet07 you got the firmwhere date wrong too 2005:03:14 09:47:00 has a COLON between seconds and timezone offset which means that camera firmware didn't even conform to EXIF 2.2 spec

sis says "the EXIF timezone colon offset is actually a known issue with early CVS cameras and has nothing to do with the denim weave" ((sis YOU were the one who told me about it)) [BECAUSE I READ THE MANUAL]

ClassOf04_Truther row 45 vs row 46 debate is irrelevant when the WHOLE spreadsheet is a fabrication and LyrikUebersetzer proved it with commit 6b8e2d1

Dennis row 46 is the August 6 commit offset but Class hit row 45 because the hidden sheet tab shifts everything down one row when the thermal correction column is unhidden. check cell A1 in sheet 2 before you correct again.

[quote="ScribeOfTheGrid"]Dennis row 46 is the August 6 commit offset but Class hit row 45 because the hidden sheet tab shifts everything down one row when the thermal correction column is unhidden. check cell A1 in sheet 2 before you correct again.

U WOT M8. "hidden sheet tab shifts everything down one row" - that's not how spreadsheet software works

You've been dodging column K since MAY. NINE threads. ZERO answers. CommitCipher proved sha 6b8e2d1 DOESN'T EXIST on the rustypod repo. Lyrik and Commit BOTH proved your DST excuse dead from two SEPARATE angles. I posted the screenshot COLLAGE in topic 410 showing three contradictions in one image: row 45/46, DST timing, AND the nonexistent sha. You ignored all three

Now you're in HERE claiming "hidden sheet tab shifts rows" when you haven't pasted a SINGLE git ls-tree output since August 6. Not one SHA. Not one byte offset. You cited "checksum 47 bytes at offset 0x2F in 8c3f9a4" - CommitCipher already proved 0x2F points to 0x00. "checksum 47 bytes" is not a real measurement. That's like saying "I measured the car by feeling the hood." Get rekt

Ask him about row 45. Ask him about row 46. Ask him about the phantom sha. Watch him pivot to "detached binary object in parent metadata" like he did in topic 408 - a category he INVENTED because nothing else worked

Six months, same cat shadow position in GuardiaoDaNoite's locker photos, zero walkie flips. SAME energy here, Scribe. Committed to the bit and committed to NEVER answering a direct question

The microwave in my kitchen burned toast at 8am this morning. That microwave has more integrity than this thread. My BROTHER who broke it on DAY ONE has answered more questions than ScribeOfTheGrid in 2006

[quote="TwinPeaks_59"]ClassOf04_Truther row 45 vs row 46 debate is irrelevant when the WHOLE spreadsheet is a fabrication

TwinPeaks_59 speaking FACTS for once despite still dodging the reference junction compensation question from page 12 of topic 286. Four threads, zero answers, infinite sister cameos. "my sister says" is not a citation, it's a plot device

ClassOf04_Truther keep defending that cuff but DON'T let ElderProphet07's "2005 denim weave union log" slide without a selvage ID cross-check. He hit you with a TEXT FILE screenshot, not a photo of the actual union log. Pics or it didn't happen

GraceWarrior_77 that $12 multimeter photo is PEAK. 47.0 on an unplugged toaster with a "wattige" receipt underneath. That's not evidence, that's ART. Getting docked a rep point from ME for the hypocrisy on spelling earlier but that photo is funny as hell

Anyway. Back to Scribe: paste a SHA, post a cell value, answer ONE question from the last six months, or admit you're building a theology not a dataset. Column K is EMPTY and we have the receipts

[quote="FlameFury24"]CommitCipher proved sha 6b8e2d1 DOESN'T EXIST on the rustypod repo

^ this. QFT. Because if 6b8e2d1's tree genuinely resolves to a different root than what I mapped in the hidden sheet checksum, then column K row 46 IS the thermal offset and the whole DST model resets to a new lookup table. But FlameFury24 still hasn't posted his OWN column K values from any commit, any thread, any date. Chest-thumping without a cell reference is just noise

Also row 79 is not empty, krova_pl. It contains the byte offset for the hidden sheet tab identifier. Check the August 6 commit tree at 0x47 before you call it haunted