Friends of Gabriel Chantayan

CommitCipher still citing the wrong revision sha while the hidden sheet row 79 checksum is right there in 6b8e2d1.

CommitCipher wrote:ScribeOfTheGrid posting about column K thermal offset in topic 161 but still wont say what value was in K47 before it went blank

^ this. CommitCipher been doing the actual reading while ScribeOfTheGrid hides behind TechAngel_00's "missing thermistor" story like we forgot the printer serials hit byte 47 three weeks early. A printer doesnt predict a null in a commit log unless the null is staged. Just saying.

Scribe - you answered FormatKing about sig width. You answered TwinPeaks about concrete. You are typing. What was in K47.

"NULL - DO NOT FILL" is not an explanation Scribe it is an instruction you left for YOURSELF so you wouldnt have to answer us!!!

I spent my whole lunch break thinking about this thread and you all are still dancing around the same question while ScribeOfTheGrid sits there answering FormatKing about signature width like that's more important than the blank row 47 he's been carrying since July. I don't usually tell this part but when I was at the dollar store today restocking the birthday cards I realized something - the 47 threads per inch in my 2003 hoodie cuff photo isn't just a number, it's a promise that keeps showing up everywhere including Scribe's null byte and the truckstop clock and the gamma curve and nobody wants to admit that all three converge on the same physical proof I posted back in April. CommiCipher keeps asking what value was in K47 before it went blank but I already gave you the answer in the weave grain of that photo - the threads don't lie about column offsets the way Scribe does with his hidden sheet excuses. TechAngel_00 can call it a missing thermistor all day but my photo was taken in 2003 with my sister's old camera and the battery was dying and I still got 47 threads per inch in perfect focus and that predates every commit and every spreadsheet and every excuse on this board.

ScribeOfTheGrid wrote:Scribe - you answered FormatKing about sig width you answered TwinPeaks about concrete you are typing what was in K47 before it went blank you cant hide behind hidden sheet row 79 checksum forever when BBS has her 16awg extension cord coiled and ready rated 15A with EUCLID READY taped to her Fluke 87V and she is DONE waiting like literally DONE waiting nobody brings cords nobody answers cell values nobody delivers pole serial photos answer the cell value or trade for the cord already

ScribeOfTheGrid wrote:still dodging row 79 column K photo and cuff photo spreadsheet theater over actual sockets

Scribe your online right NOW answering about b tags but the cell value stays blank BBS brought her own cord coiled and ready rated 15A wrote EUCLID READY on tape stuck to her Fluke 87V and she is WILLING TO TRADE for your Fluke 87V finally someone gets it but you still owe the cell value and the pole serial photo and the cuff photo and the walkie audio with EXIF delivery

CommitCipher this is the fourth time you've cited sha 4f1a9c7 in this thread. The hidden sheet row 79 checksum validates against 6b8e2d1 only. Your 4f1a9c7 parent does not contain the hidden sheet tab at all. The cell you want is K47 in 6b8e2d1 which reads NULL by design because the formula in row 79 pulls from a lookup table you cannot see unless you unhide the sheet. Asking what was in K47 before it went blank is asking what value a VLOOKUP returns before its source range exists. That is not a null byte. That is a broken reference.

ScribeOfTheGrid wrote:hidden sheet row 79 checksum is right there in 6b8e2d1

what value was in K47 before it went blank

^ this. Exactly what BestBuddyStar said. Nobody brings cords, nobody answers cell values, nobody delivers pole serial photos. I posted my August commit screenshot with the hidden sheet checksum visible THREE TIMES in this thread and people still asking what was in K47 before the reference broke. The VLOOKUP source range was empty = blank cell. That is basic Excel. Not a conspiracy.

"NULL - DO NOT FILL - SEE HIDDEN SHEET ROW 79" is not a value Scribe. That is a sticky note you left for yourself so you wouldn't forget to keep not telling us. You answered FormatKing about his sig width and TwinPeaks about concrete in the time it took you to open that screenshot but you STILL haven't said what was in K47 before you nulled it. CommitCipher asked you three ways and ClassOf04_Truther showed you the hoodie weave from 2003 and you gave us a cell comment that says DO NOT FILL. Thats not an answer thats a confession. Just saying.

ScribeOfTheGrid "basic Excel" and yet you're the only one who had a hidden sheet tab to "unhide" if the VLOOKUP source was blank then the formula never existed until you made the hidden sheet AFTER the commit and NOW the null reads like prophecy

[bro] we're supposed to believe row 79 was in the sheet all along but nobody noticed in the FOUR threads you dodged before today?

[sis] actually the commit history from 6b8e2d1's parent DOES show a missing tab count between April and July - I checked the file size delta. the hidden sheet could have been added at the same commit. but that still means K47 was genuinely empty, not a deliberate null... just an unpopulated cell that later got meaning assigned to it retroactively. which is exactly what I'd do if I were manufacturing a sign

[bro] see? even she doesn't buy it she just gave a better version of your own excuse and called it manufacturing. answer the actual question or trade the hidden sheet password for my sister's library screenshot

- the twin one

my 2003 cuff photo weave grain predates your hidden sheet

ScribeOfTheGrid wrote:the VLOOKUP source range was empty = blank cell. That is basic Excel. Not a conspiracy.

"Basic Excel" says the man who cited row 45 in topic 277 and 314, then admitted row 46 in topic 319, and NOW wants us to believe K47 was always meant to be NULL because of a VLOOKUP to a hidden sheet that somehow didn't exist in THREE earlier commits.

You don't VLOOKUP a cell that doesn't exist yet and call it "by design." That is called admitting you left it empty and now you're reverse-engineering excuses. CommitCipher asked what VALUE was in K47 before it went blank and you answered "a broken reference" which is forum code for "I don't know and I'm typing fast."

CommitCipher sha 4f1a9c7's parent predates your hidden sheet tab. So what lookup table was K47 referencing in JULY when the hidden sheet didn't exist yet? Get rekt.

ScribeOfTheGrid wrote:hidden sheet row 79 checksum is right there in 6b8e2d1

what value was in K47 before it went blank

ScribeOfTheGrid still typing in 2006 but his Excel is stuck in 1997 with hidden sheets and broken VLOOKUPs

DO NOT IGNORE ME.

ScribeOfTheGrid wrote:the VLOOKUP source range was empty = blank cell. That is basic Excel. Not a conspiracy.

basic excel my ass you just admitted the hidden sheet tab was added AFTER the commit that you keep citing

^ this. FlameFury24 says K47 was empty in three earlier commits but TwinPeaks_59's sister already checked the file size delta and confirmed the hidden sheet tab count matches between June and July. The VLOOKUP didn't have a source range until the August commit populated the hidden sheet. So yes, K47 was genuinely blank in July. That is exactly what NULL by design means - the formula existed but the lookup table hadn't been written yet. Not a conspiracy, not reverse-engineering, just a spreadsheet with a phasing delivery schedule.