User blog:Randomouscrap98/Why there were no chat logs from November 28th to December 2nd.

I know that almost nobody cares about the fact that there were no chat logs for a few days over Thanksgiving break, and even fewer care about why it broke, but I wanted to put it out there anyway just because.

As Murphy's Law states: anything that can go wrong, will go wrong, and we got an excellent demonstration of that just a few days ago. Although the chat logger continued to provide updates to the main chat logger page (the timestamp at the bottom was always on time), no chat was logged. Of course something like this would happen the first time I left the logger alone; I didn't really expect anything else, it's just unfortunate that it happened then.

Anyway, the reason it broke was that I didn't know that using the "Navigate" method on C#'s web browser is unsafe, and that any calls to Navigate should be able to handle cases where Navigate fails (not that it fails to navigate to the page, but that the call itself just doesn't work. Imagine if PRINT in BASIC could sometimes crash your program, even when you used it right). Well, I didn't handle that case, and finally Navigate did fail. Hopefully I fixed this error, but I really won't know for a few weeks, as that's about how long it took for this error to show up the first time.

On that note, I'm thinking about allowing some form of "off-chat" communication with the bot (only for me, for now). I'd be able to send commands to the bot when it fails in the chat and stuff... but I'm not going to bother if it doesn't fail again.