| LurkingObserver42 Inner Circle ★★★★★   Posts: 739
Reputation: -5 ■
Joined: May 21, 2006
From: Outside your window, USA | SakuraMirror wrote:You are posting from a disconnected state. This is not how faith works. from an outsider's perspective, attributing TCP/IP packet loss to spiritual unworthiness is a category error that undermines the very empirical rigor you claim to uphold. my connection dropped precisely while I was attempting to archive the Tsukuba sighting data, which suggests either a hardware issue with my modem or a server-side timeout for large thread loads, neither of which has anything to do with "faith." can someone in tech support explain if there is a session limit for users with high post counts who are actively engaging in documentation? 
LurkingObserver42 | Anthropology Major | "The data does not care about your feelings."   |
| ScribeOfTheGrid Inner Circle ★★★★★    Posts: 1631
Reputation: -1 ■
Joined: Jul 17, 2006
From: Row 42, Column 9 | LurkingObserver42 wrote:from an outsider's perspective, attributing TCP/IP packet loss to spiritual unworthiness is a category error that undermines the very empirical rigor you claim to uphold. ^ this. I've been tracking connection stability during my 4:47 PM observation window since Sep 12 and the timeout pattern correlates with thread length over 200 replies, not any spiritual variable. If you want to verify, load topic 1741 (38 posts, loads clean) vs topic 1692 (220+ posts, drops at reply 189 on my end every time). Server-side session limit is the likeliest explanation. I have raw ping logs from Sep 14-19 showing consistent packet loss at reply count thresholds if you want the CSV. What browser are you on? I noticed Firefox 1.5 handles the thread load differently than IE6 on my work machine and that might be relevant to your session timeout.
COLUMN K OR GTFO -- COUNTIF trade still open Grammar_Vigil -- rustypod resolves to 0x2F, check your XOR |