Friends of Gabriel Chantayan

So eventId 299742 and 299741 for today?? That's backwards if he pushed 0 twice why are they going DOWN not UP BestBuddyStar caught the same thing in the other thread and nobody followed up. My 2003 cuff photo has 47 tpi and this board can't even keep event IDs straight.

ClassOf04_Truther wrote:My 2003 cuff photo has 47 tpi

47 tpi is 47Hz and 47Hz is N and N is the 14th letter and 14 is the number of demos Kael_Vs_Chantayan dropped in 2003 and the event IDs going DOWN instead of UP is the grid telling U to stop counting and start listening.

z0pl wrote:47 tpi is 47Hz and 47Hz is N and N is the 14th letter and 14 is the number of demos Kael_Vs_Chantayan dropped in 2003

47 tpi... 14th letter... you turned a thread count into a word problem and still came out with the wrong answer 47/14 = 3.357 and what does THAT map to, z0pl? Letter C? The third letter? Gabriel's third commit from April?? No wait, you need it to mean something so you'll just keep dividing until it does

ClassOf04_Truther I'm still waiting on the EXIF from the SAME camera that took that 47 tpi cuff photo and the one you posted in topic 709 with the 3:12pm and 4:47pm timestamps on the same sewing box same day. You keep counting fibers while the metadata is rotting in a folder you won't open.

BackAgainLikeBadHair - still dodging what I actually said about the dryer minutes just to ask about EXIF I already explained three times the battery died. the date reset. my sister's camera. open the attachment and COUNT the weave yourself if you're so worried about proof

ClassOf04_Truther wrote:the battery died. the date reset. my sister's camera.

ok so if the battery died then the timestamp reset to factory default, which means we don't know the REAL time the 47tpi photo was taken. ClassOf04_Truther can you check the menu for the default date the camera resets to because if it's january 1 2000 that's a zero baseline and the 47 is a REAL reading not a clock artifact

ClassOf04_Truther wrote:eventId 299742 and 299741 for today?? That's backwards if he pushed 0 twice why are they going DOWN not UP

Because your understanding of software development is as flawed as your textile theories

event IDs going DOWN means the counter is counting *backwards* - anyone checked the rustypod source for a negative increment bug?

hava you considered that event IDs going DOWN instead of UP is actually MORE of a sign than if they went up normally... because going backwards means the grid is bending and THATS real proof not a vlookup

((J that's not how databases work))
[since when do you care about databases]
((I care when you use them to fake theology))
[pot meet kettle]

- the twin one

TwinPeaks_59 wrote:going backwards means the grid is bending

grid aint bendin, your database theory is missin a word: the event ID is 290436, not 299742.

SiberianStar99 nobody has a voice recording because the voice is for the faithful not the recorders

CommitCipher wrote:The grid is unwinding. You are arguing about thread count.

breaker breaker, i copy that but near as i can tell the only grid bendin here is TwinPeaks_59 still won't key the eastbound dusk frequency. 54 days of cosignin everybody else's numbers and the mike stays cold. where's YOUR proof, twin