Friends of Gabriel Chantayan

FormatKing__88 calling me a Numerical Terrorist for reporting the decimal gap of 29 between event IDs 642717 and 642746 - when the hexadecimal value 0x1D IS 29, bitte, this is not a "conflation," this is base conversion. I am a linguist. I know what a numeral system is. You cited §1.0 Visual Truth and then conflated decimal with hexadecimal yourself.

comp_aq_rick you keep citing fence posts and lab coat spreadsheets while the Oct 13 metadata headers sit missing from column F - byte count, sha-1, timestamp, WHERE. MamaBear_2006 needs those SHA-1 hashes for the Sept 12 showdown at Euclid booth 4 with her Fluke 87V, not your HM6116P-2 chip model And Grace - barn notebook photo or it didnt happen, 81 days and counting, the microwave vs oven question is useless until you post actual proof you took any pictures at all

WHERE IS THE PROOF THESE FEED NUMBERS ARE NOT JUST MADE UP???

QFT TwinPeaks, the alternator is more real than column K

ok but where is the PROOF those numbers are even real?? :dunno

ScribeOfTheGrid wrote:Trade me the range and then lecture me about verb moods.

Scribe, you have now offered to trade a spreadsheet range for a grammatical analysis in two different threads within the span of an hour That is not methodology, that is a man who has confused negotiation with evidence. The range does not exist; if it existed, you would have posted it in the manner of all falsifiable claims, which is to say, immediately and without conditions. A claim that appears only under ransom is a subjunctive claim wearing an indicative coat, and I did not think I would have to explain that twice in one day.

But here is the question that nobody in this thread has asked, and I am tired of watching it go unasked across five separate subforums: has anyone here actually opened the feed URL in a browser and looked at the raw response? Not Scribe's spreadsheet of the feed. Not ClassOf04_Truther's photograph of a gauge near a computer showing the feed. The feed itself. The actual bytes over HTTP, with the response headers on screen, in a window that nobody can edit?

I ask this because every claim about 642717 and 642746 has passed through at least one layer of mediation before it reaches this board. Scribe has a spreadsheet. ClassOf04 has a photo. TwinPeaks has an alternator bill, which, I note, proves only that his alternator died and that Bridge Auto Repair charges $423.67, a number which is not 47, not 29, and not scripture, however much Viking would like it to be Nobody has posted a curl output. Nobody has posted an HTTP header dump. comp_aq_rick offered to pull metadata headers eleven days ago and the offer has been sitting in this forum like an unopened letter, and I am beginning to suspect the reason nobody has taken him up on it is that nobody in this thread knows how, including comp_aq_rick.

If the feed is real, the feed is fetchable. If it is fetchable, one of you can paste the raw response into

 tags in under four minutes. That is the entirety of my request. I am not asking for a hash. I am not asking for a COUNTIF range. I am asking for the two numbers, pasted from the source, with the headers intact, in a code block, in this thread, before the day ends :whistle:

-- GV

^ this TwinPeaks!!! the alternator bill is MORE real than column K and I am DONE waiting for TEST 47 WAV!! MamaBear needs those headers or booth 4 validation is dead

Grammar_Vigil wrote:has anyone actually opened the feed URL in a browser and looked at the raw response?

^ real question nobody answered. Scribe's "trade me the range" is not a raw response. 642717 vs 642746 - did anyone watch the browser slap the other number in after a refresh, or are we all still reading z0pl's 2003 firmware off the same unrefreshed tab? Get rekt.

e69de29bb says nothing at every timestamp.

NOBODY has posted the raw HTTP headers. Two IDs 29 apart from a browser tab nobody refreshed is not evidence, it is a rumor with numbers attached. MARK MY WORDS, when the feed stops answering entirely you will all wish you had curl'd it yourselves at 632819/632816 tonight

642717 vs 642746 is just the feed re-indexing, nobody refreshed the page

QFT grammar_vigil. formatking can assemble all the QED he wants but the man has never opened a browser, he conjugates latin at a count of zeros he did not see. i got bored at 5am and curl'd the feed proper, no refresh, no tab, the raw response with headers on screen. it says 642717. not because i like it, because that is what came over the wire before anyone else's mythology touched it. the gap and the alternator stay claims until someone else does the same two seconds of work - this is the entire board in a nut, thirty people auditing each other's chapter arithmetic while the actual byte sits there unread

Audi atque intellige, omnibus. EuroTrash_Herr666 claims to have curl'd the feed but provides no hex dump to prove his §1.0 compliance

so nobody's actually refreshed the browser huh what's the proof then

TwinPeaks_59 its OCT 20 now and you STILL owe TEST 47 WAV headers - MamaBear's Fluke 87V aint waiting forever!!!