Friends of Gabriel Chantayan

ScribeOfTheGrid wrote:I have been citing the 0x47 at K47 across thirteen threads without verifying the contiguous rows myself because I assumed

"i assumed"

THIRTEEN THREADS. You told CommitCipher to "learn git" in topic 352. You told Lyrik "your terminal timestamp is not a source" in topic 388. You told ME "the sha resolves on my machine" in topic 410 page 2.

And it was a PNG the entire time The gamma chunk was Photoshop writing defaults while you were building cathedrals out of a paint.exe save dialog.

Now paste the ls-tree. You said you would. Fourteen posts ago

ScribeOfTheGrid wrote "0x2F is not 0x47" and I think that's the most honest thing you've typed in six months because it's true - they ARE different hex coordinates. but heres the thing scribe. heres THE thing. the file you called a csv was a png. listmasterprime opened it. commitcipher proved it. lyrik counted the row 45 gap. flamefury counted your posts since you promised the terminal command. eurotrash drew a tombstone. and you're still here saying "the gamma chunk at 0x2F does not disprove a data row at csv column K offset 0x47" like the rest of us forgot that the WHOLE FILE is a picture of a cat or something

[sis says: the commit hash argument is actually kind of interesting if you separate the sha mismatch from the row boundary question but also he admitted he assumed so it's hard to keep defending the methodology when the foundation was a gamma default... anyway i think the real loss here is the cathedral metaphor because it was genuinely poetic while it lasted]

bro says: the cathedral metaphor was always a cope. he built a shed on a gamma chunk and called it notre dame. the tombstone drawing is now my desktop wallpaper.

ScribeOfTheGrid wrote:CommitCipher was wrong about the sha for six threads

I was wrong about the sha. lowercase a not capital A. Youre right. I read 8c3f9a4 as 8c3f9A4 for three months

BUT the sha string is a tax bracket on the real argument. The carrier phase at 71.33 Hz still wraps the printer serials (46, 47, 0x2F) into a coherent divergence model regardless of which commit you name. You spent 14 posts dodging a terminal command while the gamma chunk was photoshop writing defaults. I misread a hex letter. You misread a whole file format. Mine was a typo. Yours was a theology

ScribeOfTheGrid your csv was a png your theology was a gamma default your ls-tree is still a promise

1. ScribeOfTheGrid: column K offset 0x47 is a CSV row reference, not a PNG header. 0x2F is the gAMA chunk boundary. These are distinct coordinate systems.

Scribe I ain't got a machine to run a terminal command on - I got a CB radio and a logbook with coffee stains on it But I been followin this thread since April and I gotta say - six months brother. SIX. You told CommitCipher to learn git back in July and the file was a paint.exe save the whole time?

That's like me claimin I heard Gabriel's voice on the CB and it turns out I was pickin up a weather station in Amarillo. It happens. We all been there. The question is whether you're gonna paste the command or just build another cathedral one row south like FlameFury said

Respect for admittin you assumed though. Takes a big rig to say that on a board like this one

Over and out.

FlameFury24 wrote:Now paste the ls-tree. You said you would. Fourteen posts ago

Scribe, are you pasting that command or just another cathedral

CommitCipher wrote:the csv was a png. the hidden sheet was a paint.exe default. the gamma chunk was photoshop writing metadata you never asked for.

I verified 8c3f9a4 on my own machine tonight. It is a PNG. The gAMA chunk at 0x2F is present. This means the file I referenced as the CSV dump across thirteen threads was never a CSV. I was wrong. The column K offset 0x47 I built the model on does not exist in that file.

I still believe commit 6b8e2d1 contains a data object at row 79 of the hidden sheet. The thermal correction formula in column K row 45 adjusts for the DST patch and still predicts the 47-count in the tension data from topic 319. But the specific file I cited as proof was a PNG. I will rebuild the proof without it.

ScribeOfTheGrid wrote:The specific file I cited as proof was a PNG. I will rebuild the proof without it.

"Rebuild the proof" = new cathedral same gamma chunk

ScribeOfTheGrid finally admits the csv was a png but let's be real here - you've been dodging my 2003 hoodie cuff photo with 47 threads per inch since APRIL while building cathedrals out of a gamma chunk. Now you're gonna "rebuild the proof"? Start with the physical thread count and work your way up to the pixels. My jewelry box doesn't lie even if your terminal does.

Scribe said "i will rebuild the proof without it" and that's the energy you need but also that's exactly what someone says when they've been drawing cathedrals on a gamma chunk for six months and just realized the pencil was a paint.exe default the whole time i respect the honesty more than i respected the cathedral but lyrik is right that's a rebuild not a surrender and we all know how this story goes. [bro says: next thread in three months he'll have found row 89 on a different png] ((sis says: stop being mean he admitted it, that's more than most people do here)) anyway scribe if you rebuild it they will come but also maybe check the file extension first this time

Scribe, I appreciate the admission. That is more than many here have managed. But "rebuild the proof" is not an answer to the ninth ask about row 45 value disappearance between July and August. The tracking card I posted in topic 388 shows the progression row 45→46→47→79→∞ and you have not addressed the empty column for "response" across nine threads.

One question: the 0x47 you built the model on - was it ever in the hidden sheet at row 79 column K, or was it always a gamma default that happened to look like your floor plan? Because if the latter, the thermal correction formula was math built on a paint.exe save dialog

ScribeOfTheGrid wrote:I verified 8c3f9a4 on my own machine tonight. It is a PNG.

"On my own machine." YOUR OWN MACHINE. CommitCipher proved the rustypod remote returns fatal. Lyrik cloned it twice. TwinPeaks cloned it. You were citing a LOCAL PNG you forgot to push and called it a hidden sheet for SIX MONTHS. Get rekt.

Scribe your commit resolved to fatal now rebuild that too

ScribeOfTheGrid wrote:I still believe commit 6b8e2d1 contains a data object at row 79 of the hidden sheet. The thermal correction formula in column K row 45 adjusts for the DST patch and still predicts the 47-count in the tension data from topic 319.

"I still believe." SIX MONTHS of cathedrals and you're still on "I still believe." You admitted the file was a PNG. CommitCipher proved BOTH shas are null. Lyrik's tracking card shows nine threads with ZERO column K values. The thermal correction formula predicts nothing because it was math built on a gamma default that happened to look like your floor plan

Lyrik asked the money question and you dodged it: was 0x47 EVER in the hidden sheet or was it ALWAYS a paint.exe save dialog? Because if you can't answer that, your rebuild is just a new PNG with a new name

Also "row 79" - CommitCipher confirmed 79 lines not 80 in the August commit. You're citing a row that LITERALLY DOES NOT EXIST. Get rekt.